- Joined
- Feb 13, 2009
- Messages
- 3,303
- Reaction score
- 651
Very nice ronny, now if only there was a way to edit aipolicy other then maybe hex...
Yes that would be cool to have an AI editor
Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!
Join Today!Very nice ronny, now if only there was a way to edit aipolicy other then maybe hex...
With this aipolicy.data Coredash with holy hall hits the 500 000, please help fix this problem
sorry, is same problem.What is it Vitor? "I have some problem"... so what's the problem?
It isn't "same"?
With this aipolicy.data Coredash with holy hall hits the 500 000, please help fix this problem
Does it still kickout the big damage when you killed all mobs before him ? I remember there was a anti bot thing in there, that prevent from farming. Check your quests when you are in there, there must be a quest that tells you how much monsters you have to kill before you may try the boss.
Does it still kickout the big damage when you killed all mobs before him ? I remember there was a anti bot thing in there, that prevent from farming. Check your quests when you are in there, there must be a quest that tells you how much monsters you have to kill before you may try the boss.
That's it, you're right i was wrong, i figured out how tasks are linked to ai control blocks: they use a "dummy" monster
The following example will show the complete pipeline for the Twilight Temple Requiem of Wraith task:
- first we look into the task for opening TT Requiem of Wraith, it's the task with id 9032 here we find the creature builder id 202
- now we look into npcgen for the creature builder id 202, here we find a connection to the npc trigger link 209
- the npc trigger link is associated with a "dummy" monster, this monster has only one usage: it executes the attached ai control block when activated by the task, i'll call it "task control monster". I'm sure some of you have noticed double coordinates on npc's when using command d_showpos, these coordinates belong to the invisible task control monsters. In our case the trigger activates the monster with id 14455
- now it's time to lookup in element list 37 for the task control monster 14455 to find the ascociated aipolicy control block, here it is 147
- at least we can look in aipolicy for the control block 147 to see what it does...
Finally we have figured out how task 9032 is linked (indirectly) to the aipolicy control block 147