News for hackers. Stuff that matters.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by ekianjo on Sunday June 05, 2016 @11:32PM (#11844483)
This advice is super generic.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by stepvhen on Monday June 06, 2016 @12:32AM (#11844675)
Sometimes you start game development with a single mechanic and see where that takes you. Like "what if you could control gravity" and that might lead to VVVVVV or others. Or it might crash and burn. The advice is to encourage developers to flesh out ideas and vet them rigorously before starting development.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by flashman on Monday June 06, 2016 @01:05AM (#11844778)
Sometimes it's complete serendipity. The Rocket League creators were originally making a deathmatch-with-cars mod for Unreal Tournament. Then someone dropped a giant ball into the map, and they realised 'car soccer' was a much stronger concept.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by ido on Monday June 06, 2016 @01:08AM (#11844784)
The problem is that you can't, really - not if you're making something original. You have to actually prototype and try the ideas, and the experimentations continue throughout development.

You can only really create a complete "fleshed out" design upfront if you're walking a very well trodden path.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Sunday June 05, 2016 @11:46PM (#11844521)
No more generic than "Make something people want" or "Listen to your users." And yet most companies get these wrong, just like most game companies fail to playtest their ideas.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by LionessLover on Monday June 06, 2016 @08:08AM (#11846146)
Why do you say "and yet" - since such generic "advice" is useless so is the conclusion "and yet they get it wrong!" (I told you something useless - why doesn't it help?)
Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Monday June 06, 2016 @09:43AM (#11846679)
Because if you follow this advice, you're more likely to yield a successful product.

Playtesting isn't useless. It's how fun games are made.

Perhaps people are disagreeing with this because they haven't tried to make a game. A curious phenomenon.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by squeaky-clean on Monday June 06, 2016 @12:25PM (#11847963)
But that's not advice. It's the same as telling a video game player that to win you need to "get a higher score than the enemy" and "play really well". And when someone loses, "I gave them such great advice, and yet they messed it up!"

"Listen to your users" is not advice, it's the end goal. What's the most effective way to listen to your users? Professional playtesting? Open alpha/beta? Forums, IRC channel, a subreddit? Frequently scheduled AMA with the devs? Infrequently scheduled AMA with the devs?

Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Monday June 06, 2016 @01:06PM (#11848301)
Play the game. When you notice something isn't fun, remove that thing. Repeat. That's playtesting.

If you want to watch someone doing this, pull up some videos of Notch making games. That's the process he follows constantly, from start to finish. He also has good taste, which is why his games turn out well.

If you don't have a nose for what's fun and what isn't, you have to take feedback from your users. If it's a multiplayer game, you should take feedback from the most competitive users, ideally from the people who are trying to form pro tournaments around your game. Casual players don't care what you do to the game, because it doesn't affect them much. But competitive players are your lifeblood, even if you don't know it yet. A competitive scene is what carries a game after its shelf-life has expired.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by ekianjo on Sunday June 12, 2016 @12:33AM (#11886663)
"Noticing something is not fun" is the archetype of non specific advice. There are tons of games i dont find fun yet many are very popular and other folks seem to enjoy them. And even then even if you do playtesting you need to ensure your sample is representative and things like that.

Playtesting is key but its far from being a simple step in itself and it never tells you exactly what is the right solution to fix things. Thats why making games is hard.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by LionessLover on Monday June 06, 2016 @11:05AM (#11847279)
You simultaneously complain the advice is generic and claim it's useful. You always bet on both colors in roulette? No, generic advice is not useful. It's... too generic.