New Game & Graphics tutorial

[RwGast]

[randall]

Actually I was being sarcastic about ridding ourselves of all those APIs.<br><br>EasyCE is just a tool. Use it - don't use it, it's up to the developer. If Invasion and Poccer are any indication, it certainly wouldn't have killed them to have EasyCE at their disposal. Maybe they could have spent less time reinventing the wheel and spent more time on content and gameplay.<br><br>After all, it's not about how you get there it's about the end result.<br><br>

[jongjungbu]

I agree with Randall and Robert both. It IS just a tool. Its a choice that some folks should make and others should go without. But if you don't understand the API, how could you possibly debug if you dont even know what particular message is being handled incorrectly.<br><br>I wish I had seen easyCE before I started work on Helios. Because I concentrate so much on the gameplay, playability, and difficulty, that I hardly touch any of the other features that an additional library would have helped facilitate (graphics, sound, etc). But I think the key must be content. I'm not worrying about these other features as much at the moment. Games like Poccer seemed to worry about neither content NOR graphics. Invasion put some bit of work into the graphics (though not well it still ran pretty smooth), they forgot to put more time into the gameplay. I think they DID rush it, as someone said.<br>I think if you can write your own reusable routines encompassing the API, then that is the best learning experience and the best way to create your own complete programs. Another library or set of instructions would be best utilized as a learning source for those newbies. For those experienced, more than likely I would think they'd want to write their own that did what THEY wanted to do...and could probably write it rather speedily relatively speaking.<br><br><br>