Skip to main content

My idea for Hearthstone to add more deck slots

Recently someone asked the Blizzard developers for more slots for decks in the game Hearthstone. The response was that they are talking about it and looking into it, but no decision has been made yet. One of the concerns over adding deck slots is that it could complicate the UI for Hearthstone and make it more difficult for new players to understand. I have what I think would be a good solution to add more deck slots without increasing the learning curve for the game much if at all.

First I would take a look at the current selection screen for starting to play a game. It defaults to showing the decks that are custom built by the player if they have any custom decks, and there is an option to page over to the basic decks. This basic deck screen is perfect for how I would change this process.

Instead of having 2 pages of decks, 1 for basic and 1 for custom, you would just see the select a Hero screen. Then once you selected the Hero you wanted, you would see all of the decks that have been built for that hero. It would include the basic deck in the top corner, so even if a new player has never built a custom deck they would see the basic deck option. Then any custom decks would show up just like the current custom deck page except they would be limited to the chosen Hero.
I think this would work just as well as the current UI, if not actually be a little easier because you would know exactly which hero you were picking and then have your choice of deck on the next screen. This solution would allow for 8 custom decks per Hero. I am sure there would still be some number of people that would not find this to be enough, but it should satisfy almost everyone. It would allow players to keep more random fun decks around and encourage experimenting with different styles of play.

How would players navigate the UI to create all of these extra new custom decks? Again I would just take what already exists in the game and expand it out a little. Instead of the sidebar showing you the custom decks that you already have built, you would see an entry for each Hero.

The player would choose the hero they wanted to make a deck for and then see all of the existing custom decks.
Here they could also show the Basic deck so that the player could look at what that deck looks like. It might even be useful for new players to get an idea of what a well rounded deck would look like. I do think this would add a small level of complexity over the current UI because the player would not immediately see their decks, but I don't think that it would be so complex as to not be able to figure out where the decks were.


Comments

  1. Idea is awesome. when you'll install it?

    ReplyDelete
    Replies
    1. Nothing I can do to make this a reality. From the news recently, the Hearthstone team went a different direction and will be adding another page of deck slots.

      Delete

Post a Comment

Popular posts from this blog

Converting a Large AngularJS Application to TypeScript Part 2

In part 1 I was able to take an Angular controller written in JavaScript and convert it to a TypeScript file while doing very little to change the code. In this post I am going to explore transitioning that same controller to actually use the features provided in TypeScript. This is how I left off my controller:
declare var angular: any; (function () { 'use strict'; var controller: any = function($scope){ ... } angular .module('app') .controller('controller', controller); controller.$inject = ["$scope"]; })();
While performing the translation from JavaScript to TypeScript, I would make sure at every step that the functionality I expected still worked, so if anything I did broke the system I would change it back and try again with another approach. Also if something seemed like it worked too easily, I would break it on purpose to make sure I wasn't getting a false result through browser caching a previously working fil…

Converting a Large AngularJS Application to TypeScript Part 1

I work on a project that uses AngularJS heavily. Recently we wondered if using a preprocesser like CoffeeScript or TypeScript for our JavaScript would be beneficial. If our team is going to switch languages, we would need to be able to convert existing code over without much pain and we would have to find enough value in switching that it would be worth the conversion.

I had read an article that stated that because TypeScript is a SuperSet of JavaScript, you could convert a plain JavaScript file to TypeScript by changing the extension to .ts and not much else would need to change. I wanted to test out this claim, so I took a file that I was familiar with, an Angular Controller, and tried to convert it to TypeScript to see how much effort it would take and then try to figure out where we would benefit from using TypeScript.

This is what the controller JavaScript file looked like to start out with:
(function () { 'use strict'; angular .module('app') …

Gamify TDD

I like it when things that would not normally be associated with games add concepts from games as a way to incentives you to accomplish things. Why simply go for a run if you can have an app that will track you and give you a gold star if you do better than you did the last time? Why go to the coffee shop that only gives you coffee if the other one will give you points that you can redeem for free drinks eventually?

I was recently introduced to CodeSchool, an online training system similar to PluralSight, it has video courses and challenges you can take to prove that you retained what the video taught. CodeSchool also adds badges and tracks to your learning, so as you complete a video and its challenges you get a badge. Complete a collection of courses within a specific discipline and you become a master of that discipline.

Some of these incentives are not tangible and really don't mean much in the real world, but they tend to work for me. If I start working towards a large goal a…