From 675dee1b5c799f6dcb6e580dd77bfb33dbb2ae65 Mon Sep 17 00:00:00 2001 From: ME1312 Date: Sun, 29 Jul 2018 16:15:29 -0400 Subject: [PATCH] Updated SubData (markdown) --- SubData.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/SubData.md b/SubData.md index d9d123f..a28a1c3 100644 --- a/SubData.md +++ b/SubData.md @@ -13,10 +13,10 @@ This is the current edition of SubData. SubServers.Bungee opens a TCP port (defa } } ``` -`f` — Packet Forward Address (Server-bound only, Optional): Connected address to forward packet to.
-`n` — Packet Channel: Used on the receiving end to decide which set of decoders to select from.
-`h` — Packet Handle: Used on the receiving end to decide which decoder to use from the set selected.
-`v` — Packet Version: Used to determine if the incoming packet is compatible with the receiving code.
+`f` — Packet Forward Address (Server-bound only, Optional): Destination to forward packet to.
+`n` — Packet Channel: Used to determine which set of decoders to select from.
+`h` — Packet Handle: Used to determine which decoder to use from the set selected.
+`v` — Packet Version: Used to verify that the incoming packet is compatible with the decoder.
`c` — Packet Contents (Optional): This is the data that will be passed to the receiving code.
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()`.