Adam

I want to keep compatibility, but I need a custom channel so that I can override the transform. Perhaps you could add a way of identifying appropriate custom channels. Maybe...


My vote is for ItemType as opposed to ItemTypes because ItemTypes is meant as a static registry of the vanilla types while ItemType knows about the dynamic registry by ID....

@Cybermaxke Would this API support the use-case of showing an item entity in a shop only to a player who's viewing that shop?

Any sort of status on this?

This still isn't fixed in the API, which was my original point.

one year later

an API PR you mean? I thought you guys only went for API PRs that included implementation

Perhaps instead of a per-plugin thing it could be a per-plugin-host thing, where the server by default only accepts signatures from the Ore public key.

We could definitely do with a way to mark message channels as "for chat-related modification" and "for chat-related global readability".