Wierdness using quest::depop in EVENT_SPAWN
Trying to code around the "lockout" in the coirnav event left an interesting error.
The Guardian_of_Coirnav should spawn when the event is ready. No problem, really. One method, if the event isn't ready, then depop the trigger mob. A simple global check, I thought: Code:
sub EVENT_SPAWN { http://www.imagebucket.net/bucket/is...uardianWTF.jpg Basically the extras were targettable on the client, but using either #depop or #kill on them resulted in "No target" Errors. When you used #listnpcs Guardian_of it only showed ONE guardian spawned (as highlighted). Okay, not the best move to do it inside the EVENT_SPAWN block, so I changed the depop method it uses. Lesson learned, but still strange. I'm left wondering why depop causes this "ghost" to appear on the client when inside a EVENT_SPAWN block. |
All times are GMT -4. The time now is 01:10 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.