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
Actual behavior: When you are morphed as an Ender Dragon, blocks around you are destroyed, both near you and very far away. The blocks destroyed aren't counted as harvested or mined by the player.
Expected behavior: When you are morphed as an Ender Dragon, either no blocks are destroyed or blocks that are within your hitbox are destroyed, just like regular Ender Dragons. No blocks are destroyed that are very far away from you.
Bonus: In addition, blocks that are automatically destroyed while you are an Ender Dragon are broken if they were mined by you. This includes correct tool handling, hunger loss, statistics, and actually dropping the item (or putting it directly in your inventory).
The text was updated successfully, but these errors were encountered:
This probably has to do something with the fact that the Enderdragon's AI isn't turned off when you're transformed as them unlike every other transformation. While turning it off does solve this issue, the Enderdragon will no longer animate because its reliant on its AI to do so.
Minecraft 1.12.2
Forge 14.23.5.2854
DominionLib 1.0.4
Changeling 1.2
Actual behavior: When you are morphed as an Ender Dragon, blocks around you are destroyed, both near you and very far away. The blocks destroyed aren't counted as harvested or mined by the player.
Expected behavior: When you are morphed as an Ender Dragon, either no blocks are destroyed or blocks that are within your hitbox are destroyed, just like regular Ender Dragons. No blocks are destroyed that are very far away from you.
Bonus: In addition, blocks that are automatically destroyed while you are an Ender Dragon are broken if they were mined by you. This includes correct tool handling, hunger loss, statistics, and actually dropping the item (or putting it directly in your inventory).
The text was updated successfully, but these errors were encountered: