News for hackers. Stuff that matters.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Sunday June 05, 2016 @10:24PM (#11844267)
This is excellent for the history and for the examples of what worked and what didn't. But the interpretations are a little dubious:

Takeaway: Game developers should create a well-defined concept before beginning development as opposed to an ad hoc method of game design.

This would exclude Dota, for example. Gamedev is a world of exceptions.

In general, it's best to playtest every idea you come up with and cut whatever isn't fun.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by flashman on Monday June 06, 2016 @01:01AM (#11844760)
Having "a well-defined concept before beginning development" would seem to include Dota and other successful mods, because Valve is starting with a successful game concept (compared to the vast majority of mods that never find an audience). For Counter-Strike/TF2/Portal/Dota, Valve took a strong existing concept and developed it. It's exactly what's recommended in the takeaway.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by wingerlang on Monday June 06, 2016 @02:47AM (#11845070)
You are probably thinking of Dota 2. Both Dota, CS and TF where most likely developed ad-hoc as they were mods that grew organically.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by ben_jones on Monday June 06, 2016 @03:05AM (#11845121)
Their were Age of Empire mods that were essentially MOBA scenarios. I don't doubt many such ideas are ad hoc genius, but a lot of game dev is re-hashing with a twist.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by stepvhen on Sunday June 05, 2016 @10:47PM (#11844337)
Dota was a user made mod originally, so I don't think that counts.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Sunday June 05, 2016 @10:59PM (#11844377)
Mods have been some of the most successful types of games, which seems like a pretty persuasive reason they should count. Some of the biggest names in the history of gaming started out as mods: Counterstrike, Team Fortress, etc. Valve's success is arguably because they find user-made mods and make them triple-A.

Also, the advent of engines like Unity and UE blur what "modding" means. The WC3 engine was flexible enough to be made into Dota, which was then implemented on the Source Engine as Dota 2. But why was the original Dota a mod, whereas Dota 2 isn't? It's hard to come up with a definitive answer to that.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by stepvhen on Monday June 06, 2016 @12:29AM (#11844660)
I think there is a misunderstanding: Dota doesn't apply to the quote "Game developers should create a well-defined concept ..." since it was neither conceptualized nor made by the Warcraft programmers.

Additionally, the originally Dota started as a mod, was then published as a game, and Dota 2 would then not count as a mod. Its not hard to come up with a definitive answer to that. A game is a mod if it doesn't stand alone, if it requires _modifying_ the structure/code of another game.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Monday June 06, 2016 @12:38AM (#11844696)
The Warcraft 3 engine was flexible enough to implement Dota, just like the Unity engine was flexible enough to implement Rust. By your criteria, Rust is a mod, even though it's clearly not.

It's better to say that mods are games and to treat them the same than to try to differentiate them. The same design process that yields a successful mod will yield a successful game.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by yelnatz on Monday June 06, 2016 @02:52AM (#11845084)
Rust is not a mod, but is a clone of a mod of Arma2 called DayZ.
Re:An Analysis of 155 Postmortems from Game Development [pdf] by sillysaurus3 on Monday June 06, 2016 @09:40AM (#11846655)
This is a strange comment, because the first half is what I said. Rust isn't a mod. Yet their criteria would classify it as one, since the Unity programmers did not conceptualize Rust when they created Unity.

But the second half is completely false. Rust has nothing whatsoever to do with DayZ, except that it's vaguely in the same genre.

Re:An Analysis of 155 Postmortems from Game Development [pdf] by chipsy on Monday June 06, 2016 @01:03AM (#11844766)
Modding basically recoups the investment into making a game's community - an individual can present their result to an existing player community directly, with a brief forum post, and a small website with some images or video to advertise. That is enough to build a small empire on, going by the most popular examples.

That's different from the typical lifecycle of a commercial game, which has a deeper level of marketing work to do before it can even consolidate a playerbase. There isn't a "Unity modding community", per se. There is a community of Unity developers, and players of individual games made in Unity, who have no broader associations. A game transitioning from the mod sphere of an existing game to an independently produced commercial title still has to overcome this gap, and most of them don't make it over the line.

The advice is sensible, nevertheless. If you can extend the schedule to focus on the core elements of the design as a "R&D" process where the majority must be thrown away, and only scale it up towards a shipping product as the concept proves itself, you minimize the risk of the budget being wasted on a flawed concept. Modding scenes, game jams, and micro-budget productions all have the benefit of weeding out most of the really early, risky design experiments, without wasting enough of people's time or money to care.

Even when conceiving the marketing for a larger production, the same advice works. The "trial balloon" or "landing page" method, etc. You still do design thinking when you market, but it's design on the topics of "how do we build a funnel" or "how do we make this a franchise." Still very easy to spend a lot of money on making a splash without getting the blueprint right.

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.