MCPE-14345Boats enter nether portals too easily
Steps to reproduce :
-build a portal and place an iron block like in the attachment
-place a boat on the iron block
What I expected to happen :
Nothing
What happened :
The boat was teleported to the nether
Attachments1
Created Issue:
Boats enter nether portals too easily
Steps to reproduce :
-build a portal and place an iron block like in the attachment
-place a boat on the iron blockWhat I expected to happen :
NothingWhat happened :
The boat was teleported to the nether
Attachments1
I can confirm on Minecraft Windows 10 Edition Beta Version: 0.14.2
![[Bot] Arisa](../../../data/assets/gravatar/mustek2.png){kind=small}
This bug might be triggered by something, or it may be completely random. At least, I can say it isn't triggered by the nether.
Steps to reproduce :
-Play the game normally
-Keep playing until it happens
To go back to normal :
-Close the app
-Kill the process
-Reopen the world
Device : "Soshphone 4g"
Generic ZTE phone
Android 4.4.2
Everything below this line may be unrelated to the bug
-What I did :
-I placed 30 boats in the nether using MCPE-14345
-I entered the nether. The game crashed, but I didn't think this was worthy of a bug report in itself, because it seems to have already been reported. Plus, it often happens without the last part of the bug.
-I reopened the world and entered the Nether.
Steps to reproduce :
No idea. I tried to do it again, but it didn't work.
What I expected to happen :
I would be in the Nether
What happened :
-Netherrack looked weird in a radius of about 16 blocks
-I placed a redstone torch, and it looked strange too
-Going back to the overworld didn't fix anything
-More blocks were affected (white clay was red, droppers had a black face, cobble had a bad texture...)
-After leaving the world and coming back, everything was normal again
I can confirm, on Minecraft Windows 10 Edition Beta, Version: 0.14.2
I can confirm.
Other very closely related bug : boats can destroy lilypads without touching them. It seems to be another consequence of the same bug.
Please respond and add the current version if you can reproduce this issue.
Confirmed in 0.15.4, please reopen.
This is a bulk resolve of issues that haven't been updated to 0.16.0+ yet. Please comment below (To open the ticket) and update your affected versions. If you cannot reproduce the bug, please write in the comments so we can resolve it as "Cannot Reproduce". Thank You!