Difference between revisions of "NetMsgTypes"

(First round of formatting/editing for NetMsg Types. Eventually, this will be a Doxy file.)
(Added TODO)
Line 11: Line 11:
 
Some NetMsgs will need to have custom bodies.  Here is a list of NetMsgs, their related MsgTypes, and links to details on that specific NetMsg:
 
Some NetMsgs will need to have custom bodies.  Here is a list of NetMsgs, their related MsgTypes, and links to details on that specific NetMsg:
  
'''NOTE:'''  This list is not uptodate as of 1.25.11
+
'''NOTE:'''  This list is not up-to-date as of 1.25.11
 
+
'''TODO:'''  Replace this with Doxy files
 
   
 
   
 
{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #666699; padding: 0;"
 
{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #666699; padding: 0;"

Revision as of 18:10, 25 January 2011

NetMsg Generic Templates

The GSNet Protocol provides several Template classes to be used or extended from.

NetMsg MsgTypes

Some NetMsgs will need to have custom bodies. Here is a list of NetMsgs, their related MsgTypes, and links to details on that specific NetMsg:

NOTE: This list is not up-to-date as of 1.25.11 TODO: Replace this with Doxy files

MsgType ID Name Description
0x0050 Failure Uses Generic One Byte Msg.
0x0051 Success Uses Generic One Byte Msg.
0x0100 RemHostNameSET Uses Generic One String Msg.
0x0150 DisconnectREQ "MsgType Only" NetMsg and has no body.
0x0200 NewHostOnNet Uses Generic One String Msg.
0x0250 FullHostListREQ* Not Implemented Yet
0x0255 FullHostList* Not Implemented Yet
0x0300 NewSessionREQ* Not Implemented Yet
0x0305 NewSession* Not Implemented Yet
0x0310 LogoutSession Not Implemented Yet
0x0400 GeometryREQ Uses Generic One String Msg in addition to custom fields.
0x0405 GeometryMANIFEST Not Implemented Yet
0x0410 GeometryCHUNK Uses Generic Multi Byte Msg.