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
I can reproduce this issue consistently in single-player
I can reproduce this issue consistently in multi-player
I have searched for this issue previously and it was either (1) not previously reported, or (2) previously fixed and I am having the same problem.
I am crashing and can provide my crash report(s)
I am using the latest version of the mod
Loader version
Fabric 0.16.3
Minecraft version
1.21.1
Mod version
ArmorPoser-fabric-1.21-6.1.1
Java version
java version "1.8.0_411"
Issue Description
When I try to move the armor stand on the y-axis it acts like the gravity is still applied even when turned off. It will even go as far as falling several blocks underground This does not happen in my singleplayer world.
I saw someone else on the comments on curseforge state this, but did not see a report here.
Additional Information
No response
The text was updated successfully, but these errors were encountered:
OMG, yes that is a typo, meant to be 1.21.1
When I look at my Java version it says that is the one I have installed.
Server is hosted through Shockbyte if that is useful information.
Yes, the server has the mod installed. I am able to access the UI and edit armor stands, however the gravity does not actually turn off, base plates do not stay disabled, and all rotations reset to south.
General Info
Loader version
Fabric 0.16.3
Minecraft version
1.21.1
Mod version
ArmorPoser-fabric-1.21-6.1.1
Java version
java version "1.8.0_411"
Issue Description
When I try to move the armor stand on the y-axis it acts like the gravity is still applied even when turned off. It will even go as far as falling several blocks underground This does not happen in my singleplayer world.
I saw someone else on the comments on curseforge state this, but did not see a report here.
Additional Information
No response
The text was updated successfully, but these errors were encountered: