Prior to 1.20.2 introducing the always_kills_armor_stands tag, shulker bullets popped harmlessly on armor stands, and this mechanic was used in some popular shulker farms to destroy stray bullets or stop them from hitting shulkers when they shouldn't. Check this timestamped vid for a ~1 minute explanation.
Unfortunately, the change went unnoticed by farm designers until just before 1.20.2 released due to it being glossed over in the patch notes, so there wasn't really time to request a reversion. We also assumed a report would just be closed as WAI, but when the topic came up in slicedlime's stream a few days ago, he encouraged me to file one.
Ultimately it's nothing like the end of shulker farming if this is not reverted, but it was IMO a nice mechanic that worked very well for this niche use case, and the change broke some cool farms.
Linked issues
relates to 1
Attachments
Comments 8
Just my 2 cents: In general I am okay with this change, but would be nice to know if it is WAI, as it is a nice mechanic for a lot of different farms with very few workarounds. For shulker farming it is only a minor annoyance (possibly even opens up more options), but it does break people's existing farms.
I can also confirm this, I was looking at making a new shulker farm (because updating to 1.20.2 broke my last one) and found out that the one I was trying to make won't work because shulkers are breaking the armor stand. I really hope this gets solved.
I'm new to watching bug tickets, but after seeing it as "Resolved" I've checked my shulker farm in 1.20.3 and the issue is still there. The Shulker Bullets are destroying the armor stand.
Look further than status; it was resolved as fixed for "Future Hotfix", however, that was an accident and it has been reopened.
You're not going to see an immediate change in-game when something gets resolved as fixed, you'll need to update first in those cases.
Additionally, resolved does not always mean fixed, look at the resolution of a resolved report to see what resolution it got.
Yeah, unmentioned changes should just be reported. Even if it ends up getting WAId, at least then you know it was an intentional change. But chances always are unmentioned changes are accidental.