Zone Reset Quest on a Timer

[AndMetal]

Originally Posted by trevius

The first bug I have found so far is that one of my quest NPCs in PoTimeB was shouting that Crushbone was going to reset and it reset PoTimeB instead. The zone resetting NPC in potimeb is definitely only set to reset potimeb and only set to warn that it is shutting down that zone. Crushbone has a completely different quest with it's own spawn that shouts about Crushbone being reset.

You could always make just 1 quest, in say the plugins folder, and use the variable $zoneln to make the quest dynamically say the zone's long name:

#############
#Quest Name: 4 Hour Zone Reset Script
#Author: Trevius
#NPC's Involved: Storm Haven
#Items Involved: None
#############
###NPC 1
#Name: Storm Haven (Or whatever your server name Is)
#Race 127 (invisible man), Texture of 0, Size 1, gender of 0, body type 11
#Location: 0,0,-999 of the Nexus
#level: 100
#Type: Quest NPC that resets the zone
#Loot: N/A
#############

sub EVENT_SPAWN {
quest::settimer("reset",14400);
quest::settimer("warning1",12600);
quest::settimer("warning2",13200);
quest::settimer("warning3",13800);
quest::settimer("warning4",14100);
quest::settimer("warning5",14280);
quest::settimer("warning6",14340);

}


sub EVENT_TIMER{
  if ($timer eq "warning1"){
    quest::stoptimer("warning1");
    quest::shout("$zoneln will be restarting in 30 minutes.  Please zone out before that time.");}

  if ($timer eq "warning2"){
    quest::stoptimer("warning2");
    quest::shout("$zoneln will be restarting in 20 minutes.  Please zone out before that time.");}

  if ($timer eq "warning3"){
    quest::stoptimer("warning3");
    quest::shout("$zoneln will be restarting in 10 minutes.  Please zone out before that time.");}

  if ($timer eq "warning4"){
    quest::stoptimer("warning4");
    quest::shout2("$zoneln will be restarting in 5 minutes.  Please zone out before that time.");}

  if ($timer eq "warning5"){
    quest::stoptimer("warning5");
    quest::shout("$zoneln will be restarting in 2 minutes.  Please zone out before that time.");}

  if ($timer eq "warning6"){
    quest::stoptimer("warning6");
    quest::shout2("$zoneln will be restarting in 1 minute!  Please zone out NOW!");}

  if ($timer eq "reset"){
    quest::stoptimer("reset");
    quest::shout2("$zoneln is being restarted right now!  It will be back immediately, so you can log back in right away.");
    kill SEGV => $$;}
}

Should save a ton of headache if you want to make each zone the same. And if you don't, you should be able to create the individual quests for the specific zones, while still keeping the main one in plugins.

You may also notice I removed "$counter = 0;" because it doesn't seem to do anything in the script.

Originally Posted by trevius

When I first put the quests in, I had all of the timers set to the same names in each zone and I think this may have been the problem. All of the timers were $reset, $warning1, $warning2, etc. Now, I have renamed each of them in the quests for each zone. For example, Crushbone timers are now called $cb_reset, $cb_warning1, $cb_warning2, etc. I will test and see if that clears up my problem.

If I'm not mistaken, if you define the variables at the beginning of the script (before the subs) using my (so my $reset, my $warning1, etc), I believe it will give you the desired result without having to create a script for each zone.