Open DreadKnight opened 8 years ago
Game loads too fast; also states probably a bad idea, rather hard to deal with them atm and maybe more suitable for a different type of game.
Might give states another go, but within a single file this time to keep things a little simpler as I'm not using an IDE yet.
Current prototype doesn't make any use of states. Should have one for main menu / gameplay / outcome And perhaps even for booting/loading, in case that assets will become quite large for slow connections. Booting could be Gumble head static + tutorial at the top + LOADING text (graphical asset), when done loading, some music could be playing, Gumble could be moving around and text displayed would be "PRESS START", so basically state would change to main menu with more going on, even having the key input. There's a cool example over here (which does sorting of groups nicely) http://jsfiddle.net/6fnrgxcv/3/