Earlier quoted context omitted.
Are you sure about the book title? That one is a guide to post ww2 combat whereas this one: The Complete Wargames Handbook http://www.hyw.com/Books/WargamesHandbook/Contents.htm Is about how to make computer war games.
This one: http://www.amazon.com/How-Make-Fourth-Edition-Comprehensive/... Called "How to Make War" and it describes the mechanics, the theory, and the variables that impact the prosecution of warfare. The Wargames book was, in my opinion of course, a derivative which attempted to re-contextualize the information from HtMW into something more directly 'wargame like' but, again in my opinion, it left out too much to be…
A developer who spent 13 years making his childhood game
101–106 of 106 posts
Re: A developer who spent 13 years making his childhood game
#102This article is pretty light on content. Much more interesting is the well-produced video the dev made himself, talking about his experience making the game, and talking about why it took 13 years. The Game That Time Forgot: https://www.youtube.com/watch?v=2b0tSu0QDQ0
Re: A developer who spent 13 years making his childhood game
#103Earlier quoted context omitted.
What exactly does that mean?
Maybe he means that, when he wants to be told a story, he reads a book or watches a movie, and when he wants to play a game, he plays a game. I feel mostly this way myself: when I want to do something interactive, I want to do something interactive, not watch cutscenes or listen to or read dialogue. I guess this is why singleplayer story-driven games have never interested me very much, and why I prefer multiplayer ga…
Re: A developer who spent 13 years making his childhood game
#104Are there any good such games for mobile platforms? Maybe the game is not good enough though...
Re: A developer who spent 13 years making his childhood game
#105Earlier quoted context omitted.
Considered a ground-up rewrite using something like Unity? They have some kickass 2D tooling now, plus you get physics for free
Unity is closed-source; I'll bet in ten years we'll see the same thing happening again, with people trying desperately to find some way to run these old games that were developed on the no-longer-supported Unity platform.
Developers write their own code in unity (C# or JS) as well as bringing in their own assets (music, art, etc). So even if the unity engine disappears, authors will be able to release their work in a meaningful fashion.
Re: A developer who spent 13 years making his childhood game
#106Earlier quoted context omitted.
I feel exactly the opposite. To hell with graphics and story-telling - I want to play a GAME with good GAMEPLAY
What exactly does that mean?
I like games with great core mechanics, balance, etc. Hell I actually value soundtracks over graphics or story.