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

BMapPlayfield save state #171

Open
mschwartz opened this issue Aug 2, 2019 · 0 comments
Open

BMapPlayfield save state #171

mschwartz opened this issue Aug 2, 2019 · 0 comments
Assignees

Comments

@mschwartz
Copy link
Contributor

Currently, BMapPlayfield loads its data as described in the "tilemap".files.txt file. The attributes and tile indexes are combined so the attributes (code, "wall" bits) into TUint32 per position in the map.

This allows the game logic to fiddle with the attribute bits, or modify the map (e.g. playfield animation), while being able to reload the map and have none of those changes made.

In a game like modite-adventure, you may want to enter a dungeon and then exit, and then enter it again. You probably want the dungeon state to be the same as when you left it.

In order to persist the dungeon state, the BMapPlayfield class needs to be able to save its state to persistent storage (e.g. file system in flash), and then be able to load from the persisted data.

@mschwartz mschwartz self-assigned this Aug 2, 2019
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