Upstream/SubServers-2
1
0
Fork 0
mirror of https://github.com/ME1312/SubServers-2.git synced 2025-02-17 20:21:33 +01:00
Code Issues Projects Releases Wiki Activity

Updated SubData (markdown)

ME1312 2018-07-29 16:15:29 -04:00
parent 56944504a8
commit 675dee1b5c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
SubData.md

@ -13,10 +13,10 @@ This is the current edition of SubData. SubServers.Bungee opens a TCP port (defa
}
}
```
`f` &mdash; Packet Forward Address (Server-bound only, Optional): Connected address to forward packet to.<br>
`n` &mdash; Packet Channel: Used on the receiving end to decide which set of decoders to select from.<br>
`h` &mdash; Packet Handle: Used on the receiving end to decide which decoder to use from the set selected.<br>
`v` &mdash; Packet Version: Used to determine if the incoming packet is compatible with the receiving code.<br>
`f` &mdash; Packet Forward Address (Server-bound only, Optional): Destination to forward packet to.<br>
`n` &mdash; Packet Channel: Used to determine which set of decoders to select from.<br>
`h` &mdash; Packet Handle: Used to determine which decoder to use from the set selected.<br>
`v` &mdash; Packet Version: Used to verify that the incoming packet is compatible with the decoder.<br>
`c` &mdash; Packet Contents (Optional): This is the data that will be passed to the receiving code.<br>
Of course, SubAPI handles this all for you, but if you are looking to create a custom application this information may be useful to you. The SubAPI way to create a packet is to create a new class and implement `PacketIn` and/or `PacketOut` and register it via `SubData.registerPacket()`.