mojira.dev

Rodrigo

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

View all
MCPE-235751 Problem closing tabs and interfaces Duplicate MCL-26266 "Failed to load game" message after trying to start bedrock edition Duplicate MCPE-222975 happy ghast turns black Awaiting Response MCPE-194192 Mace doesn’t launch you high on bedrock Duplicate MCPE-129391 when I try to log into a server it gets infinitely loaded. Incomplete WEB-4209 SKIN DO MINACRAFT PC Incomplete BDS-12244 i cant get into online servers Incomplete MCPE-115551 Nintendo switch online services Duplicate MC-201189 cada ves que apreto f3s me aparecen unas rayas como de sonido Invalid MC-193800 Wrong mob sounds playing Awaiting Response

Comments

I’m having the same issue on Minecraft Bedrock 1.21.121 (Windows, Launcher version).
Even in fullscreen or borderless window, the mouse doesn’t stay locked inside the game.
When I move the camera or try to shoot an arrow, the cursor sometimes escapes to the edge or to another monitor.
It even clicks on the Windows taskbar or minimizes the game if I aim near the bottom of the screen.

This makes aiming with bows or tridents almost impossible.

I’m having the same issue, have watched countless streams, for hours and hours. And still no Home Cape code.

The Mineplex server in particular, and one that my friend created using the aternos host (this one in particular is what has me most distressed, since I have some friends playing on it and I ended up with my progress frozen) 

I can confirm. I also noticed that other detector blocks are also broken: Tripwire hook does not activate and detector rails activate only the first time.

I can’t even refund it I tried to cancel but it takes forever to load

I do have the exact same issue and i couldn't fix it. 

also we need these options in the realms. 

http://imgur.com/nr6eUes

Still happens in windows 10 (v1.1.2).

Fixed in 1.1 beta (idk the build)

Sad to know that. This worked well before and I built a few things that uses that mechanism.

@unknown Yes, this still happens

This still affects windows 10 edition in version 1.0. Please reopen it.

Guys their worlds were generated in version 0.16.2 or earlier, right? I have a world of 0.16.2 and when I open a copy of it in build 1 I see these errors, but when I open in build 5 (directly from 0.16.2 without having opened in other builds) I do not see these errors so I believe this has already been fixed and their worlds continue with errors because they were corrupted in build 1. I'm not sure but in this case I think mojang will not do something to fix those worlds. That's why mojang recommends backing up the worlds before installing a beta.

Load more comments