mojira.dev

Holger

Assigned

No issues.

Reported

MC-70133 Player marker on map stops following player Duplicate MC-61099 placing ladders crashes the game Duplicate MC-59015 Redstone torches pop off powered blocks Duplicate MC-51350 Hitbox of small flowers sometimes do not match item Duplicate MC-47562 Cannot place pistons facing upward Duplicate MC-5287 players and minecarts are being rendered at the wrong spot in MP Duplicate MC-3547 minecart movement jerky Duplicate MC-772 cow sounds do not fit well into game Invalid

Comments

Version 1.16.2: Adventuring time trophy came!

Version 1.16.1: Adventuring time trophy not unlocking

unfortunately this workaround does not work for me. I deleted the save data (saved on usb, I had not deleted Mincraft) and started a new world. Even after a number of other biomes, the trophy does not drop. Not even after the latest update after Nether update. Any tips?

@Mog: as of 1.8pre black items are fixed

confirmed for 1.8pre3

Still have this issue in 14w30c.

Behaviour seems to fit the "feet hypothesis" as light returns when riding downhill.

Since 14w29b the effect has kind of reversed.

Before, once the block was loaded and visible everything worked just fine.

Now changes to the nearby environment (placing a torch, breaking a block) are subject to delay. Sometimes it's just a split second (annoying when placing a torch takes time to illuminate the cave), sometimes the are quasi permanent: I can break a couple of blocks above my head and then jump into the new space gaining clipping errors like being in "spectator" mode. I need to place another torch then.

This happens whenever there is a solid block directly above the floating lava/water.

Similar things happen in fortresses:
Wrongly attached Torches,
Generated doors consisting of two upper halves (and connot be opended/closed).
Generated buttons besides doors not working.
Upper half slabs are being generated where lower half slabs are expected.

Might be worth noting that there is more to it than just redstone torches:

I have the following sequence of blocks:
(any) Button>Repeater>Redstone>Redstone>Redstone>Redstone (Facing north)
Pressing the button makes the repeater start flickering.
Must be facing north.
Must be at least 4 redstone.

please reopen, this bug report is not about the flowers being placed off center!

This seems to happen when a (storage?)minecart is moving while one is quitting the game (SSP).

The minecart is being displayed at (x,y,z-1) when being at (x,y,z).
Illumination is being computed referring to (x,y,z-1) (i.e. gets black when moving next to a solid blocks).
Apart from that the cart follows the rail quite normally: The interaction with turns, acceleration tracks, and sensor tracks is normal.

Still in 1.4.6. At high altitude I was able to observe the behaviour on short tracks. There I even got one minecart driving UNDER the track.

By the way: die player avatar is still sitting at the place where he started the ride (On long tracks the avatar mainly stuck somewhere standing along the track).

Also present in 1.4.5 (SMP)

Still happens in 1.4.4. More specifically:

  • build a long track (>400) from A to B

  • first player takes a ride with a cart from A

  • after first player ends at B second player starts

  • second players arrives a B and is invisible even after leaving the cart

  • first player rides back from a B to A and finds second player hanging in midair along the track.

+1 Ealrann Xor: Sometime the chunk terrain will be displayed (almost) upon entrance. This makes orientation extremely hard. Imagine a lava pit inside that chunk...

1.4.4 on linux it's workse than before (1.4.2) now, as I could tweak /etc/hosts manually before, which is no longer possible when opening to 0.0.0.0.

Workaround: starting the world as a true SMP version.

Happens in 1.4.2 with Players SSP(open to Lan - does this count as SMP?). Player visually stick at a random position above the track whereas the minecart continues empty. When the player leaves the minecart the avater "zooms" (very fast) from the stuck position to the correct place.

Can reproduce problem on 1.4.2 (SSP / SSP open to lan)