mojira.dev

Vitold Chernatinski

Assigned

No issues.

Reported

MC-103286 Sound when equiping armor Duplicate MC-102252 Auto-jump height requirement needs to be raised. Works As Intended MC-102008 Can't type in unsigned Book and Quills that have no NBT tag Duplicate MC-100810 Standing on Grass Path + Hoe = Doing a jig Duplicate

Comments

[media]

Added my launcher log showing the root tick spam as well. Includes some /debug as well. Done with a clean install, as should be obvious from the log.

I'm still having this issue with the 1.10 official release.

Affects 1.10

Affects 1.10

I see. Either way, the bug is still confirmed for 1.9.4 since my mouse was recently unbound until it got "fixed".

What possible convenience is there to having it locked at all times? The mouse doesn't become loose during normal gameplay and so doesn't cause any sort of inconvenience there. Instead, removing the ability to move across screens makes it noticeably more inconvenient for when you want to do so.

@Redstonehelper I suppose that is part of the problem and related, but not what I'm talking about. My main issue is that, for some reason out of the blue, I could not move my mouse off the Minecraft window on to the next screen. The problem persists even after restarting my computer.

Confirmed for MC 1.9.4 and Snapshot 16w21b.

I found a workaround for the time being and posted it into the Minecraft forums here:
http://www.minecraftforum.net/forums/support/unmodified-minecraft-client/1854755-cant-move-cursor-mouse-to-second-monitor-when?comment=11

There is a small possibility that the issue has to do with some sort of system keyboard shortcut we've accidentally pushed. From what I recall, the problem seems to occur after my daughter attacks my keyboard, and I have seen a similar sentiment on another website, but I haven't been able to find any shortcuts that would do such a thing and it is entirely possible that the correlation does not equal causation. I believe the issue is indeed a bug since turning on Fullscreen after applying the workaround and then immediately turning fullscreen back off again completely disables the ability to maximize the game that you had just a second ago. This inability to maximize with the workaround seems to be exactly the same as when it happens when this issue is left unresolved and fullscreen is off. If you accidentally turn on fullscreen after applying the workaround, you have to close the game and reopen it to have the option to maximize it again.

Still Reproducible in 1.9.4
Seed: 2368284
x: 1941
z: 5825
Look for pink sheep.

The problem lies in the NBT tags. There is no NBT tag when the book is virgin but once any writing is placed, even if immediately erased before ever closing, an NBT tag is created and writing is allowed.

Please close this report. I somehow forgot to check if this was a duplicate, as it is by MC-1685. I'll just add a comment about the NBT tags to that one.

I tried to add "Minecraft 1.9" and "snapshot 15w41b" to the list of affected versions but it didn't give me the options for either. It also persists into the latest snapshot (16w14a).