jukkae
commented
5 years ago Mission should have title and description. They should subscribe to events and track their own progress based on events. Furthermore, failure conditions should be implemented via events as well. In this scheme, missions don't need to poke around all over the place, hardcoding can be kept to a minimum, and missions don't inherently care about how a goal is achieved, but they can, if it's useful.
End condition, rewards, description need to be explicit. Most likely, the easiest way of getting missions initially is via talking. Also, completed missions should be listed.