GillianYue
commented
4 years ago Quest is a class, can be found in QuestLoader. The csv file is now officially in charge of storing ALL quests, and they will be loaded in by the loader, and after parsing the loader will hold on to a long array of Quests. The title scene will wait for questloader to be done parsing and Save/Load to be done loading quest progress then compare the two to figure out what to display.
Quest (loader) is there, till need to work on S/L and compare
Currently, quests are loaded in at the start of title scene via one single csv file.
Let's think about how we should approach this. If this is handled, then the storage of other kinds of data can follow a similar pattern.
So the quests are universal in the sense that there's a place where one copy of ALL quests ever existent is stored, and each player stores their own progress of what's completed and what's not, what's available and what's in line of getting done.
And so I think that during title scene load we should check for all conditions and compare between the "official" quests and the player's progress and make the corresponding changes (some quests made available b/c of new conditions, some quests completed compared to past run; etc etc.)
a quest file ("questStatus.dat") that stores progress of quests
think about when to write to that file and when to load --> loading is simple, during title scene load; I think writing is just writing whenever changes occur (just write that changed part to file with a specified function)
a huge compare function that covers everything