[04:05] Oh... [04:06] You on the favors list? :P [04:06] Those who can see the threads? :)) [04:06] Well, here goes... [04:06] Based on somethings I've tried to implement, [04:06] there should be an GlobalAuthority availble for Quests [04:07] (btw, when I say Quest I mean Events aswell, because you can successfully implement events and other kinds of AI usign the current poor QuestJython implementation) [04:08] The GlobalAuthority should be able to handle, among others: [04:08] install() - setting up the env for the quest [04:08] like spawning folk or mob NPCs and such [04:08] uninstall() - for cleaning the environment [04:09] it should be able to handle reports [04:09] for example return a list of L2PcInstances that took the a specific Quest. [04:10] Further, the current QuestState system is really messed up and hard to get. [04:10] There should be a cleanup... [04:10] Maybe use a simpler system. [04:11] Or rather document it properly... ^^ [04:11] Many of the classes in the application should support listeners [04:11] for example: [04:13] L2Character: onDeath(victim) (like the current onKill implementation called when the character dies), onKill(killer, victim) (called when this character killed another), [04:13] L2PcInstance: onEnterWorld(player) - highly useful for restoring some event data [04:14] L2PcInstance: onEnterArea(player, area) [04:14] And well, I should sleep on it and come up with more examples. [04:14] The listener system should not be restrictive... [04:15] That means if I want to implement support for a new event, I should be able to do that with Java easily. [04:15] Am I talking to myself? :D [04:15] Must I send EOF when I'm done? :))