Saving and quitting while swimming causes the player to stand up even when they should not be able to
Identical to MC-132482 in cause, however results differ.
If you swim into a one block high space, then save and quit, when you log back in, you will have teleported to the nearest available space above where you logged out. One would expect to have logged back in to remain in a swimming state in the same location.
Linked Issues
is duplicated by5
MCPE-115271Spawn randomly when left the game while crawlingDuplicateMCPE-118863Saving & exiting while in a 1X1 tunnel causing to spawn on y above thats not 1X1DuplicateMCPE-139779Player comes back to surface after logging in while crawling in caveDuplicateMCPE-144226save while swimming loses players location co-ordinatesDuplicateMCPE-146997Mining bugDuplicate
Created Issue:
Saving and quitting while swimming causes the player to stand up even when they should not be able to
Identical to
MC-132482in cause, however results differ.If you swim into a one block high space, then save and quit, when you log back in, you will have teleported to the nearest available space above where you logged out. One would expect to have logged back in to remain in a swimming state in the same location.
Attachments4
![[Mojang] Mega_Spud (Jay Wells)](../../../data/avatars/users/92696.png){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] OcelotOnesie](../../../data/avatars/users/43220.png){kind=small}
![[MCQA] Kinga Izdebska](../../../data/avatars/users/18949.svg){kind=small}
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
![[MCQA] v-weszaj](../../../data/avatars/users/18941.svg){kind=small}
Thank you for your report!
We're actually already tracking this issue at MCPE-35808, so I will resolve and link this ticket as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-35808, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-35808, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Thank you for your report!
We're tracking this issue in MCPE-35808, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
– I am a bot. This action was performed automatically! The ticket was resolved by one of our moderators, and I left this message to give more information to you.
The bigger problem at hand is why does mojang/Microsoft insist on the divergent path between Bedrock and Java.
the crawl state is something g that needs to be addressed. Either allow i players to crawl and add in the proper support for Bedrock or fix the effective bug that you can be in a swimming state outside of water. This discrepancy makes a whole lot more issues in game play and other bugs like MCPE-35808. Where there is an improper save/reload when in a single block high space.. ie swimming outside of water.
Thank you for your report!
We're tracking this issue in MCPE-35808, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Cleaning up old tickets: This ticket has not been updated recently (~1 year+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Issue Guidelines – 💬 Mojang Support – 📧 Suggestions – 📖 Minecraft Wiki
This is a valid issue and is affected in the recent hotfix 1.17.11 hotfix. I also posted the same issue but it is saying duplicate with this post.
still an outstanding issue. it is easily duplicated. is still an error inside 1.17.34+ clearly is not considered to be of high enough priority for anyone to bother looking into. BTW. Comment posted by Jay Wells. has a dead link. why are the issue Guidelines secret? why would this link be removed?
Any update as to if this bug is now getting taken seriously?
please update to show this is and outstanding error in the 1.18.2 stream still
Still outstanding and does not appear to be resolved in 1.18.10.28
is this something that is just so far bottom of the list to fix that it will never see the light of day? this is a major flaw as it directly effects the game play. Unlike the things you seem to be focusing on like a pixel is wrong with the image of the fire, or the door doesn't have the correct bitmap applied. How about taking on bugs that have some impact?
So still can’t be bothered to fix this or even acknowledge that it’s outstanding in 1.18