Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use phaser states #2

Open
DreadKnight opened this issue Apr 17, 2016 · 2 comments
Open

use phaser states #2

DreadKnight opened this issue Apr 17, 2016 · 2 comments
Assignees

Comments

@DreadKnight
Copy link
Member

DreadKnight commented Apr 17, 2016

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/

@DreadKnight
Copy link
Member Author

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.

@DreadKnight
Copy link
Member Author

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.

@DreadKnight DreadKnight reopened this Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant