Recent content by Machine Maker

There is the VillagerAcquireTradeEvent event that can be used to modify trades.

Run the /difficulty command in the world you are expecting the zombies to break doors in.

You have invalid player skulls somewhere. Mojang recently change something in their API which manages skins, player names, UUIDs and such. And previously valid skulls which make requests (to get the player skin) aren't anymore.

There are plugins that let you filter logs. This is one such example.

If you are playing on the vanilla server, this isn't really the place to ask for support. This is the Paper forums, which is a modified server (aka NOT vanilla).

Well, it doesn't look like you are using a supported way of accessing NMS. we only support 1.17+ here and nms via paperweight which deobfuscates all fields/methods/classes to their correct mojang names.

Adding custom enchantments isn't supported by the API. You have to use reflection to allow the registering of new Enchantments (see what the registerEnchantment method does and checks to see if its valid). For some things, you have to use nms (or reflection) to add an enchantment to the NMS...

This is a very not good way to get the text. What happens if I set the display name of an itemstack to a translatable component, or some other component type? Casting it to TextComponent isn't going to work then. Like others have said, there are very few legitimate reasons to want the plain text...

Well the problem is an invalid skull. And if no placed skulls existed in any world, that error wouldn't appear. So you haven't removed all skulls. I think this is due to mojang changing something with their skin/game profile api.

Where on the itemstack nbt tag tree is this stored? I think Paper only limits the length in some places. Like is this being added to the Lore or smth?

/summon minecraft:armor_stand ~ ~ ~ {Small:1b} works fine for me on a paper server. Make sure you are trying this without any plugins or datapacks installed.

Correct, but that’s not an entry. The entry itself still doesn’t support anything more than legacy strings. Team prefixes/suffices aren’t the same thing, and yes, they do work.

Yeah, that's a bug. I'll PR a fix for it. EDIT: Here's the fix

In what part of the scoreboard? Entries are just strings, so the only colors that show up there are legacy strings. Which do not work with hex colors. EDIT: ^This is a vanilla client thing, not something that Paper can fix (or spigot, or purpur for that matter) Other parts of the scoreboard...

Can you post some reproduction steps? And provide the datapack, or a trimmed down datapack that demonstrates what's broken.