BDS-4965Frost walker does not work with Server Authoritative Movement off
What I expected to happen was...:
Frost walker should work regardless of server settings.
What actually happened was...:
When setting server-authoritative-movement to false, frost walker no longer functions as expected.
Steps to Reproduce:
- Start BDS instance with server-authoritative-movement=true
- Obtain frost walker boots and walk over water
- Note that they work as expected, freezing water beneath you
- Stop BDS instance and switch server-authoritative-movement to false
- Rejoin world and note that frost walker no longer functions
In this current version of minecraft, frost walker doesn't appear to work at all. I get 0 freezing with Frost Walker II boots.
Linked Issues
is duplicated by5
BDS-16654Frost walker don't workDuplicateBDS-16915Frost Walker is not working in My minecraft serverDuplicateMCPE-132294Frost walker boots/enchant not working for minecraft pocket editionDuplicateMCPE-134678My frost walker 2 boots doesn't turn water into iceDuplicateMCPE-142019Frost walker doesn't work correctly on serversDuplicateAttachments1
Comments5
History30
Resolution: Unresolved → Awaiting Response
Minecraft 2020.05.02 - 11.07.51.02-1.m4v
Resolution: Awaiting Response → Unresolved
Changed description:
In this current version of minecraft, frost walker doesn't appear to work at all. I get 0 freezing with Frost Walker II boots.
What I expected to happen was...:
What actually happened was...:
Steps to Reproduce:
- 0
- Start BDS instance with server-authoritative-movement=true
- Obtain frost walker boots and walk over water
- Note that they work as expected, freezing water beneath you
- Stop BDS instance and switch server-authoritative-movement to false
- Rejoin world and note that frost walker no longer functions
In this current version of minecraft, frost walker doesn't appear to work at all. I get 0 freezing with Frost Walker II boots.
Added is duplicated by link: MCPE-132294Frost walker boots/enchant not working for minecraft pocket editionDuplicate
Added affects versions: 1.17.0
Added is duplicated by link: MCPE-134678My frost walker 2 boots doesn't turn water into iceDuplicate
Added is duplicated by link: MCPE-142019Frost walker doesn't work correctly on serversDuplicate
Added affects versions: 1.17.30
Changed summary:
Added is duplicated by link: BDS-16654Frost walker don't workDuplicate
Added affects versions: 1.18.2 Hotfix
Added is duplicated by link: BDS-16915Frost Walker is not working in My minecraft serverDuplicate
Added affects versions: 1.18.31
Added relates to link: MCPE-168280Unable to place blocks on interactable blocks when sneakingFixed
Resolution: Unresolved → Fixed
Potentially a duplicate of
MCPE-52788But this issue was supposed to be fixed in 1.14.0.1
I cannot reproduce this in 1.14.60. Frost Walker I and II both work as expected, freezing water sources at in a radius immediately below the player's feet.
Note that you do have to be moving horizontally for Frost Walker to freeze water. Is that your issue?
So, I wonder if it's conflicting with feather falling. I forgot to mention the boots are actually
Diamond Boots
Here's a video of it happening:
Minecraft 2020.05.02 - 11.07.51.02-1.m4v
Your video is clear but I can't reproduce it in 1.14.60 using diamond boots with the same enchantments in the same order. I also tried toggling world settings like "fire spreads" and "mob griefing," I tried adventure mode, and I tried joining a world with only "visitor" permissions, but none of these caused frost walker to stop working for me. I will therefore set the status of this report to "plausible" until someone can determine how to reproduce the bug.
Does this occur in all worlds for you, or just the one shown in your video?
Does it in the world if you open it locally rather than from a server?
Would you be able to upload a copy of the world where this is happening?
I found the issue.
I had server authoritative movement turned off. When I turned it back on, frost walker worked.
So if you disable server authoritative movement, frost walker breaks
This seems like a super low priority issue since this has an easy work-around.