Everyone and even non-programmers muggles have faced more than once the antedilvian problem of which action to do first in a row of two, each one interconnected tightly with the other ( « chicken or egg » sentence).
In my case it happens with the mission system, composed of two parts:
– a mission manager, interpreting and acting/linking missions
– a mission object, to store the mission infos (text, references for checks, …) and to link the references to the next mission(s), it can allow for randomly generated « basic missions » like bounty hunting, cargo hauling,…
The question on which one to begin is in my point of view like a key and its lock.
I decided previously to store the missions information in several mission files written in a XML-like fashion, using keywords I’ll detail the different checks to perform, then I’ll display the text of the mission and the possible choices ( yes/no/next ), each one pointing on the next mission.
I’ve decided for now to try an « downside-up » approach, designing the needed infos and then the manager to use them.
More news here as I dig into the problem 😉