mojira.dev

Kevin Reid

Assigned

No issues.

Reported

MC-27261 Larger-than-possible windowed resolution causes clipped display Awaiting Response MC-22737 When sky light is blocked it does not update below water Duplicate MC-13129 Floating/grounded restriction on tripwire behaves inconsistently. Invalid MC-12017 Can get permanently stuck in a minecart in a nether portal Fixed MC-8471 Blocks cannot be placed on a block you are next to Fixed MC-6266 Hoppers grab items too far away Works As Intended MC-3674 Vines can no longer grow past glass Cannot Reproduce MC-2034 Brewing stands' input slots do not have normal stacking behavior Fixed MC-1080 Mob fire graphics do not match death animation Works As Intended MC-676 Signs and chests do not display cracking animation Fixed MC-674 Items different only in damage cannot be swapped Fixed MC-672 Right-clicking on a brewing stand's input does not split the stack Duplicate MC-671 Minecarts with Furnace consume coal in creative mode Fixed MC-669 Failing to place blocks in creative mode causes an animation Fixed MC-665 Minecarts and TNT are not moved by water currents Fixed

Comments

(I no longer play Minecraft much at all these days so someone else will have to check.)

The screenshots produced are now complete instead of having black bars, but the in-game display is still cut off at the top.

Note that my previous remark that an alternative to getting this right would be “Fix fullscreen so that Cmd-Tab application switching works” is even more relevant today: Mac OS X (er i mean macOS) now has an even better fullscreen system, which actually can be used with Minecraft by clicking the green title bar button, but this is not remembered when the game is quit like the built-in fullscreen option. Ideally the two would be the same — both switch-allowing and remembered across restarts.

In 1.8.1-pre3, specifying a too-large size still causes the window contents to be cut off at the top. I don't get a black bar in screenshots.

Confirmed for 1.8.1-pre3. However, the effects have changed slightly.

  • Tripwire behavior (when it sends a redstone signal) is still inconsistent as described.

  • I no longer see the spontaneous toggling or sounds.

  • NEW: The hooks with blocks under them have glitched models: the metal hook part is separated from the wooden arm.

Confirmed for 1.8.1-pre3. I had a skeleton shoot a zombie and the zombie then did not attack either me or the skeleton.

Hm, I see the point that there's a lot of noise. I wish you would at least request updates for the most recent release version, not snapshots (unless it was a bug introduced in a snapshot). A reporter shouldn't need to install pre-release versions just to usefully report a long-standing bug.

Confirmed for 14w30c.

Confirmed described behavior for 14w30c.

Dear mods, do old bugs (as opposed to ones that were, say, introduced in the current snapshot series) really need this frequent of reconfirmation? I think it's much more likely to cause a false closure if the reporter(s) aren't persistent, and IMO reporters shouldn't be obligated to install snapshot versions.

The described behavior still occurs in 14w30c.

Still in 14w30c.

Dear mods, do old bugs (as opposed to ones that were, say, introduced in the current snapshot series) really need this frequent of reconfirmation? I think it's much more likely to cause a false closure if the reporter(s) aren't persistent.

Confirmed for 14w30c.

Confirmed for 14w30c

Confirmed for 14w21b.

Agreeing, 14w18b shows no gap.

Retested, shows the same behavior as in my original report on 14w05b.

Confirmed for 14w04b.

Confirmed in 14w04b: behavior appears to be identical to previous versions.

Stairs placeable intersecting the player confirmed for 14w04b. Note that you must be standing on the lower half of a stair block for this to happen as originally described.

Lily pads placeable intersecting the player confirmed for 14w04b, no special conditions. I stand by my previous claim that MC-667 should be considered a different bug than this, as lily pad placement is unlike regular block placement and the code causing the bug is most likely different.

In 1.7.4 (current release), the behavior is as described in the original report.

Confirmed in 14w03b.

However, the misbehavior has changed slightly: right-clicking on a stack in the stand will appear to split the stack and pick up half, and allow you to place it in your inventory, but on exiting and returning to the brewing stand GUI you will see the entire stack moved instead. Looks like client/server desync and the server implementing the buggy behavior.