|
|
Post by Amairgen on Jan 13, 2014 6:57:05 GMT -8
Hi,
As some know, others forgot and more discover . . . I will be away for the next six weeks. I will drop in on the forum and the game periodically from my laptop to check for messages etc.
The Server has been set to run and to auto recover from any power outage problems. Based on the past three years experience it should remain stable and run fine. If I discover a problem when I check in I can remotely try to solve it but nothing new will be added or revised while I am away.
If a new player walks into our world, please be kind. I will be thinking of you on my travels and if I find interesting things I will try to share them here.
Thanks everyone - Walk in sunshine!
*bows*
|
|
|
|
Post by Ravenclaw on Jan 13, 2014 15:24:56 GMT -8
Enjoy your vacation and don't worry, I'm sure things will be just fine.
Sent from my Nexus 5 using proboards
|
|
|
|
Post by karin on Jan 24, 2014 17:30:51 GMT -8
anyone else not able to log in? still unable to log oh well!
|
|
|
|
Post by barak on Jan 25, 2014 1:55:18 GMT -8
I am unable to log in thought my computer was playing up
|
|
|
|
Post by Amairgen on Jan 25, 2014 23:26:12 GMT -8
Sorry!
As you know I am in Asia (currently in Myanmar - 15 hours ahead of the Server and on a Dial Up connection).
I just noticed the posts above (thanks for the 'heads up') so I remotely accessed the Server and restarted the game. This is the first time the game has dropped in a long time.
The computer hosting the game was running 'rock steady' but something in game with the Merlin's Quest had caused a null reference exception that made the game hang up.
All should be good now as long as the Merlin Quest scripts do not repeat the error. I will examine them when I get home at the end of February. Mean time I will continue checking in once a day to see if any problems pop up.
Thanks for the patience folks. I know how frustrating that can be (been there did that as a player).
Cheers
|
|
|
|
Post by karin on Jan 26, 2014 8:08:53 GMT -8
up and all good tyvm!
|
|
|
|
Post by Lone wolf on Jan 26, 2014 13:04:26 GMT -8
Spent all Saturday at work doing nothing. Switched with a co-worker so i could harvest some metal  A little advice, if i may... There is crashguard.cs that keeps server rebooting after a critical error, but there is a little bug, that should be fixed. Crashed server window is not closed by default and restarted server keeps trying to listen to the port that is already in use. So all you need to do is close crashed server: under Restart section just before new process is about to start just add Core.Process.Kill(); |
|
|
|
Post by Amairgen on Jan 26, 2014 14:49:28 GMT -8
Thanks Lone Wolf - nice tip. I will look at it when I get to a place with a better connection.
*Smiles*
|
|
|
|
Post by Amairgen on Jan 28, 2014 17:25:48 GMT -8
Okay - I was able to test and implement Lone Wolf's suggestion remotely from a beach in Thailand *sorry to rub that in - grins*
If this works as it should, the server will restart itself after a crash caused by some in game event. I will check the crash logs (if any) when I get home to debug any errant code.
Thanks Lone Wolf -and sorry to all for the inconvenience.
Cheers
|
|
