Описание игры и намётки архитектуры
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
|
||||
# Scenes
|
||||
|
||||
The project should have two scenes. First, `loader` scene. It should contain
|
||||
all module initialization, and then should proceed to `lobby` scene.
|
||||
|
||||
`lobby` scene should contain main game UI and all objects needed for game
|
||||
functionality to work.
|
||||
|
||||
# Modules
|
||||
|
||||
## Savegame
|
||||
|
||||
Savegame module manages saving and loading user's progress achieved throughout
|
||||
the game. All in-game currency values, passed levels (if any) and so on.
|
||||
|
||||
Savegame module should have a method for triggering of saving current game state.
|
||||
It should have several classes inside it, each handling its own part of the save.
|
||||
When asked for save, it should enumerate all those and put all data into JSON
|
||||
where key is class name and value is an object with data, produced by that class.
|
||||
|
||||
Loading of the game should occur on game start and be performed in reverse order -
|
||||
parse JSON, then enumerate all classes and trigger every of them to parse its data.
|
||||
|
||||
Reference in New Issue
Block a user