-snip-

[nothinggas]

[RSDuck]

hi,
first of all sorry for the later answer I am a bit lazy in regards to answering emails, etc.

Unfortunately I can't help you much. I thought I managed to get the random crashes under control, but seemingly I didn't. I also haven't touched the code in quite a while and the saving/loading/world generation was always a bit problematic.

I'm glad that you wrote that the image of a crash comes from google, otherwise I could have gone hunting shadows. The crash info contains vital informations which could have been used to find the source of the crash. These are the only way to get atleast some pointers where to search, for these hard to predict crashes.

The only positive thing to say is that you can type in /d to display/hide debug informations including your current coordinates.

[RSDuck]

My apologies for the late response, again.

So does this mean the developments for the game are ceased?

yes

you not upload sort of an emergency patch with an autosave feature to somewhat eliminate the problem of crashing?

unfortunately no, since I have no clue where to search, nor to be honest the motivation to do so. You have to know that saving isn't something that only happens when you close the application. Instead the world is streamed from and onto the SD card, which means parts of the world which constantly loaded from SD card or saved to it in case they were modified or newly generated. The crash might be related to the saving itself, which wouldn't surprise me, since it's always been the most fragile part of the code. Then autosaving would bring no advantage since the world file would be corrupted.