Encrypted Debug Loc for hunting down Syncs and Fatals

[Ivan Eres]

We all know the Syncs and Fatals that we've grown accustomed to over the years.

I understand that it is hard to track them down because there could be many issues causing them.

That's why I propose to add a log similar to the damage log that was introduced in 2.2, but for tracking down Syncs and Fatals.

This log should contain internal debug messages to know where exactly in the code the Sync or Fatal happened.

To avoid abuse by malicious players that log should be strongly encrypted by the client, so nobody can read it.

This debug log could also be accompanied / replaced by a memory dump or crash dump if it helps the devs.

This way we could find out what's causing the Syncs and Fatals.

Regards

[Kane Gregory]

[all the stuff u said]

A great idea. But I think it's an integrated future like:

public void timerActionEvent(Event e) {
int random = (int) Math.random()*1000;
if(random > 900) {
throw new FatalErrorMessage();
System.exit(0);
}
timerTask.delay(Math.random()*6000);
}