summaryrefslogtreecommitdiff
path: root/doc/protocol.txt
diff options
context:
space:
mode:
authorPerttu Ahola <celeron55@gmail.com>2011-06-18 20:16:11 +0300
committerPerttu Ahola <celeron55@gmail.com>2011-06-18 20:16:11 +0300
commit28a8218adfa103361b9ea371eae5aa093b6d7e29 (patch)
tree9a11ca168c5ed016b622c51cdaee9dae4a57175e /doc/protocol.txt
parent5d1ae85ab9829ab38b96277a8cd63e4539774e06 (diff)
downloadminetest-28a8218adfa103361b9ea371eae5aa093b6d7e29.tar.gz
minetest-28a8218adfa103361b9ea371eae5aa093b6d7e29.tar.bz2
minetest-28a8218adfa103361b9ea371eae5aa093b6d7e29.zip
Documentation update
Diffstat (limited to 'doc/protocol.txt')
-rw-r--r--doc/protocol.txt32
1 files changed, 32 insertions, 0 deletions
diff --git a/doc/protocol.txt b/doc/protocol.txt
new file mode 100644
index 000000000..b7b433c9e
--- /dev/null
+++ b/doc/protocol.txt
@@ -0,0 +1,32 @@
+Minetest-c55 protocol (incomplete, early draft):
+Updated 2011-06-18
+
+A custom protocol over UDP.
+
+Initialization:
+- A dummy reliable packet with peer_id=PEER_ID_INEXISTENT=0 is sent to the server:
+ - Actually this can be sent without the reliable packet header, too, i guess,
+ but the sequence number in the header allows the sender to re-send the
+ packet without accidentally getting a double initialization.
+ - Packet content:
+ # Basic header
+ u32 protocol_id = PROTOCOL_ID = 0x4f457403
+ u16 sender_peer_id = PEER_ID_INEXISTENT = 0
+ u8 channel = 0
+ # Reliable packet header
+ u8 type = TYPE_RELIABLE = 3
+ u16 seqnum = SEQNUM_INITIAL = 6550
+ # Original packet header
+ u8 type = TYPE_ORIGINAL = 1
+ # And no actual payload.
+- Server responds with something like this:
+ - Packet content:
+ # Basic header
+ u32 protocol_id = PROTOCOL_ID = 0x4f457403
+ u16 sender_peer_id = PEER_ID_INEXISTENT = 0
+ u8 channel = 0
+ # Control packet header
+ u8 type = TYPE_CONTROL = 0
+ u8 controltype = CONTROLTYPE_SET_PEER_ID = 1
+ u16 peer_id_new = assigned peer id to client (other than 0 or 1)
+