-
-
Notifications
You must be signed in to change notification settings - Fork 691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix inconsistencies with movement and position #699
Conversation
is this even active? |
Yes, it's very active, I just haven't pushed the latest changes yet. I have snow layers fixed etc. |
Just a heads-up that some |
Ah, I'll fix that, thank you |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The mappings submodule got updated which seems unintentional.
- There are still some Gradle files in the commit.
- Why move the session jumping and sneaking variables to PlayerEntity>
connector/src/main/java/org/geysermc/connector/entity/PlayerEntity.java
Outdated
Show resolved
Hide resolved
connector/src/main/java/org/geysermc/connector/network/session/cache/TeleportCache.java
Outdated
Show resolved
Hide resolved
...va/org/geysermc/connector/network/translators/bedrock/BedrockBlockPickRequestTranslator.java
Outdated
Show resolved
Hide resolved
.../main/java/org/geysermc/connector/network/translators/world/collision/CollisionRemapper.java
Outdated
Show resolved
Hide resolved
Fixes #1008 |
I can get in boats |
Updated to latest adapters commit and fixes the double getWorld call
# Whether to use direct server methods to retrieve information such as block states. | ||
# Turning this off for Spigot will stop NMS from being used but will have a performance impact. | ||
use-adapters: true | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have an option for move fixes too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I'm not opposed, I see no reason. There's not much reason people would want the move fixes off, and performance shouldn't be an issue. The reason that is an issue is in case there's a Spigot instance that breaks with them enabled.
Something that could be a config option is teleport ID confirmation flexibility.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean the position and resend thresholds?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
When was this renamed? |
I renamed it a couple weeks ago. |
Hmm, wonder why it says "sprinting up stairs," walking was the worst part for me, sprinting didn't have any issues. |
cache-chunks
needs to be enabled in your config for the move fixes to take effect!GeyserMC/mappings-generator#18 needs to be merged first
The same as #669 which was accidentality closed and the branch deleted
Move fixes V2 using bounding boxes
Currently fixes #548, #1008 and #617
Might fix #204
Known bugs that I can only fix when the custom collision boxes are in the release versions
Known bugs to fix
Sometimes when sprinting up stairs you get teleported backFixed!Snow layers are a bit buggy (disabling optimisations 2 and 3 at the same time seems to help)Mostly fixed, still has issues with different collision (not easily fixable but I'll try!)Add proper hitboxes for:Now uses mappingsDoor collision is buggyFixed except for a specific arrangementPlease tell me about any more bugs you find!