I have this issue very commonly when playing in Multiplayer (using the friends tab), when in the End it is a constant fight for our lives. If I look at an obsidian pillar that an Enderman is behind, the Enderman engages me. Despite having potions and 5 other players it was the most difficult Ender Dragon encounter I have ever faced personally, and we were forced to retrieve carved pumpkins to explore the outer islands and raid end cities if we wanted to survive.
However, when I try to replicate this on Singleplayer, I did not get attacked once while running around the island, and I made sure to place some walls and look at pillars when I know Endermen are behind them, and I never once got aggro.
This issue seems to be a bit more complicated than first glance, hopefully others here can state whether they ran into this issue on Singleplayer or Multiplayer. Hopefully sometime soon I can try to provide more Multiplayer data.
Can confirm this is still the case in 1.15 Pre-Release 1
Confirming for 1.15 Pre-Release 1, tested with Bow, Trident, and Crossbow
Can confirm this is still active in 1.15-Pre-Release 1
Can confirm this is still an issue in 1.15 Pre-Release 1, sorry for not posting an update in a while!
I believe gaspoweredpick means 1.14.1 Pre-Release 1 😉
I third this, I would love to see this bug fixed. Map making can be tough when ideas you have are ruined by bugs, and it hurts to see one of them marked as "Will Not Fix" without a given reason. At the very least, a reason would be great
Can confirm for 1.14. North is the top one. This also affects Tridents
[media]Can confirm for Minecraft 1.14
Can confirm for Minecraft 1.14. Although you can replace a bed with two Impulse Command Blocks set to "Always Active" (so it replaces itself with a bed the second it's placed in the structure) there's no good way to have that be compatible with rotated structures.
I'm not sure where the game defines those pools, village Decorations (hay bales and stuff) don't seem to even have structure files in the jar, that I can find anyways. Except for the flower planter.
I haven't messed with that functionality of Jigsaw Blocks, but i've heard you can use them to overwrite vanilla structures, just can't make your own.
Can confirm for Release 1.14.
I understand this is likely intentional, but we still have not received official word on that, or why it is like that. I'll keep updating this until we get an official answer.
Also, Dag Hef, the Wiki is written by players, not Mojang. I've myself made edits to the Wiki, so never take it as official answers. HOWEVER the Wiki does provide a Source to the Crowdin website, which states: (in the context of block.minecraft.jigsaw)Â
It is a junction block that allows to construct structures out of smaller templates.Â
Think about "Jigsaw Puzzle" when translating
So to me, that is odd. "that allows to contruct" seems to be missing "the players", but there is room for it, the sentence is broken without it. In the [translation history|https://crowdin.com/project/minecraft/activity_stream?translation_id=5201242&lang=99] it does not appear to have ever included that missing word. So it appears to be a mistake on the Wiki.
Can confirm for Minecraft 1.14. This bug report was marked as a Duplicate, yet the post linked does not appear to be the same bug. Iron Golems can still kill a hostile mob on the same team, but only IF that hostile mob is RIDING the Iron Golem.
If you summon /summon iron_golem ~ ~ ~ {Team:"Test"} and also ~/summon silverfish ~ ~ ~ {Team:"Test"} as the same Team, for this example we'll be using the team Test. Make sure to create the team ahead of time: /team add Test~ and run /team modify Test friendlyFire false
You'll see those two mobs ignore each other.
Now run: ~/summon iron_golem ~ ~ ~ {Team:"Test",Passengers:[{id:"minecraft:silverfish",Team:"Test"}]}~
You'll quickly see the Iron Golem kill the Silverfish
Can confirm for 19w14b aswell
Actually upon further testing, you can create a functional function (pun intended) by saving the text file under the encoding type called UTF-8 (NOT UTF-8 BOM). Which can be done with Notepad++ for example
Can confirm this for the latest snapshot 19w14b
Can confirm for minecraft 19w11b, it should only take 3 baby villager kills to have enough "negative reputation" (if we assume it works like it used to) to trigger Iron Golem hostility, but they never become hostile. It looks like Iron Golems don't remember what Village they're a part of, but they do stay near the Village.
Is that confirmed? I cannot find any information about how it is supposed to work anywhere other than people guessing on YouTube. I'd love to see a source. I should note, i'm not the person who submitted this bug report, I was simply updating it to confirm it was still the case in the latest snapshot.
I understand how it currently works, and that this block may not even be intended to be used by players in game, but its worth having this bug report and keeping it up to date so we can one day get an answer about it. I am desperately waiting to find out, as my current map is requiring hundreds of structure blocks to pull random structures, whilst a jigsaw block would simplify the entire thing immensely and save me many hours.
So my framerate has been going down for quite a while in my original world I made over 10 years ago. I attributed it to age and the amount of stuff I have, but recently noticed I had 900 entities loaded, and my framerate was low because I had over 300 rendered.
They turned out to be mostly Endermen, and it took a lot of looking (by that I mean X-ray glitch, finding them would have been difficult). Dozens of endermen clumped up in small holes in the cave floor, surrounded by their collection of dirt, gravel, and mushrooms. A prison of their own making, unable to despawn due to the stuff in their hands.
This takes a long time to make an impact on the game, many many hours since 1.16 when this seems to have started. The biggest issue seems to be that the Endermen somehow become unable to teleport, despite the fact they have plenty of valid areas nearby. They did still teleport after being hit, proving that there were valid areas nearby.