-
Bug
-
Resolution: Unresolved
-
None
-
1.19.2, 22w43a, 22w44a, 22w45a, 22w46a, 1.19.3 Pre-release 1, 1.19.3, 23w03a, 1.19.4 Pre-release 1, 1.19.4, 23w16a, 23w18a, 1.20 Pre-release 1, 1.20 Pre-release 2, 1.20 Pre-release 5, 1.20 Pre-release 6, 1.20, 1.20.1, 23w32a, 23w35a, 1.20.2 Pre-release 1, 1.20.2 Release Candidate 1, 1.20.2, 23w41a, 23w42a, 23w43a, 23w44a, 1.20.3 Pre-Release 2, 1.20.3, 1.20.4, 24w07a, 24w09a, 24w10a, 24w12a, 24w13a, 1.20.5 Release Candidate 1, 1.20.5, 24w19b, 1.21 Pre-Release 1, 1.21, 24w39a, 1.21.3, 1.21.4
-
None
-
Confirmed
-
Combat, UI
-
Low
-
Platform
If a player ignites TNT with unstable=true by punching it and another player dies to it, the former does not get the credit for the kill.
How to reproduce:
- Use the /setblock command to place a TNT block with unstable=true, or place a regular TNT block and use a debug stick on it.
- In survival mode, punch the block to ignite it and stand inside it.
- Wait to die and look at the death message.
Expected result:
"<player> was blown up by <player>"
Observed result:
"<player> blew up" (not 22w43a-22w44a) / "<player> was blown up by Primed TNT" (22w43a-22w44a)
- relates to
-
MC-268932 TNT with unstable=true is not ignited when broken with /setblock or /fill destroy
- Resolved