UkoeHB
UkoeHB
> We could add as an optional Feature that the Client Webtransport runs in a Webworker. Since im not from the users which often implement games for browsers, im not...
> Im not sure how complex it will be to get this mechanism into this. I would look for the lowest common denominator between renetcode and webtransport, then port all...
@TrustNoOneElse The issues I mentioned would be fixed by migrating your implementation to use the `TransportSocket` trait from #145, which should be very easy. Let's hope poffo merges that.
@TrustNoOneElse can you give more detailed instructions for running the client example? I am having a lot of pain trying to run it. You reference `../pkg` in `package.json` but idk...
This is now implemented in [renet2](https://github.com/UkoeHB/renet2), using this PR as a base.
> Create a publicly accessible SystemSet and add them to important renet systems such as send_packets. So user code can use and configure the execution order of these sets within...
Can you rebase this?
Not totally sure, but the original implementation is in C and stores a lot of stuff on the stack.
> Wrapping that into client_connected() function would have better sound. We need this to run when connecting and connected.
This PR has a bug, since the client needs to update at least once while disconnected in order to send a disconnect packet to the server. The correct run condition...