mojira.dev
MC-263204

Dying in the End void does not have the same behavior as dying in the Nether or Overworld

I was updating my tombstone datapack to 1.20 when i noticed a weird behavior.

Steps :

  • Trigger on death

    • execute as @a[scores=
      {tombstone=1..,hp=1..}] at @s ... 

  • Summoning pos marker into the dimension

    • execute in ... run summon ...

  • Find place & Summon the grave

    • execute as 'pos_marker' at @s ... (searching stuff)

    • execute as 'find_place' at @s run function tombstone:create/place

Expected behavior :

  • Working in every dimension, even if player fall into the void.

Current behavior :

  • Working in every dimension, even if player fall into the void exept if player dying into the end void.

Explication :

For an unknown reason, spawned entity during the process are not detected with @e selector if, and only if, player dying into the end void from the Y level that does the damages.

Tests :

  • Rewriting the datapack using others techniques : Same issue.

  • Test others dimensions : Only end is affected

  • When player are below Y:-65, tp at -30 and killing them : Working

  • Tested in loaded & unloaded area (forceload command) : Same issue

Ressources

Attachments

Comments 4

hey, could you give you the datapack you use?

@peashooter Np, i added it, but this is the version with the debug enabled (into .../data/tombstone/functions/tick.mcfunction at line 18)

I can't reproduce this. I've attached my version of a pack that detects player death and summons a marker, then looks for it. It works successfully in the end. Can I ask why your pack requires the player's health to be > 0?

@tryashtar Because I followed Cloud Wolf's advice on his video about using the LastDeathLocation tag (video from 1 year ago) ^^"

But i can't remember the exact reason ^^"

Wolphwood

(Unassigned)

Unconfirmed

Data Packs

1.20 Release Candidate 1, 1.20.1

Retrieved