World Crash Rebooter

[nightsta69]

try double clicking on '1' or 'default'.
it only loads them when you double click on them - allows multiple rule sets to be used / managed.

yep that worked, didn't know to double click lol

so the server tender app is closing? sounds like the app is gaining focus and catching the alt + f4 closing keystrokes.
You might want to do what i suggested earlier - open my source, find 'Private Sub BroadcastNow', change broadcast3(msg) to broadcast1(msg) and recompile.
That will use sockets instead of telnet and sendkeys.

will try this probably tonight, after I get some sleep.

NP. sorry it was confusing! This was built before the UCS had taken effect and the separate mailserver was removed.

its no biggie. just wantin to help get it up to date

it's a good skill to learn and not really that hard.

yea i'm workin on it, slowly lol.

manually closed meaning...? (the english language is open to such lovely interpretation!)

the app will close any crashed apps, it doesn't restart them if they crash (world takes care of re-starting zones that crash.)

IE clicking the x in the corner of world and eqlauncher. but you cleared that up.


if I come up with more ideas to help improve this I will definitely let you know. I can always come up with the ideas, but I just can't code for crap lol.

[nosfentora]

Always on the lookout for ideas! =)

[nightsta69]

1. another problem I found. if you have a pre-existing peqdb-revxxx.sql in your database SVN folder, that is already unpacked (IE unzipped and placed in the peq-db SVN folder). when it drops the tables, it will source the previous db version in first, then it will try to source the new version in, but since the tables already exists from sourcing the old sql, it will come up with an error. maybe you could have it delete the new peq-db.sql after it sources so that wouldn't be a problem?

2. i've been watching the auto rebooter for the past several days, and I don't believe its closing out the old world/zone exe's before starting new ones up, when you have it set to auto reboot every 24 hours.

3. when it goes to shut down, it doesn't broadcast "30 mins til server reboot" or any subsequent messages at the correct times. all it does is broadcast the 30 mins, then immediately kills the server. i've noticed that several times, and normally it does this about 4-5 mins early. dunno if thats intended or not. /shrug

think thats it for now. hope this helps you fix it up.

thanx

[nightsta69]

ok found an update to #2 of previous post. what its doing is closing everything but the eqlaunch down, and then starting up another eqlaunch, and it keeps adding and removing launchers to world. still doing debugging on it atm, wish I could just edit my posts cause this mass posting just doesn't seem right lol.

[nosfentora]

yea i just noticed that - i dev'd it in xp and did some quick tests with vista and it seemed to work.

i think it's not working for you cuz serv 2008 is vista based (or vice versa).
you might try changing the shutdown option from "send ctrl+c" to "kill processes directly"

see if that works for the time being.

As far as the old sql's go, i need to look at the code again and see how it searches/sources. i think you may be right as it might be looking for the 1st .gz /sql file it finds.

thanks for the heads up!

[nightsta69]

just to let you know, killing the process directly fixed the issue of eqlaunch not shutting down. I have another feature request tho if you don't mind. could you make an option to lock world when it restarts? cause one of the things i've noticed is when world restarts its doesn't retain its locked status. my server is still in development, and I don't want people coming on until I release it from alpha stages. plus I would think that would be a good feature for the restarter to have.

thanx

[nosfentora]

That's set in your eqemu_config.xml file

change

<!-- Server status.  Default is unlocked -->
        <unlocked/>
        <!-- <locked/> -->

to

<!-- Server status.  Default is unlocked -->
        <!-- <unlocked/> -->
        <locked/>

and set your status in your account table to >= 250 and you can log in.
anyone else you want in, you'll need to set their status accordingly.