I've been thinking about this but don't have any great answers right now.
Anyway:
-I would create a separate parser implementation for your quest system. Piggybacking on existing systems is a bad idea because as you can see the internals are subject to pretty broad change.
-I think we need to look at how we pass information in a standard way (right now we have a ton of variables of different types which is kind of messy).
-You can get the event name from the event code we already pass so I'm not entirely sure what you're asking for there.
|
Threaded Mode
