For some context, I am working on a reboot of the SmartMoving mod. This mod is using the PlayerAPI and RenderPlayerAPI core mods and is significantly overriding some aspects of the vanilla movement logic. I have been able to resize the player's bounding box by changing player.height (e.g. making the bb less than 1 block high for crawling). However, when I try to offset using a value of bbyOffset != 0, aka translate the bounding box vertically, this actually keeps moving the player in that direction. They will constantly move upwards when I just want to hitbox to be offset vertically and maintain the same movement.
This is happening on afterOnUpdate(). I know this question is not necessarily a Forge question, but the core mods do not really have a responsive community and my question primarily lies in why the vanilla code is causing this movement.
This is being worked on in 1.12.2 currently but will be moving to newer versions soon. Tested on a newer version with the same effect.
For some context, I am working on a reboot of the SmartMoving mod. This mod is using the PlayerAPI and RenderPlayerAPI core mods and is significantly overriding some aspects of the vanilla movement logic. I have been able to resize the player's bounding box by changing player.height (e.g. making the bb less than 1 block high for crawling). However, when I try to offset using a value of bbyOffset != 0, aka translate the bounding box vertically, this actually keeps moving the player in that direction. They will constantly move upwards when I just want to hitbox to be offset vertically and maintain the same movement.
This is happening on afterOnUpdate(). I know this question is not necessarily a Forge question, but the core mods do not really have a responsive community and my question primarily lies in why the vanilla code is causing this movement.
This is being worked on in 1.12.2 currently but will be moving to newer versions soon. Tested on a newer version with the same effect.