thilo77

This problem persists in 1.15.1

Maybe the issue should be renamed to better reflect it's content? Something like "Items not properly gliding from ice blocks onto slime blocks", or similar.

Is the gliding issue the main problem or did slimeblock behaviour change in other ways, e.g. did items in 1.14.4 bounce into the air from slimeblocks in positions where they don't do so in 1.15?

In my world, this does not happen in 1.14.2 in a place where I could reliably reproduce it in 1.13.2.

I have just had chicken drop both the cooked and the uncooked variant when killed with a fire aspect ii and looting iii sword. World is in minecraft realms, the client is out-of-the-box 1.14, no data-/resource-pack of any kind in use anywhere.

Please reopen, as this bug is not a duplicate of MC-137792. That bug is the other way round (mobs dropping cooked stuff when they should not) and involves faulty datapacks (which are not in use when the effect that is described here happens).

As Amanda commented on MC-134969, the issue seem to be resolved in version 1.13.2. For me, the issue described in the original post vanished with 1.13.2. Also, my trident farm has started to work with 1.13.2, without me changing anything else.

Partial world resets for java realms are also mentioned in the description and comments of MC-134506 from around the same time as Joshua Adkison commented above.

The problem persists in 1.13.1 (at least that's the client version I'm running when connecting to the realm).

This might be related to MC-134506 .

I have a very similar stoy to tell as is told above in "final conclusion", including the crash, the partial world reset, restoring a backup and no spawns in the pigmen farm. Also, moving around the farm helps with spawning.

On the other hand, I cannot say with certainty whether this spawning behaviour started with the crash or with the update to 1.13. Additionaly, I built drowned/trident farms in both pre- and post-1.13 terrain, and none of them works (though I am sure the farms' design is valid).

The phenomenon under discussion here might be related to MC-134969 .

Thanks for reopening. After playing 1.11 for a while, I must correct the statement in my previous comment: the behavior did not change at all, the bug is as described in the original bug description. I guess me being able to turn 90 degrees in each direction was a coincidence of the mouse position. Since then, I've experienced the bug as was reported initially.

Can anyone confirm with certainty that this is a Linux-only problem?

Something very much like this still happens under linux in 1.11. If I leave fullscreen and cause the minecraft window to lose focus (e.g., by looking something up in the browser), refocus the minecraft window and return it to fullscreen, then sometimes (but not always) the character cannot be fully turned around. Pressing Esc to enter the menu still solves this.

The one change I noticed since 1.10.2 is that the character is now restricted to turning 90 degrees to the left and 90 degrees to the right of the initial viewing direction, whereas before it was as described in the original report.

I think this bug should be reopened, as the problem basically remains the same. Please let me know if it would be better to open a new report due to the slightly changed behavior.

(I'm currently running mc 1.11 on archlinux
4.4.24-1-lts #1 SMP Fri Oct 7 20:44:49 CEST 2016 x86_64 GNU/Linux, java is
OpenJDK Runtime Environment (build 1.8.0_102-b14))

Happened to me on a realm using the 1.10.1 client, attached the crash report.

Curiously, using the 1.10 client works without problems (though I'm mostly surprised that it works at all, as realms previously always forced me to use the latest client).

This is still an issue in 1.9.2.

still present in 1.8 release

This bug does no longer seems to appear in 14w04a and 14w08a. In these snapshots, the player's position in the F3 screen is simply given as "XYZ" (which obviously is the player's feet position); both visual spawner activity and mob generation now seem to be triggered by this position being within 16 blocks from the spawner's center. Maybe this is the effect of code cleanup? I consider this bug fixed.

Still happens in what the launcher calls "snapshot 1.6" and "snapshot 1.6.1".

I think what is meant is that seemingly there is a color gradient within individual grass blocks. In the first screenshot, if you look at the block in the lower center, the lower left corner of the block may appear to be more blueish than the upper right corner, which would indeed be reversed.

However, I think this is an optical illusion because the block is surrounded by different greens. If you dim everything but this block (edited screenshot), the block looks quite uniform (and, as far as I know, individual grass blocks cannot have a gradient, they are tinted per block).

I guess this would be invalid or works as intended.

I was able to reproduce this for the "above" position in snapshot 13w16a, with a pig spawner in creative mode.

Edit: Same in the other recent snapshots (13w16b and 13w17a), and the 1.5.2 pre-release.

I'm afraid the wiki page never said anything about this bug being fixed. IMO, the wiki user age2empires2020 just vented his/her anger that lots of new features have been added before making the already existing features work correctly. Look, for example, at this revision of the "Version history/Development" versions wiki page, which I think started the debate. Under "13w16a" it says "Bugs" and "Top 10 most popular bugs", but nothing about them being fixed. As opposed to "Bug fixes" in all other entries.

Thank you for checking!