Lincoln Bryant

Hi! I have a question/issue about what happens when out-of-order reliable packets come in. I see here https://github.com/flambard/enet/blob/master/src/enet_channel.erl#L147-L150 That you have the following: ``` {recv_reliable, { #command_header{ reliable_sequence_number = N...

``` message entity { required uint64 id = 1; required vector2 position = 2; optional vector2 velocity = 3; // doesn't work as OPTIONAL and VECTOR2 in this message. investigate!...

It seems that reliable, and unsequenced packets work fine, but unreliable packets never seem to get sent or possibly received by Godot. needs further investigation

For ENet, we automatically set compression on the server side: ``` % Start ENet Options = [ {peer_limit, ?PEER_LIMIT}, {channel_limit, ?CHANNEL_LIMIT}, {compression_mode, zlib} ], ``` And on the client we...

It seems that if `s2c_call` and `c2s_proto` are both specified in the Overworld RPC definition, they have to match else the bindings fall back to using the handler function name...

there's a lot of interesting things to have as metrics * number of connections * per session stats for ENet clients (resends, discards, etc) * number of zone servers running...

Publishing to hex complains about the lac of docs 🤭 ``` ===> Published overworld 1.0.0 ===> No valid hex docs configuration found. Docs will will not be generated ```

This WIP commit massively revamps session handling such that sessions are a separate process and everything refers to them by ID. Approximately following this workflow I mapped out: > Connection:...

There's somewhat of an asymmetry with encoders and decoders. Decoding is hard because we route messages based on a prefix, but we only assume 1 'app prefix' per Overworld application....

There seems to be plenty of dead wood to clear out. I finally figured out from reading the code: ``` $ curl localhost:4433/client/manifest ["libow4.gd","chat.proto","overworld.proto"] $ curl localhost:4433/client/download > client.zip $...