Difference between revisions of "HCN"

From HaloNet.Net
Jump to: navigation, search
(Created page with "HCN - Halo Client Networking ---- HCN is a way for servers and clients to communicate with each other. Using Sehe's idea of using chat strings, HCN goes further with generic...")
 
 
Line 4: Line 4:
  
 
HCN is a way for servers and clients to communicate with each other. Using Sehe's idea of using chat strings, HCN goes further with generic key/value pairs, and datapoint and vector updates. It doesn't rely on a data length, instead opting for standard wcslen() (wchar_t) string lengths, and zero encoding.
 
HCN is a way for servers and clients to communicate with each other. Using Sehe's idea of using chat strings, HCN goes further with generic key/value pairs, and datapoint and vector updates. It doesn't rely on a data length, instead opting for standard wcslen() (wchar_t) string lengths, and zero encoding.
 +
 +
Using this methodology, LUA on SAPP should be able to receive and send data. Sehe's NetEvents was not exposed to LUA as far as we can tell, so there has to be a way for SAPP users to communicate with HAC2, and other clients.

Latest revision as of 01:01, 24 March 2019

HCN - Halo Client Networking


HCN is a way for servers and clients to communicate with each other. Using Sehe's idea of using chat strings, HCN goes further with generic key/value pairs, and datapoint and vector updates. It doesn't rely on a data length, instead opting for standard wcslen() (wchar_t) string lengths, and zero encoding.

Using this methodology, LUA on SAPP should be able to receive and send data. Sehe's NetEvents was not exposed to LUA as far as we can tell, so there has to be a way for SAPP users to communicate with HAC2, and other clients.