Return to repo list


Tactical RPG written in python, using pygame.
Return to

commit 3a47bd203a0f22a6ce78c6e1daca28917c694690
parent 4d07565d741a1384ba1ea7320ba9abf7be4c67f1
Author: Erik Letson <>
Date:   Wed, 16 Sep 2020 00:29:47 -0500

Todo comment regarding jsons and saves

Diffstat: | 7++++++-
1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/ b/ @@ -3,7 +3,12 @@ from src import game ## GLOBAL TODO: # 1. Decide on final method for managing the cursor. Should it be managed by EntityManager? BoardManager? GameInterface? A seperate manager object? -# +# 2. The JSON loading methods are all over the place. Need to decide about whether or not things like units should be defined in individual JSONs and +# referenced by a big meta JSON or if there should just be many individual JSONs for that. One problem with it is that when saving is implemented +# there will have to be a way to distinguish between the basic versions of a unit and the ones that are leveled up. Maybe JSONs are not the correct +# choice altogether. Perhaps there should be one huge save.json file for all changes. If that is so, then there could be several JSONs in the dir +# located at data/json that are loaded first, then the save.json file is parsed by a save-load subsystem and any changes are applied, at which point +# the game would be in a loaded state. This seems the ideal solution, and it can be put off a bit. pygame.init()