Pause Behavior for Level Success Screen, and Pause Screen VS. Using Current Scene.

VoidedSky

Hey, Quick Question:

I know that in the past, that pause screens and level success screens have been implemented as just another area of the scene, to save on loading times. Since then, loading times have improved. I don't have the apple developer program yet, so I can't test this, so what do you guys think? Do I make my level success screen as just another part of the game scene, or do I make it like a pause screen? And for the actual pause screen, should that be an actual pause behavior and scene, or should I just make a pause area in the game scene, while artificially "pausing" all of the actor?

Thanks!

-Josh

Approw

I have the same trouble, I want a game over screen but when you pause the game you can't reset the scene from another scene. can somebody give some advice?

VoidedSky

@matthiasstoopman
I believe thats a different problem...
You can probably reset the scene from the pause scene by having a game.resetScene attribute. Change it to 1 in the pause screen when you hit reset, and then unpause the game. Have a rule in an actor in the regular scene, and then have it triggered when the game.resetScene is 1, then reset the scene, and change the attribute back to 0.
That should work for your problem.

Anyone else know what way is more efficient for the pause and/or level success screens?

Thanks!

-Josh

GoAppSoftGames

if you have an android just test it there it works even if its iphone

VoidedSky

@GoAppsoftGames
Thanks, but I don't have any android devices.

VoidedSky

Nobody?

GLGAMES

Maybe with the table implementation you can reset easier. Have a table to store all starting values of your stage or all stages. So every stage it just reads off the value stored on your table. As for scoring or other data you can choose to use another table to store them and save them after each stage. So you always have one untouched table with original values in it.