MC-179940 covers the player’s base attributes, which are preserved upon death; that fix does not however extend to attribute modifiers.
Still present in 1.21.11
This is still an issue in 1.21.7.
This affects sign, book, and chat click events, but the quickest way to test this is using dialogs.
Steps to reproduce: Start a multiplayer server, deop yourself, and run this command from the console:
/dialog show @p { "type": "minecraft:multi_action", "pause":false, "after_action": "none", "actions": [{ "label": "Click here!", "action": { "type": "run_command", "command": "trigger dummy add 1" }} ], "title":"MC-101859"}After that, either click the button repeatedly, or tab-select it and hold down the spacebar. After a certain number of uses, the player is kicked for spamming.
This only happens if the player does not have operator permissions, happens regardless of whether or not the command is successful, and happens regardless of whether or not command feedback is enabled - which means the player can be kicked for spamming the chat without even sending anything visible to chat. And there is no setting to disable this.
Given that the original creator of this ticket seems not to have migrated their account to the new bug tracker, I would be willing to take over maintaining this report once it is re-opened.
Affects 1.21.6 release candidate 1.
Confirmed in 25w06a.
Confirmed in 1.21.4.
Still present in 1.21, and might be a little more impactful than just a couple of error messages. Some changes to tags even seem to persist between worlds; adding a new item to #minecraft:stone_tool_materials in one world, exiting, and loading another will carry over and allow the newly-added item to be used to repair stone tools in an anvil, even without any datapacks loaded, until the game is rebooted.
Confirmed in 1.20.6 and 1.21 release candidate 1.
This is still an issue in 1.21 release candidate 1, and I think I know what the problem is: If the target structure generates on a chunk border at the edge of the map, the marker doesn't render. So if the structure is at, say, -576 by 576, and the top-left corner of the map is at -576 by 448, I guess the marker is being seen as "off" the edge of the map and gets disregarded. Probably why buried treasure chests always generate in the middle of a chunk, but explorer maps to other structures don't necessarily get that safeguard.
So, likely a symptom of MC-158546.
Can confirm in 1.21 pre-release 2. Easily seen if you place an armor stand and relog. This is, to put it mildly, catastrophic to any map or datapack that uses display entities in any capacity.
In 1.20.5 release candidate 1.
Confirmed in 1.20.5 pre-release 3.
@Jiingy: Shoot, you know what, I just dug into one of my resource packs and it's got the formatting codes baked into the translation string in en_us. I guess to stop the name showing up as italicized back from when that was an issue, or something.
Which, I mean, I guess you could say "formatting codes parsed from translation strings aren't properly cleared when renaming item" is still an issue, but eh, I'm content to just call a mulligan on this one.
Affects 24w11a.
As of 24w09a the command is now /give @s armor_stand[minecraft:entity_data={id:"minecraft:armor_stand",Small:1b}]
Still present in 1.21.11. Also applies when using
/item modify. I can take over maintaining this report since the original creator seems not to have migrated their account.