1 decade ago by beardedbuddha
Hey guys,
still working on my first small 2D sidescroller (my rite of passage, and my first game).
I want to do a level select screen, much like the ones you remember from Super Mario World.
You know, the one where you saw islands from above and you'd walk Mario along a set path from each level to the next. In this regard I have a couple of questions as to how I should do this.
As I see it, I have a couple of options. I could..
a) Do it as a level itself. A special WM built level with its own tilesize, tileset and rules.
Problems with this: My main game uses gravity and a specific control-scheme.. How would I go about changing all these parameters for the level-select screen only?
b) Do it as a separate game, is in
Problems with this: If I do it like this, I have a hard time figuring out how I would pass data around between the different games. I could store things in an object in
As I see it, these two are my best options. Could you give me some advice on how to structure the relationship between the level select screen, loading the levels, keeping track of the levels, global data and so on?
Thanks in advance
- BeardedBuddha
still working on my first small 2D sidescroller (my rite of passage, and my first game).
I want to do a level select screen, much like the ones you remember from Super Mario World.
You know, the one where you saw islands from above and you'd walk Mario along a set path from each level to the next. In this regard I have a couple of questions as to how I should do this.
As I see it, I have a couple of options. I could..
a) Do it as a level itself. A special WM built level with its own tilesize, tileset and rules.
Problems with this: My main game uses gravity and a specific control-scheme.. How would I go about changing all these parameters for the level-select screen only?
b) Do it as a separate game, is in
LevelSelectScreen = ig.Game.extend({
Problems with this: If I do it like this, I have a hard time figuring out how I would pass data around between the different games. I could store things in an object in
ig.gameState = {}
or something like that. Any thoughts on this?As I see it, these two are my best options. Could you give me some advice on how to structure the relationship between the level select screen, loading the levels, keeping track of the levels, global data and so on?
Thanks in advance
- BeardedBuddha