[MC-8559] Having cheats enabled shows always "Cheats: False" in the crash report Created: 27/Jan/13  Updated: 03/Oct/21  Resolved: 03/Oct/21

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w04a, Snapshot 13w07a, Snapshot 13w09a, Snapshot 13w09c, Snapshot 13w10a, Snapshot 13w10b, Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Snapshot 13w17a, Snapshot 13w18c, Snapshot 13w19a, Snapshot 13w21b, Snapshot 13w22a, Snapshot 13w23a, Snapshot 13w23b, Snapshot 13w26a, Minecraft 1.6, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 1.6.4, Minecraft 13w36b, Minecraft 13w37a, Minecraft 13w38c, Minecraft 13w39b, Minecraft 13w41a, Minecraft 1.7.1, Minecraft 1.7.2, Minecraft 1.7.3, Minecraft 1.7.4, Minecraft 14w05a, Minecraft 1.7.5, Minecraft 14w11b, Minecraft 14w26c, Minecraft 1.7.10, Minecraft 1.8, Minecraft 1.8.1-pre3, Minecraft 1.8.1, Minecraft 1.8.2-pre1, Minecraft 1.8.8, Minecraft 15w32c, Minecraft 15w51b, Minecraft 1.10.2, Minecraft 16w40a, Minecraft 16w42a, Minecraft 1.11.2, Minecraft 1.12.1, Minecraft 1.12.2, Minecraft 18w02a, Minecraft 18w06a, Minecraft 18w20c, Minecraft 1.13.1, 1.14.4, 19w38b, 20w07a, 1.16.1, 20w29a
Fix Version/s: None

Type: Bug
Reporter: Kumasasa Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 25
Labels: None

Attachments: PNG File 2013-01-27_23.48.40.png     Text File crash-2013-01-27_23.46.20-client.txt     Text File crash-2013-01-27_23.49.06-client.txt    
Issue Links:
Bonfire Testing
discovered while testing MC-8539 can't break some blocks in survival w... Closed
Relates
relates to MC-108372 Crash report does not contain generat... Resolved
CHK:
Confirmation Status: Confirmed
Category:
Crash, Debug, Text
Mojang Priority: Low

 Description   

The bug

Any survival or creative world created with cheats enabled shows "Cheats: False" in the crash report:

Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false

Code analysis

Code analysis by marcono1234 can be found in this comment.



 Comments   
Comment by Marcono1234 [ 03/Oct/21 ]

Resolving as Cannot Reproduce then.

Comment by [Mod] ampolive [ 20/Sep/21 ]

It is a server crash report. The client crash report indeed contains no information about the game mode.

Comment by Marcono1234 [ 20/Sep/21 ]

@ampolive, are you seeing this for a client or (integrated) server crash report (-client.txt or -server.txt)?
This issue appears to be about client crash reports only. However, in 21w37a the "-- Affected level --" section of a forced client crash report (triggered by holding F3 + C) does not seem to contain any information about game mode or cheats at all. Does a client crash report contain this information for you?

Comment by [Mod] ampolive [ 17/Sep/21 ]

Cannot reproduce in 21w37a. The crash states Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: true.

Comment by pulpetti [ 06/Jul/20 ]

Confirmed in 20w29a

Comment by pulpetti [ 06/Jul/20 ]

Confirmed in 1.16.1

Comment by Conem [ 08/Jun/20 ]

Cannot reproduce in 1.16-pre2. Triggered a debug crash but there's not anything related to the "Level game mode" in it.

Comment by Mike24 [ 16/Feb/20 ]

The bug is in 20w07a

Comment by Kraif [ 31/Aug/18 ]

Confirmed for 1.13.1.

Comment by Marcono1234 [ 06/Aug/16 ]

Please link to this comment in the description

The following is based on a decompiled version of Minecraft 1.10 using MCP 9.30.

The reason for this is that the crash report is thrown client side. Therefor all information displayed is the one available to the client. The problem is that the packet SPacketJoinGame does not contain information about whether or not commands are enabled (same should apply to mapFeaturesEnabled). This could probably be solved by having the server (and the client) create a crash report each.

Comment by Marcono1234 [ 10/Jan/16 ]

Confirmed for

  • 15w51b
Comment by Itouch2 [ 16/Mar/14 ]

Confirmed for 1.7.5 and 14w11b

Comment by Kumasasa [ 27/Jan/13 ]

Crash report of creative and survival attached, both worlds created with cheats enabled

Generated at Sun Jan 12 12:18:11 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.