-
Bug
-
Resolution: Unresolved
-
None
-
1.18.2, 22w18a, 22w19a, 1.19 Pre-release 2, 1.19, 1.19.1 Pre-release 6, 1.19.1, 1.19.2, 22w42a, 22w43a, 22w44a, 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
-
None
-
Confirmed
-
Advancements
-
Normal
-
Platform
Setting the location.dimension field of the entity condition in player_killed_entity will not make the advancement check for the entity's dimension, but the dimension the player that will get the advancement is in.
How to reproduce:
- Summon a ghast with no AI in the nether.
- Use /forceload add on the chunk the ghast is in, or have another player stand close to the ghast to make sure it is loaded.
- Place a TNT block next to it.
- Light the TNT using flint and steel or a fire charge and go through a nether portal before it explodes.
- Find out that you just got the advancement "Uneasy Alliance", even though the ghast was in the nether.
What I expected to happen was:
The advancement would require the ghast to be in the overworld.
What actually happened was:
Only the player is required to be in the overworld.
Code analysis:
Code analysis by Misoloo can be found in this comment.