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
Describe the bug
This one's a nasty one. Basically, leaving The End triggers a form of respawn that is similar, but different, from dying. This causes any Band of Gigantism scaling effects which were active upon leaving The End to become permanent, and on respawn they will be applied again. Running /scale reset and dying are the only two methods of fixing this.
To Reproduce
Steps to reproduce the behavior:
Equip any scale-changing item. Personally, I used the Improved Band of Dwarfism for this.
Enter the portal which takes you from The End to The Overworld.
Check your scale. It will be twice as small or large as it should be, and taking off the band will reveal that the effects of the original band have become permanent.
Expected behavior
No issues relating to scaling becoming erratic after leaving The End.
Screenshots
I recorded a brief video to explain this issue:
2024-04-22.21-31-53.mp4
Versions (Important! Please do this):
Minecraft version: 1.19.2
Forge version: 43.3.13
Mod version: 1.2.0
The text was updated successfully, but these errors were encountered:
* Bump NeoGradle and remove 3G memory settings for Gradle, since the memory for decompilation is no longer inherited from Gradles memory settings since NeoGradle 7.0.56.
* Bump NeoForge to stable for 1.20.2
Describe the bug
This one's a nasty one. Basically, leaving The End triggers a form of respawn that is similar, but different, from dying. This causes any Band of Gigantism scaling effects which were active upon leaving The End to become permanent, and on respawn they will be applied again. Running /scale reset and dying are the only two methods of fixing this.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No issues relating to scaling becoming erratic after leaving The End.
Screenshots
I recorded a brief video to explain this issue:
2024-04-22.21-31-53.mp4
Versions (Important! Please do this):
The text was updated successfully, but these errors were encountered: