Jump to content
  • Advertisement
Sign in to follow this  
FoxHunter2

Game flow chart (UML)

This topic is 4866 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi guys! This is my first attempt in creating some kind of a design for my little game engine (just for testing purposes right now). I'd like to know what you think about it. Right now I've only created a flow chart. If everything is fine I will continue with class diagrams and all the fancy UML stuff. This is the thing I came up with: click! regards

Share this post


Link to post
Share on other sites
Advertisement
It's a good start. However, you have several actions that have no exit arrows (e.g. "GameState = GameSplash"). This means that once you get there, the application will forever reside there! There needs to be a way out of these boxes! :)

Share this post


Link to post
Share on other sites
These boxes (gamestate = ...) actually mean that once the gamestate is finished (e.g. a splash expiring after a display time of 5 seconds) it will switch the gamestate to the next one, so that the next render-loop will switch to the next state.
Is it actually necessary to check the gamestate before each render loop?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!