“loadedincreative” is set to 1 as soon as you select creative, not load it.

This bug report is private due to how long my rambling is, but I ramble in good faith. I want better for everyone.

The “achivements disabled” popup does not properly state what will disable a world. When in Edit and switching from survival to creative, the popup simply states that creating a world in creative disables achievements for that world. Yet, this world was not created in creative.

My control flow: have a survival world ~> edit ~> change to creative ~> warned about creation of world ~> duplicate world, creating a Creative copy ~> back arrow.

Result: loadedincreative == 1 on both worlds, even though one world was never loaded in creative.

My reasons for this particular case: longer term survival world, day 200 or so. 2 achivements left in the game. I die in a hole in the end dragon fight (i hobbit holed myself to let the dog out) assuming I could tank the contact damage, but the dragon got a breath shot underground, so I died a block below the surface, but not knowing coordinates.

~> Edit ~> set to creative ~> duplicate ~> back arrow ~> find my death location ~> i set back original world to survival once i see “achivements disabled” ~> achivements permanently disabled.

Maybe it’s not a bug, but at a bare minimum, the wording on the Achivements Warning Popup needs to be reviewed. Additionally, the variable name loadedincreative suggests that this actually is a bug.

Suggested Fix:

1. Update wording on the warning to include “setting world game mode to creative”

2. Don’t uptick loadedincreative unless the world is actually loaded in creative. Y’all currently just use 0 and 1, but maybe y’all could impliment this logic:

if (world is loaded in creative):

loadedincreative++

if (loadedincreative):

no achievements

1. I assume that the second if statement exists, intuitively speaking. If instead of hard-setting loadedincreative = 1 (LIC), if you just uptick it every time, then once LIC != 0, achivements will still get disabled forever.

2. On the subject of integer overflow, should a user load their world 65535 times to reset their integer to 0 (if they are lucky and it is a uint16_t)

3. The proposed fix will have the conditions of achivement disabling more correspondant to descriptions and expectations found in game, online, and of old times. (On xbox 360 minecraft, achivements would not disable until you did in fact load the world in creative)

4. The proposed fix will thus allow for a greater understanding and cohesive experience for Minecraft’s users, in particular the achivement hunters.

5. I did not load this world, (did not ping the servers) so I was lucky and able to successfully set loadedincreative = 0 and reenable achievements, but after this experience, I know other gamers are out there who are unsuccessful. I’m lucky I’m an adult with a desktop PC and knowledge, but not everyone is.