Skye Anastasion
- Lilithvia
- lilithvia
- Europe/Stockholm
- Yes
- No
On a world upgraded from last year's latest 1.17 snapshot, attempt to dye a dark oak sign. I believe there's something broken by the addition of glow ink, because both attempting to dye the sign with a normal color, and attempting to make the sign glow will not work, as no visible changes to the sign occur.
Should also mention that placing signs on other signs when not shifting being broken seems to be a feature in snapshots.
Projectiles (including arrows) sometimes pass throughmobs without hitting themProjectiles (including arrows) sometimes pass through Entities without hitting them
Relates to MC-214546 and other similiar, but not quite the same bugs such as MC-125936.
Skeletons shooting arrows can have their arrows bounced off a shield, through them, and into another mob. Initially discovered this bug while caving and used it to kill bats, but during testing found this can be used from everything from getting zombies to attack skeletons to creeper farming.
Testing also confirmed that this is abusable as long as you are between 1.1 and 4ish blocks away.
Relates to MC-214546 and other similiar, but not quite the same bugs such as MC-125936.
Skeletons shooting arrows can have their arrows bounced off a shield, through them, and into another mob. Initially discovered this bug while caving and used it to kill bats, but during testing found this can be used from everything from getting zombies to attack skeletons to creeper farming.
Testing also confirmed that this is abusable as long as you are between 1.1 and 4ish blocks away.
List of Related bugs:
MC-214546
MC-125936
MC-147233Skeletons shooting arrows can have their arrows bounced off a shield, through them, and into another mob. Initially discovered this bug while caving and used it to kill bats, but during testing found this can be used from everything from getting zombies to attack skeletons to creeper farming.
Testing also confirmed that this is abusable as long as you are between 1.1 and 4ish blocks away.
No, it definitely relates though. Adding to OP.
Using a repeating command block while your character is surrounded by a ring of blocks to keep your character from moving while summoning in cows into a smallish pen via a repeating command block will cause minecraft to stop responding within a relatively short period of time due to minecraft trying to handle more than 247 sounds at one time, and thus preventing you from doing anything, including shutting the command block off.
Console continues to log warnings and info even AFTER the game has been force closed.

Can confirm it is present in 1.12.2
I think this is working as intended, water in minecraft is usually supposed to drip through one block thick layers of any material.
That is kind of their issue.
Let the mods deal with that
Can you try opening the simple chests to see if there is a double chest inventory, or just two single chest inventories?
Just use double layers then
Yeah Matthew, search seems to be broken, I couldn't find it before posting an issue concerning minecarts being offset from the rails.
Vio, I've seen players make item elevators using bubble columns with flowing water
Not sure if that relates since the projectiles spawned several blocks away.
@theduke Did you mean to comment that on another issue?
Game does not crash, it stops responding and then stalls. Game continues to output to the log even while it's not responding, and even after you force close it.
I assumed that updating affected versions was a thing the mods did, as the only update I posted was the snapshot version, and mods would update when someone confirmed the bug for a new version as happens with many other bugs. If you want versions added, just do what Avoma and co have done, as I have a job (and playtest other games in my freetime) and can't always confirm it exists on new versions (especially since I've encountered the bug three to four times ever when I do test for it. I suppose I could write a bot to shoot the bow for me and then detect when the arrow doesn't collided with the mob after a certain amount of time to test on eash version, though,
By focusing on one thing trying to usurp a freaking bug report from someone instead of commenting what versions are currently affected and aren't listed, all you are doing is wasting everyone's time.
As I said in my previous post, which you failed to read:
Do what Avoma has done and post versions you can confirm this bug on, and it will be added to the report. Otherwise you are creating unnecessary drama.
Finally, some useful info.
Adding it to the list.
confirming and updating for 1.19 pre release 1
I'm locked out of my microsoft account, but if someone could, it might be helpful to see exactly how far back this goes so that Mojang can narrow down exactly what changes might have started causing this.
Can confirm in 1.14, took 3 weeks of monitoring a slow-fired creeper farm built exclusively for testing for this to find, but can be repeated fairly easily once it does, not sure why