Well, we were expecting some response to A Heavy Problem, but we severely underestimated just how much interest everyone had in contributing. If you're one of the many folks who emailed us proposals and haven't received a response, please accept our apologies, because there's just too many for us to reply to all of them. From the large amount of feedback and forum activity, it's clear that many of you found this interesting, so we'll definitely be posting more design goals. For those of you still thinking about it, here are some more tools to use in evaluating ideas:
The last one raises another question: What other goals should we have for the Heavy update? Half the battle of good design is choosing the right goals and the right constraints. In A Heavy Problem, we specified a goal for you, and the constraints that had to be kept in mind. Try taking a shot at defining the overall set of goals that the Heavy unlockables should be trying to achieve. Watch out for the common circular logic trap of finding an idea you like and then trying to extract goals from it. We find it's best to not think about ideas at all at this point, and to focus entirely on more abstract goals. What are the biggest problems in the Heavy class? In what situations is it the least fun? Like idea evaluation, goal generation is a big topic in itself, and one we'll go into in a later post.