There is FAR more to game design than graphics. Heck, I''m working on multiplayer rpg right now, and the idea of making a server that can scale to 1000+ users, with worlds gig+ in size, is something that DirectX will not help you with at all. Not that I''m saying a load-balanced, multithreaded, server should be the next article. Hey, come to think of it, I may write one when I''m done ;>.

I would really like to see an article detailing inner workings of a game. Heck maybe even some kind "code critique" article/series going say the Quake source(since it was GPL''ed and is available). Preferably something not a FPS though(personal thing). Someone talking about programming the guts of game, not a tutorial about some API, nor a discussion of how to write tetris, but say a moderately complex game, and it ought to be something thats done, not a theoretical walk in the park(however there should be lots of theory in the article though), but about the issues you come across in a game, like say putting in scripting languages in a game(roll your own, integrate Perl, simple languages like Forth or C-like variants with higher level abstractions).

Maybe this sounds like _boring_ stuff since it doesn''t making flashing lights on the screen, but heck there IS a lot more to a game than pretty pictures.

Sorry about the rant, just one frustrated programmer coding too late at night.

And oh yes, I will put my money where my mouth is sometime, maybe this fall I''ll start writing some articles on these articles once I''ve explored the topic thoroughly enough to say something worthwhile.