Confirmed (18w19a)

So, it appears that it's not a visual glitch. Occasionally you can see the item flash quickly in the bottom right (right handed) as if it's just being switched back and forth quickly. Also if it's a tool, it no longer functions.

Exactly, that's why I chose in the title "too far to the right", as they are flashing into the viewpoint if you move your player. - Interesting regarding the tool not working though, haven't tested that, thanks a lot for the info Jakob Knigga!

Likely relates to MC-129239.

Yup. My tools also don't work.

I deleted my DIMM and region folders and regenerated my world keeping playerdata/stats

I have my old inventory. But the world is new. Tools don't work.

Server: 18w19a OS: Win7 x64 Java: 1.8.0 Build 171

Update: Crafting a new Wooden Axe. Worked...Once. Then it broke too.

Update 2: Confirmed for Single Player

Steps to reproduce:

1) Start a new world. Any seed.

2) Break 2 wood.

3) Craft Planks.

4) Craft a Crafting Table.

5) Craft Sticks

6) Craft a Wooden Shovel.

7) Observe bug.

I'd like to add that when I tested this bug myself, when allocated 1 gb of ram the item would bob in and out of view , kinda liked switching between two items real fast. When I checked with more ram allocated , It would behave the same as the report above shows.

Thank you all very much for the additional info, will update it accordingly in a bit!
Unless the mods decide that them tools not working should be rather in a new bugpost?

Just asked, I shall add it to the description, there's a bit of inconsistency with the tools by the way, e.g. shovels and hoes which were used still work on dirt/grass (rightclicking), just not mining the block in the case of the shovel.

Will add an additional video in a bit, thank you all again!

neron I always dedicate 3GB RAM to MC, but still, some items wiggle up and down.
It seems to be sometimes a bit random though, e.g. in one world dyed leather armour didn't "wiggle" at all, whereas in another worldsave it did. No idea currently, why.

Same is happening with potions. Out of view and no sound during drinking, sometimes cannot drink.

it happens when holding a map and a shield with two hands.

After one use all tools and weapons jump while you are holding them and no longer work after they have taken any amount of damage. My computer was being a butt and wouldn't let me take a video, so I took a video with my phone.

crazy sword.mp4

This applies to all un-enchanted shovels, pickaxes, axes, hoes, and swords, as well as the flint and steel, fishing pole, sheers, bow, and trident.

Once you have a bow that starts jumping, switching it out to a new bow doesn't fix the problem. Same with the trident, but you can still throw the trident, while the bow in unusable.

In creative, you can use undamaged tools and there is no issue. But weapons start jumping like they do in survival as soon as you hit an enemy. (The second time I tried to get swords jump in creative it didn't work. So not sure about them.)

seed: -8300275442758179407

James Rood you're not supposed to really play a snapshot version as if it were a release version
They can corrupt worlds (happened to many people incl. myself), they can break stuff, and, worst case, it may be that you can't play the world you entered in a snapshot version at all anymore in a release version. E.g. in this case, if I entered a world last time in 16a, all builds in there got erased upon entering the worldsave in 19a (should be fixed in the upcoming b-snapshot).

Hence they say to always backup the worlds, even more so if it's a Survival world you play in legit.

But I agree that it's not easy to pinpoint maybe other bugs if you cannot play the game also in Survival, but all we can do is to wait it being fixed, so thank you for any help/additional info

Still happens when you repair the tool to full durability with another tool

Oddly, the axe continues to kill sheep and cows, even though it will not cut down trees. So it's "break" that is broken, while "kill" works fine.

This also affects items like buried treasure maps.

having same issues myself when is this expected anytime soon ?

luke noddle Look at the top middle, at "Resolution", it is resolved to "Fixed" now
So maybe it'll be in today's b-snapshot

was gonna say i seen it fixed neverrealized there was the b snap today lol
thank you

I was going to ask why all the bugs like this one say "resolved" when I still have the issue, but okay there should be 18w19b now. However, in my launcher (opened at 11:01 GMT+2) it still says the latest snapshot is 18w19a which is weird if 19b is out.

19b isn't out. Also there is no guarantee that 'future version 1.13+' means 19b. It probably will, but it could be next week if we're unlucky.

1. [Mojang] ProfMobius (Thomas Guimbretiere) tweeted yesterday that a 18w19b will release today.
2. It just changed to "Minecraft 18w19b".

Renate Koelman Just to explain it a little bit: The developers who fix the bugs change the game code, and all those various code changes have to be implemented in the resulting (new) snapshot. That means the snapshot has to be "built" first, containing all those code changes. The developers mark them here on the bugtracker as fixed as it is fixed on their end, but that very (new snapshot) version is not being pushed out to the launcher/to us immediately.

Just keep in mind that there are often many bugfixes, and of various developers, and some other bugs they may consider a "must-fix" for a next snapshot may not have been fixed yet. They cannot push out a new snapshot for each single bugfix

If you got Twitter, follow the MC Java developers on there, at least one of them will tweet out that there's a new snapshot out as soon as it is Or of course on the minecraft.net blog.

My bug report is duplicate too.

MC-129362