akkadius scripts + static zones

[NostalgiaEQ]

Originally Posted by Darkscis

If you are using Akka's script you just edit the "t_start_server.bat" file and change zones="X" to however many you want.

The benefit's to running extra? More people can be in different zones at once. If there are no zone processes available people will try to zone and receive an error message, then end up at the safe point of the zone they were already in. The don't consume a lot of resources and it definitely pays to have more than you need, but basically - balance it around your population.

Beautiful that is exactly what I needed to know. I am assuming I should also change "peq" or "zone" entry in the launcher table in the database to my elevated number as well but not sure which does which there yet. Also there is a win_server_launcher.pl file and it says if there is a zones_to_launch statement in the .bat file then it will launch 10 zones. I assume this is if you don't set it in the .bat file but I changed the pl file too just in case.

[Uleat]

I'm not sure that I understand how Akkadius's scripts operate..but...

I do believe that they bypass the use of eqlaunch.exe.

If that's the case, then I'm not sure how much the db table values come into play.

[khalathas]

Uleat, then can they not be mixed?

@echo off
cls
echo *** CLEARING OLD LOGS ***
del "logs/zone/" /q
shared_memory.exe
start perl win_server_launcher.pl zones="30" zone_background_start loginserver kill_all_on_start

pause

echo starting static zones
start eqlaunch antonica
start eqlaunch faydwer
start eqlaunch odus
start eqlaunch luclin
start eqlaunch kunark
start eqlaunch velious
start eqlaunch ykesha
start eqlaunch planes
exit

[Uleat]

Don't ask me..not my script :P

Just going off of comments I hear in chat..though, your post would indicate otherwise.

[Akkadius]

Really should just do dynamics + long shutdown delays. Statics are unecessary

[khalathas]

I completely did not realize until now that the shutdown delay was a per-zone setting! Holy crap *runs off to do like an extra 70 dynamic zones, then increase shutdown timers on them*

[jpyou127]

Cool, I learned something new today!! Shutdown delay!

Any recommendations for length of time? 1-2 hours?

I have a default value of 5000, is this in seconds?


Celestial

[Uleat]

years.....

[jpyou127]

LOL

60000 looks like its 60 secs.

[N0ctrnl]

If you don't want people to be able to cycle loot on NPCs, the only way is to do static zones. Otherwise it will change every time the zone starts backup. For that reason I do statics on raid zones. Even with a long delay, loot still changes when the zone boots up.

[Akkadius]

Apparently no one read my post on the first page explaining all of this

[Shiny151]

The disadvantage to dynamic zones is this:

If you have a named mob you want to kill that has a minimum chance to spawn every four hours that also has a placeholder with a zone shutdown delay of one hour, you could essentially check the zone every hour in the hopes that the named is up without having to kill the placeholder. Granted, the zone has very little foot traffic to prevent the zone from staying open/active.

With a static zone, let's say the placeholder is up. It will STAY up indefinitely until someone kills it. Thus not allowing lazy players to cycle-check the zone.

The solution? You'd want the dynamic zone shutdown delay to match or exceed the longest timed mob that has a placeholder in the zone in order to behave more static and live-like. I know it was an example, but an hour shutdown delay won't always do it for the crafty loot-seeker. Which basically means you'll need a custom shutdown delay for every zone you don't want this happening in.

[Akkadius]

Originally Posted by Shiny151

The disadvantage to dynamic zones is this:

If you have a named mob you want to kill that has a minimum chance to spawn every four hours that also has a placeholder with a zone shutdown delay of one hour, you could essentially check the zone every hour in the hopes that the named is up without having to kill the placeholder. Granted, the zone has very little foot traffic to prevent the zone from staying open/active.

With a static zone, let's say the placeholder is up. It will STAY up indefinitely until someone kills it. Thus not allowing lazy players to cycle-check the zone.

The solution? You'd want the dynamic zone shutdown delay to match or exceed the longest timed mob that has a placeholder in the zone in order to behave more static and live-like. I know it was an example, but an hour shutdown delay won't always do it for the crafty loot-seeker. Which basically means you'll need a custom shutdown delay for every zone you don't want this happening in.

Not really a disadvantage of shutdown delay functionality itself than it is configuration of your own server

[NostalgiaEQ]

Originally Posted by Akkadius

Not really a disadvantage of shutdown delay functionality itself than it is configuration of your own server

That's very cryptic but what I think your saying is a server should be designed to not have unused zones. But with a live like or classic like server this could be a problem. Also it isn't very classy when you zone into a place with a boat and the boat is always waiting at the dock. For me I feel a good solution is dynamic zones and an 8 hr blanket zone reset time which should prevent any mob cycling but would still have the boat issue. I'll survive.

[dburg30]

So if I change the zones="xx" in the bat file, after a certain point in the one server launcher window, the zones will continue to count up.. ie: if I put 100 in the zones=. It will count up to 100 in the windows server launcher, but will then start counting again, but not from 0/100, somewhere higher, but when it gets to 100/100 it will restart again.. Is there a limit to how many zones it will load? my memory is not running out. Does there need to be a delay somewhere that it loads them?