Salem

We recognize the server is Timedout. Its not responding to commands in the exact way I would expect and want.

For the record, a vast majority of the time a bug is easily squashed and a clean restart is a fairly simple thing. I'm not expecting that this is anything too far out of the ordinary, but there are some dangers with forcing a restart before a full investigation is concluded which requires some debugging tools a bit more sophisticated than a typical quick-peek from yours truly. In the spirit of being 1000% safe, I'm going to leave this down until we can get somebody to verify we are in the clear to restart without jeopardizing any data integrity.

Its also a major holiday. So please allow me some patience, and use this time to maybe go update the public wiki with all the new stuff you found so far!

Also in the future I will make it a priority to be able to do some more advanced debugging from my remote computer so I can have the confidence to restart this for you in a more timely manner.

JohnCarver wrote:We recognize the server is Timedout. Its not responding to commands in the exact way I would expect and want.

For the record, a vast majority of the time a bug is easily squashed and a clean restart is a fairly simple thing. I'm not expecting that this is anything too far out of the ordinary, but there are some dangers with forcing a restart before a full investigation is concluded which requires some debugging tools a bit more sophisticated than a typical quick-peek from yours truly. In the spirit of being 1000% safe, I'm going to leave this down until we can get somebody to verify we are in the clear to restart without jeopardizing any data integrity.

Its also a major holiday. So please allow me some patience, and use this time to maybe go update the public wiki with all the new stuff you found so far!

Also in the future I will make it a priority to be able to do some more advanced debugging from my remote computer so I can have the confidence to restart this for you in a more timely manner.

Does it help if ppl say what they where doing the moment the server went down ?

For me, right as i right-clicked the executioner to deliver a scalp, the server went down

I was riding around in a majestic horse that I borrowed from someone else. I might have got stuck in a barrel or that could be the side affect of the sudden downtime.

I was working on my crops then couldn't move. Hey John, these things happen no problem. I am sure you and your team will get this resolved as soon as you can.

First patch - first crash
I hope you solve this problem fast.

Hopefully there are numerous of backups, if it may come to that.

*UPDATE*
The execution list got full. Somebody tried to give him a scalp that met certain criteria... and not other criteria as he only displays the (Top 10). That is fixed, but work is still being done to ensure minimal collateral dmg from the crash.

JohnCarver wrote:*UPDATE*
The execution list got full. Somebody tried to give him a scalp that met certain criteria... and not other criteria as he only displays the (Top 10). That is fixed, but work is still being done to ensure minimal collateral dmg from the crash.

Damn you alloin . Why you gotta kill so much

solitude_stalker wrote:

JohnCarver wrote:*UPDATE*
The execution list got full. Somebody tried to give him a scalp that met certain criteria... and not other criteria as he only displays the (Top 10). That is fixed, but work is still being done to ensure minimal collateral dmg from the crash.

Damn you alloin . Why you gotta kill so much

I was testing stuff

JohnCarver wrote:That is fixed, but work is still being done to ensure minimal collateral dmg from the crash.

Just as long as there is no hnh style area nukes.