Posted 23 January 2002 - 10:38 PM
alright maybe a little over the top...but c''mon...if you don''t have a good go yourself first and work out what you need to learn...how will you ever learn that well?
Members - Reputation: 523
Posted 24 January 2002 - 02:20 AM
Make it work.
Make it fast.
"Commmmpuuuuterrrr.." --Scotty Star Trek IV:The Voyage Home
Members - Reputation: 182
Posted 24 January 2002 - 09:40 AM
Anyway, to make a game, it is a matter of differentiating what is seen by the player on the screen, and what your code has to calculate to get there.
Imagine Super Mario Bros.
On the screen, you see a guy running and jumping.
In the game, it is more like this:
And in each function there is more underneath, such as testing to see if Mario is jumping, going up or going down, and whether or not he is hitting a brick that can break or a solid part of the wall, checking if he is landing on an enemy, whether that enemy can be squished or hurts Mario instead, etc.
There is a lot going on in Tetris that is similar, but the end result is a game that the player sees on the screen. It might seem hard at first, but Tetris is probably the basic game. Pacman and Mario just add extensions to it, such as AI and enemies and such.
(Gorgeous graphics)+(beautiful sound effects)+(symphonic music)+(no gameplay) != Good game