Quote:
Originally Posted by Akkadius
The zones that get launched from my perl based launcher are purely dynamic.
You can achieve most of the 'static' behaviors by keeping zones dynamic and adjusting your 'shutdowndelay' in your zone table to be something that suits your needs.
The shutdowndelay is in milliseconds (1000) = 1 second.
To keep a zone up for, say an hour, you'd set the shutdowndelay to 3600000.
Once a zone has been booted, it will take a full hour to shutdown and go back into the dynamic pool. Only at this time will the zone flush corpses and things of that nature. Spawns and named are in the database so those timers are going to stay in tact regardless - BUT - if you have a low shutdowndelay and pure dynamics, plays can walk back and forth on zone lines to force a spawn cycle for a named that hasn't been killed or has an expired timer.
The perl based launcher is far more resilient and speedy, but does not support statics.
If you want to run statics you can run them in your batch on your own like so
zone.exe soldungb
zone.exe everfrost
Or you can do as mentioned in the thread before and set your launcher_zones table and map all of your statics and run eqlaunch.exe in parallel with the perl launcher.
To give you an idea, EZ Server runs pure dynamcis using the above methodology I explained earlier to be leaner on resources.
Hopefully that clears up some questions.
|
Definitely clears up a lot. I'll just trim my batch file down to the start eqlaunch <launchername> segment, and run it in parallel then. Thank you Akkadius!
Edit: removing my own launcher called Dynamics from my segment of the batch file since your perl script has 30 dynamics already. Perfect! Works like a charm!
Threaded Mode
