search

RSDuck / craftus_reloaded

A second attempt at a homebrew Minecraft clone for 3DS
Other
53 stars 9 forks source link

[BUG] [Gamebreaking Glitches] Crashing, Teleporting glitch and infinite void. #15

Open L0ST5ILVER opened 5 years ago

L0ST5ILVER commented 5 years ago

The game will often cause random crashes, the longer you play the more this seems to occur. The worst part about this is that you will lose all progress from that session (Lost about 40 minutes of work) image This image was taken from Google, this is not a crash from Craftus, but this is what the errors look like, exactly like this.

The second glitch is this: When you press the HOME button while playing in a world, opening the game again will cause you to teleport so far away that you will never find your spawn again.

The third and final glitch is less of a glitch and more of an overlooked flaw. To put it simply, if you fall far enough into the void you basically lose your world forever.

Some counters for these issues to help fix them: (I hope they are taken into account)

Adding an auto save feature Publicising certain commands (Such as /spawn or /home to return to the original spawn point) Readding the Coordinates on the bottom screen (And or a map) Once you fall far enough into the void, you will be teleported about 40 blocks above your spawn point and drop back to safety.

I hope this thread is seen and taken into consideration, I know this is only meant to be a small, PoC game, but I just want the game to be fully stable so the simplicity of it can be fully enjoyed!

Kind regards, -L0ST

RSDuck commented 5 years ago

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.

L0ST5ILVER commented 5 years ago

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.

Thank you for the response. So does this mean the developments for the game are ceased? Could you not upload sort of an emergency patch with an autosave feature to somewhat eliminate the problem of crashing? Since that would make the crashes more of inconvenient rather than potentially devastating.

Kind regards, -L0ST

RSDuck commented 5 years ago

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.

L0ST5ILVER commented 5 years ago

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.

I see. Thanks for the response. It's a shame nothing can be done though. Regards, -L0ST