For the levels themselves one option would be to create a class Level. And make different instances of that class for each level. This class could then keep track of all the information you want. So in a circumstances that you were to leave and then return to an area the information would still have been saved.
As to how you organize keeping track of the different Level Instances that is up to you and the game you are making. If the areas represent sections of a map, a 2d array would allow you to access each Instance by its position on the grid. If the areas represent separate levels entirely than a simple array would do. If you know before hand how many areas there are then creating and naming each one on initializing the game might be preferable.
I guess we just need more information about your game to give you more advice. But yes I agree with the above, definitely keep menu states and levels separate. You will avoid a lot of headache if you do, trust me.
Hope this helped.
Munchkin9Member Since 14 Nov 2007
Offline Last Active Feb 04 2014 10:11 PM
- Group Members
- Active Posts 72
- Profile Views 1,170
- Submitted Links 0
- Member Title Member
- Age Age Unknown
- Birthday Birthday Unknown
Munchkin9 hasn't added any contacts yet.