AndrewGaming587
Assigned
Reported
Comments
Cannot seem to reproduce this, might be a hardware specific issue?
can confirm
Can confirm in all versions that released while the bug tracker was down. (Welcome back, Mojira!)
This should really be fixed, it's breaking a lot of tellraw usages in my datapacks (not that they weren't already broken because of hoverEvent being changed to hover_event and clickEvent being changed to click_event) because of \n and removing all of the \n usages makes them look very ugly in-game, especially hover text.
can confirm, also happens with targets selected by a target selector with the nbt= parameter. Also affects 25w04a. Relates to MC-279543, a similar (but not duplicate) bug that I reported myself.
It actually does work, but under VERY specific conditions that I do not know, as I ran the command near spawn, and I got the end spike to spawn, but only in that one specific spot did it work. I don't know why that specific spot worked and not any other that I tried.
EDIT: I figured out the conditions, the spikes only place if you try to place them in the ring where they would spawn in the end. Probably has been a bug since 1.9 if you use a mod to attempt to place a spike elsewhere before /placefeature was added
I think this is intentional, but I'm not fully sure.
Can confirm, happens on the latest version of preview at the time of writing this comment.
can confirm, applies to nearly every sound made by warden
or driver issue? or something?