Paint
- paint
- paint
- America/Edmonton
- Yes
- No
Angry Zombie Pigmen usually won't jump over 1-highiron bars/glass panes to get to enemies.Angry Zombie Pigmen usually won't jump over 1-high transparent blocks to get to enemies.
When there's a 1 block high obstacle (
has to beiron barsorglass panes) between an angry zombie pigmen and their enemy, they will go up to the bars/panes but usually won't jump over them.When there's a 1 block high obstacle (iron bars, glass panes, enchantment table, glass, ice, or end portal block) between an angry zombie pigmen and their enemy, they will go up to the bars/panes but usually won't jump over them.
When there's a 1 block high obstacle (iron bars, glass panes, enchantment table, glass, ice, or end portal block) between an angry zombie pigmen and their enemy, they will go up to the
bars/panesbut usually won't jump over them.When there's a 1 block high obstacle (iron bars, glass panes, enchantment table, glass, ice, or end portal block) between an angry zombie pigmen and their enemy, they will go up to the obstacle but usually won't jump over them.
Wither Skeletons and Zombie Pigmen won't go through lava to get to enemies, even though they can't burn.
Wither Skeletons and Zombie Pigmen won't pass through a single block of source/flowing lava to get to players even though they can't burn. They get as close to the player as possible, but the lava seems to register as dangerous to them.
The game lags down to 2 fps when the player looks at a cluster of command blocks. Otherwise 30+fps is the average. Only in 14w04a.
See this bug in action: http://youtu.be/nsUtoAhviyM The command blocks all have fill, clone and blockdata commands in them, if that's relevant.
I looked at other tickets before making this one, all the others seem to be affected by other versions, unlike this one.
The game lags down to 2 fps when the player looks at a cluster of command blocks. Otherwise 30+fps is the average. Only in 14w04a.
See this bug in action: http://youtu.be/nsUtoAhviyM The command blocks all have testfor, fill, clone and blockdata commands in them, if that's relevant.
I looked at other tickets before making this one, all the others seem to be affected by other versions, unlike this one.
Ravines don't naturally cut through sand, sandstone, terracottaor myceliumupon generation, but other cave types do.Ravines don't naturally cut through sand, sandstone, or terracotta upon generation, but other cave types do.
1. Create a flat world with a small world border.
2. Make a self-duplicating structure, like [this](http://imgur.com/a/sm83W) (or see attachments).
3. See that even through the border, the structure mechanism is continuing. This is inconsistent with other block-changing blocks such as pistons, which don't extend/retract if they are outside of the border.
But command blocks work outside of the border too, so this might be intended? On the other hand, I thought one of the reasons for the world border was to prevent infinitely-travelling mechanisms such as slime-block piston carriers, and this.
1. Create a flat world with a small world border.
2. Make a self-duplicating structure, like this (see attachments).
3. See that even through the border, the structure mechanism is continuing. This is inconsistent with other block-changing blocks such as pistons, which don't extend/retract if they are outside of the border.
But command blocks work outside of the border too, so this might be intended? On the other hand, I thought one of the reasons for the world border was to prevent infinitely-travelling mechanisms such as slime-block piston carriers, and this.
@ Paint:
That's because it's a bug with LOS (line of sight). This bug causes mobs not to use LOS at all. So yes, that bug will return, but it was never really fixed. This bug just caused it to no longer be expressed.
@Paint, ya just make a new report for it.
Paint gave the ticket to you since the original reporter makes no sign of keeping his ticket updated.




























I had this issue today with 13w21a,b and 1.5.2 (we tried all three). The work-around is to direct connect to COMPUTERNAME:54321. Use the five digits that minecraft gives you when you publish the world. It'll say something like published on 0.0.0.0:54321.
One computer had 64-bit Windows 8, the other Windows 7, and the minecraft versions were always consistent with both computers throughout our trails.
It does not! Resistance V negates all the damage, same as the void problem. Good query.
I did more mining: In fact the /kill problem was reported on before:
MC-16530But that was labelled as a duplicate of a similar problem (wrongly, in my opinion):
MC-10755And that ticket was resolved with "Won't Fix", so... the end?
This ticket might be labelled a duplicate too, but I don't think people should be unwilling to fix this. It's a legitimate bug and it shouldn't be this way in the game.
I don't think this is a duplicate of
MC-10755but rather a more specific problem within it, and still exists in 12w21b.Confirmed in 12w25c.
It doesn't seem right to me that a zombie can spawn on the block right next to you and you have to take instant unavoidable damage. Shouldn't they spawn at a minimum distance away to at least give you a chance?
In 12w36a, you should be able (in theory) to create a scoreboard which tracks how many Spawners have been destroyed. But stat.mineItem.52 isn't a valid objective, and it's because of this bug. The statistics don't track how many Spawners have been destroyed, and it's having a knock-on effect onto new features because they're relying on already-implemented mechanics.
Still present in 13w38a.
Two days from now will mark the 100-day anniversary of this bug being reported. I'm going to throw a party with a banner with invisibility potions on either side, and giant text that reads "100 days! Still not fixed!" There will be grey glowing drinks for everyone (still figuring that part out), served in glass bottles, and big sheets will be provided so we can pretend to be invisible when we actually are not, hence the overall theme of the party.
Can't wait 'til we hit 200. We'll have to upscale the party to include more old will-never-be-fixed bugs like
MC-10099,MC-13497, andMC-5461.Voted upon. I'm trying to make a map and relying heavily on Night Vision as well as 1.7 command features to make it. Thanks for the torch trick, I wasn't aware of that.
I've been trying to summon a thrown custom potion for well over an hour now, it just doesn't work. All you can do is summon a thrown potion that does nothing. I would loved to be proved wrong on this.
I uploaded a screenshot, though I'm not the reporter of this bug.
Confirmed for 1.7.4
Karl, the issue you're having and the issue I'm having must be different. With my magic stained glass, the light is there whether there's a light source or not. How very odd. I also cannot reproduce what you're describing.
If I were to have a wild stab in the dark, I'd say it has something to do with ID 95. This ID was used for locked chest, which had light level 15, now that stained glass has that ID, some piece of code somewhere probably still thinks that block 95s must have light level 15.
I have a build with item frames that crosses over the z=0 line. Item frames on the South of z=0 are fine, but item frames on the north of the line bug out as described here. Odd, considering the build is otherwise perfectly symmeterical.
I was also in a superflat world that just generated a single layer of air.
This isn't a duplicate of
MC-36883. That bug affects versions other than 14w04a, and seems to be inconsistent when this bug is perfectly consistent. This is most likely a duplicate ofMC-45568(which has been mistakenly 'resolved' as a duplicate). I have discovered the source of the lag is actually the item frames I used which duplicate themselves as their items dozens of times over, but only the item frames on the north side of z=0. Item frames on the south side of z=0 are fine.Thanks. I thought if there wasn't a Count value the default was 1. Was this not always the case? Has this changed recently?
Can confirm. I was just checking to see if this had been reported on before I reported it.
Can confirm for 14w05a. I found some oak wood planks where the chests should be, but no chests.
Hello again. This has been incidentally resolved because of the update to mob AI in the 14w06a snapshot and is no longer a bug. Thank-you.
Confirmed for 14w08a.
Confirmed for 08a
A mob that can't burn hides from the daylight, as this is 'working as intended'? Are you sure?
"a 60 second fuse simply doesn't work"
Indeed, since the fuse value can only go to a max of 127 (See
MC-30255, that's intentional). But ignoring that factor, the fuse animation is still independent from the actual fuse of the entity. Use this command:/summon PrimedTnt ~ ~ ~
{Fuse:127}The pause in-between the entity disappearing and the actual explosion is the bug.
Having this bug fixed bug
MC-3626, but now that you fixed this bug, 3626 is probably going to be back.Confirmed for 15w38a
I guess since sword blocking is no longer a feature, this bug doesn't matter anymore? Or is it the same story with shield blocking? I would test myself, but I don't have access to MC right now.
Confirmed for 15w45a and 15w46a.
Confirmed for 15w50a
There's only one mob that I can get to attack me when we're on the same team (in 15w51b) and that's the reinforcement zombies that spawn sometimes when you hit 'leader' zombies. Not sure if that qualifies for its own ticket.
(As of 15w51b) Looks like cave generation does cut through mycelium, but not snow. Also doesn't cut through packed ice (see the 3 most recently-added attachments)
One other little thing to note is that ravine generation follows slightly different rules than other kinds of cave generation, see
MC-94487. I think that ravines will require their own separate fix.Here, you can use Seed 1, and just fly a flew hundred blocks north of spawn. Image attached.
Confirmed for 15w51b.
Confirmed for 15w51b.
Just discovered this bug myself in 1.10.2. Kinda disappointing.
This bug is a duplicate of
MC-1541.Yes, this is still an issue. This means that you can't have scoreboard objectives with criteria stat.killEntity.ender_dragon, as I discovered today.
Confirmed for 16w38a. I was in full regular iron armour and did some tests.
Fire for 8 seconds: 3.5 hearts lost.
Standing on magma for 8 seconds: 3 hearts lost.
Fire + standing on magma for 8 seconds: 3.5 hearts lost.
Relates to
MC-107224: World Border death message states "suffocated in a wall".In 16w38a, I've found that the armor stand is there, but without the Marker tag.
Just found this bug in 16w39b.
Confirmed for 16w39c. Weird bug.
Confirmed for 16w42a. Just discovered this one today, very annoying.
I think we can close this one. Boats haven't done this since before the big boat overhaul of 15w41a.
Yes, this is still an issue.
Please confirm?
I provided screenshots to show that ravines don't naturally cut through hardened clay or mycelium. I used a customised world to prove the mycelium, details in the screenshot.
Confirmed for 1.11.2.
Confirmed for 1.11.2
Confirmed for 1.11.2. I thought I was doing something wrong! Very confusing.
Confirmed for 17w14a.
Confirmed for 1.11.2. Husks can see them too.
[Mod] Neko changed my report from "Villagers don't run away from Illusion Illagers" to "Villagers don't run away from Illagers", but this bug only applies to the illusion illagers, they run away from the other two types of illagers as expected.
Confirmed for 17w17a. I know this isn't high-priority, but since the upcoming update is 'World of colour' and note blocks have been worked on, perhaps it's time to bring back the vibrantly-coloured note particles.
It seems as though Wither Skeletons don't know they're immune to fire.
Relates to
MC-13497.Relates to MC-116510.
Relates to MC-118740.
Confirmed for Minecraft 1.12.2. Terrible bug!
Relates to
MC-13497.This is also the case for stat.diveOneCm. Should we add that to this bug report instead of making a new one?
Confirmed for Minecraft 1.12.2 and 17w46a.
Relates to MC-122656.
This is fixed in 17w49a, but there are two things still not right:
1. The criteria for breaking banners now exists, but never increases score (
MC-122939).2. The criteria for breaking fire exists but never increases. Is it supposed to increase score when you put out fire with your fist? Or is it not possible to "mine" fire?
All the others exist and work as intended. I tested them all. There are some that have been re-named or act differently than they were intended to when this bug report was made, but those are the only two problematic issues.
Fixed in 17w49a. It's called minecraft.crafted:minecraft.tipped_arrow
Confirmed for 17w50a. Affects all things that can use JSON to display scores, so written_books as well.
Duplicate of MC-16663?
Confirmed in 17w50a. Found this one today.
Cannot reproduce in 17w50a, instead I get this message in the chat: java.lang.NullPointerException
MIchael, at first I didn't realise you had to reset the settings back to default to trigger the bug.
Windows 10
Cannot reproduce in 18w02a. I guess it's fixed?
Can confirm. Relates to
MC-122939.TL;DR: Fixed in 18w08a.
In 18w08a, ravines changed. They don't generate where they did in previous versions (using the same seeds and locations), so I had to find new surface-ravines or would-be surface-ravines to see what they cut into.
Sand & Sandstone:
Ravines now cut through these. Seed: 1
Location: /tp @s -10360 75 39780
Red Sand & Terracotta:
Ravines now cut through these. Seed: -635205980
Location: /tp @s -805 70 -188
Mycelium/Snow Blocks:
Can't find surface ravines or would-be surface ravines in these biomes. Much harder now that we can't use Customised Worlds to generate a world of just that biome. But even if they don't cut through those,
MC-16132exists for that.Conclusion: Fixed in 18w08a.
Confirmed for 18w14b. Just found a taiga village covered in trees.
Confirmed for 18w31a.
Confirmed for Minecraft 18w32a. Mildly infuriating.
In 18w32a, I noticed there were no subtitles for the beacon sounds.
Confirmed for 18w32a.
This ticket needs Reproduction steps. Here's what I would write:
—
Player A's hunger bar will work as intended, but Player B's hunger bar will regenerate haunches during and after the effect. This is purely visual, as they will starve to death. Every tick of starvation damage will reset the hunger to its correct value, but it will continue to visually regenerate inbetween those damage ticks.
—
This ticket's affected versions also keeps to be kept updated, I'd be ok with being the reporter.
Confirmed for 18w33a
Works as intended.
Is this still a thing?
Confirmed for 1.13.2
This bug allows you to stand on the edge of a magma block and not take any damage.
The same problem exists when you punch an end_crystal. Interestingly, if you shoot an end_crystal, the direct_entity isn't anything at all. MC-165111
This bug should mention something about advancements so people don't duplicate it as much.
Crossbow-fired firework rockets won't trigger the player_killed_entity advancement unless the player damages the entity in some other way prior. Interestingly, if you do this, the advancement will correctly consider the killing_blow to be explosion damage, even if the prior hits that made the advancement work weren't explosion. However it doesn't count as projectile damage.
Confirmed for 1.14.4
Mods please confirm. This bug is bananas! Even the vanilla datapack is invalidated if you have any invalid data tags anywhere, and the error messages are no help at all.
Confirmed for 1.15.2. Add using an iron ingot on a damaged iron golem to the list.
Update: Changed this ticket to include the trident, which works the same way as the elytra now.
Confirmed for 1.15.2.
Confirmed for 1.15.2. When I turn my subtitles off, there's no underlines at all!
Update: Seems to have been fixed overnight.
Here's my steps of reproduction:
1. Use seed -5541185355023925660 and go to exactly
/tp -5831 66 -4607. You might find yourself inside a tree.
2. /locate Desert_Pyramid, it's 241m away.
3. Go 1m north. You should pass through a chunk border doing this.
4. /locate Desert_Pyramid, it's 1060m away!
Confirmed for 20w13b.
Confirmed for 20w14a.
Confirmed for 20w16a
Confirmed for 20w16a.
Update: Included the same problem with respawn anchors.
Cannot reproduce in 20w19a. Looks like it's fixed.
You can't detect the damage/killing of any mob of an exploding bed/respawn anchor with an advancement. See MC-165109.
It was! I had no idea.
Confirmed for 20w20b
Confirmed in 20w20b
Fixed in 20w21a.
Confirmed for 20w21a
Confirmed for 1.16 Pre-release 2
Confirmed for 20w30a. This overlap of functionality is annoying. I can't detect a player removing a music disc from a jukebox without also detecting when a player places a block against an empty jukebox.
Confirmed for 20w30a.
Confirmed for 1.16.2 pre-1. I don't know if this is a separate issue, but placing the block itself will trigger the item_used_on_block criteria if the item is not defined and if you are replacing a non-air block by placing it (like grass or fern).
So do End Portal blocks.
Seed: -1777561445
Co-ords: /tp @s -1419 21 1875
The instructions are vague. What does the L look like? I tried a few interpretations and can't reproduce this in 1.16.2.
Can't reproduce in 1.16.2
Can confirm for 1.16.2.
Can confirm for 1.16.2.
Confirmed for 20w46a.
This got me curious about what would happen if geode generation overlapped with an end portal, so I found one example of that, but thankfully the end portal room is perfectly preserved. See for yourselves:
Seed: -1533097473925923742
Location: /tp @s 19870 45 -2444
Relates to
MC-203753.Is it also intentional that this still happens in the nether?
Cannot reproduce in 21w10a. Bees sting as intended.
Confirmed in 21w11a.
No, that's a different issue with a different target selector argument.
Confirmed for 21w11a.
@Numeritos The Ender Dragon & Exit Portal Fountain don't spawn
Can confirm in 21w14a.
Confirmed for 21w44a.