Quote:
Originally Posted by Akkadius
Natedog,
To avoid this you can simple set your shutdown delay on your zones:
Code:
UPDATE `zone` SET `shutdowndelay` = 900000;
This will keep zones up for 15 minutes so players can't just zone out and back in to force the zone to completely repop. |
This seems to work I think.
Zone is available for 30minutes after completion of the Adventure. (which the rulevalue for this timer does nothing unfortunately since the code to back it up was never implemented)
I left 2 characters inside the instance 2 minutes before the zone was about to kick us out.. I killed a few of the static mobs and made sure they left corpses inside Instance ID 31.
When the zone kicked us out I used 2 other characters to request the same exact adventure and zoned in right away.. they got Instance ID 31 .. (same instance)... however all the mobs were back and the corpses were gone and the adventure was able to be completed in this "new" instance.
Zoning in and out did not repop the boss when the instance was in the 30min shutdown mode.
So this seems to have fixed it.. I was trying to overlap the instances but I could not get them to overlap. (gonna try with a different zone later like sorvani suggested might happen)
edit..
Tested with 2 different zone... and it seems to work just fine always sends you to the correct instance / zone.
Threaded Mode
