You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Respawnable Enderdragon Egg rule, the enderdragon egg is added too early without checking the UUID of the dragon entities. Suppose the ender dragon is teleported, and then killed in far away chunks, this feature will still modify the chunk remotely.
Steps to reproduce
Create a new world
Enable the regeneratingDragonEgg
Go into the end, freeze the enderdragon and push it into unloaded chunks(or you can teleport it away)
New dragoneggs actually respawned
Expected behavior
New dragoneggs do not respawn until we kill the new one
Actual behavior
No response
Relevant logs
No response
Minecraft version
Any
TemplateMod version
newest
Other information
No response
Check list
I have verified that the issue persists in the latest version of the mod.
I have searched the existing issues and confirmed that this is not a duplicate.
The text was updated successfully, but these errors were encountered:
Bug description
In Respawnable Enderdragon Egg rule, the enderdragon egg is added too early without checking the UUID of the dragon entities. Suppose the ender dragon is teleported, and then killed in far away chunks, this feature will still modify the chunk remotely.
Steps to reproduce
Expected behavior
New dragoneggs do not respawn until we kill the new one
Actual behavior
No response
Relevant logs
No response
Minecraft version
Any
TemplateMod version
newest
Other information
No response
Check list
The text was updated successfully, but these errors were encountered: