|
Well, you can keep a list of when each list is set to be needed. That seems like it would overcomplicate things. I go with a global list personally.
Interestingly, that's how my current system works, but in my next I think I'm going to queue everything. There's a certain benefit to having almost everything executing from the same part of the code.
I would have thought that talking, combat, spells, regeneration are precisely the things that an event system is there for? These all represent acts that take place some time in the future so it makes sense to create an event for them and trigger it when necessary. It's only ever going overboard if you complicate things, and I'd think that moving these concepts into an event-based system would simplify them in several ways.
|