Plugin channel: Difference between revisions

From wiki.vg
Jump to navigation Jump to search
imported>Md 5
imported>Pokechu22
(Pokechu22 moved page Plugin channel to Plugin channels over redirect: I really prefer the plural form; it's much easier to use and works better for subpages.)
 
(29 intermediate revisions by 7 users not shown)
Line 1: Line 1:
'''Plugin channels''' are implemented using [[Protocol#0xFA|packet 0xFA]], allowing client mods and server plugins to communicate without cluttering up chat. [http://dinnerbone.com/blog/2012/01/13/minecraft-plugin-channels-messaging/ This post by Dinnerbone] is a good introduction and basic documentation.
#REDIRECT [[Plugin channels]]
{{anchor|Internal}}
== Channels internal to Minecraft ==
As of 1.3, Minecraft itself started using plugin channels to implement new features. These internal channel names are prefixed by <code>MC|</code>.
=== <code>MC|BEdit</code> ===
''Client to server''
 
When a player edits an unsigned book.
 
This payload is simply a set of bytes corresponding to an ItemStack. It is serialized / deserialized exactly the same as itemstacks in packets.
 
=== <code>MC|BSign</code> ===
''Client to server''
 
When a player signs a book.
 
=== <code>MC|TPack</code> ===
''Two-Way''
 
Remote texture packs.
 
===  <code>MC|TrList</code> ===
''Two-Way''
 
The list of trades a villager NPC is offering.
 
=== <code>MC|TrSel</code> ===
''Client to server''
 
When a player selects a specific trade offered by a villager NPC.
 
== Notable community plugin channels ==
Channels listed in this section are not Mojang-sanctioned. This is just a likely-incomplete list of channels used by mods/plugins popular within the Minecraft community.

Latest revision as of 20:56, 9 April 2016

Redirect to: