[MC-669] Failing to place blocks in creative mode causes an animation Created: 26/Oct/12  Updated: 09/Sep/15  Resolved: 09/Sep/15

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Minecraft 1.4.2, Minecraft 1.4.5, Minecraft 1.4.7, Minecraft 1.5, Minecraft 1.5.1, Minecraft 1.5.2, Minecraft 1.6, Minecraft 1.6.1, Minecraft 1.6.2, Minecraft 13w42b, Minecraft 1.7.4, Minecraft 14w02c, Minecraft 14w03a, Minecraft 14w03b, Minecraft 14w05b, Minecraft 14w06b, Minecraft 14w07a, Minecraft 14w08a, Minecraft 1.7.5, Minecraft 1.7.10, Minecraft 14w30b, Minecraft 14w30c, Minecraft 1.8.6, Minecraft 1.8.8
Fix Version/s: Minecraft 15w36b

Type: Bug
Reporter: Kevin Reid Assignee: Unassigned
Resolution: Fixed Votes: 6
Labels: input, item

Issue Links:
Duplicate
is duplicated by MC-13820 Right-clicking ground with non-placea... Resolved
is duplicated by MC-14827 If you right click the ground with a... Resolved
is duplicated by MC-21508 Right clicking with any item in creat... Resolved
CHK:
Confirmation Status: Confirmed
Game Mode: Creative

 Description   

If you right-click to place a block, and the block cannot be placed in that location, then in survival mode nothing at all happens, but in creative mode the item animates, sort of like half of the item-switch animation. This is distracting and misleadingly suggests that something happened.



 Comments   
Comment by [Mod] redstonehelper [ 09/Sep/15 ]

Fixed in some 1.9 snapshot.

Comment by david vandian [ 30/Jul/15 ]

Same in 1.8.8

Comment by [Mod] Torabi [ 07/Aug/14 ]

The point of the snapshots is to allow bugs, and attempts to fix them, to be tested before each release. If we only asked for confirmation that bugs still existed in the current release, then more bugs would survive the snapshot phase, and general users who only play releases would be stuck with them for yet another release cycle.

Reporters are not obligated to use the snapshots, though it is very easy to do so using the current launcher, and presents no risk to existing worlds if configured to use a separate directory. The bug tracker is public so that multiple users may contribute to a ticket by commenting on it, and either the reporter or a moderator can update the affected versions based on input from other users. The affects version/s field does accept both the current release and the latest snapshot, so confirmation that the issue still exists in the current release is useful.

All that said, updates to the tracker have given us new tools to manage tickets, and our confirmation policy has changed accordingly.

Comment by [Mod] Ezekiel (ezfe) [ 26/Jul/14 ]

Good point, and we've come across that issue before and switched out behavior before. The current stance is that installing the snapshot is no longer that hard, and that snapshots are considered the most recent version to developers, so if its fixed in 30c, theres no reason to ask if its fixed in 1.7.10. We may change this behavior in the future.

Comment by Kevin Reid [ 26/Jul/14 ]

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.

Comment by [Mod] Ezekiel (ezfe) [ 26/Jul/14 ]

We have an incredibly large number of tickets, and many tickets are bugs that end up getting fixed, or are invalid, but their ticket remains open simply because they get hidden in the collection. By resolving stale tickets, and reopening them at the owners request, we guarantee that only the valid tickets get reopened, which helps reduce the number of invalid tickets in the system.

Comment by Kevin Reid [ 26/Jul/14 ]

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.

Comment by [Mod] Ezekiel (ezfe) [ 26/Jul/14 ]

Is this still a concern in the latest Minecraft version 14w30c? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by Hartspoon [ 02/Mar/14 ]

Still a concern in 14w08a.

Comment by yut951121 [ 20/Oct/13 ]

Can confirm in 13w42b

Comment by Kevin Reid [ 10/Jul/13 ]

Confirmed in 1.6.2.

Comment by [Mod] Ezekiel (ezfe) [ 10/Jul/13 ]

Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.

Comment by fake fakes [ 03/Jul/13 ]

Still in 1.6.1 It happens to all items/blocks that cant be placed there.

Comment by Tails [ 04/Dec/12 ]

Confirmed in 1.4.5.

Generated at Sun Jan 12 11:51:49 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.