ModusCreateOrg / ModusCreateOrg/creative-engine

BMapPlayfield save state

Open
#171 0 comments 0 reactions 1 assignee View on GitHub

@mschwartz is already working on this.

Since Aug 2, 2019.

Dominant language
C
Stars
20
Forks
7
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.