Flei tech pro 2041

[19:23] <longbyte1> hello
[19:23] <longbyte1> anyone on?
[19:23] <Fleischy> maybe
[19:24] <longbyte1> I'm trying to make a simple client for educational purposes
[19:24] <longbyte1> I have the ENet stuff down, but I have to send some magic packet to the server when I connect
[19:25] <Fleischy> sounds amazing
[19:25] <longbyte1> Unfortunately, it seems that only server -> client packets are documented, not the other way around
[19:25] <Fleischy> I have absolute faith in your abilities
[19:26] <longbyte1> so I'm looking at how openspades does it
[19:28] <longbyte1> and this line is the most concerning right now: https://github.com/yvt/openspades/blob/master/Sources/Client/NetClient.cpp#L391
[19:28] <DerpyBot> "openspades/Sources/Client/NetClient.cpp at master · yvt/openspades · GitHub" at github.com
[19:29] <longbyte1> that fourth parameter is the data, which means that I'm supposed to send the server's protocol version
[19:29] <longbyte1> so I send 3, still times out
[19:30] <Fleischy> that's troubling news
[19:32] <learn_more> do you poll for events with enet_host_service?
[19:32] <Fleischy> maybe
[19:36] <longbyte1> yes, but I'm not familiar with enet_host_service because I'm using node.js. It has an enet package and it conforms to the documentation. So the equivalent would be peer.on("event", function() {});
[19:36] <Fleischy> that's just the way it's gotta be