lucaspoffo

What benefits could we have from having our clearing/updating of events instead of the default behavior? Do you have any different behavior in mind?

Issue about this in bevy_rapier: https://github.com/dimforge/bevy_rapier/issues/216 If I cleared the events in `update_system`, wouldn't it work the same way? Update: I see, we would let the user configure the `update_system`

Is there a way to clear events by default, and optionally let the user do it? Maybe a flag in the plugin :shrug:

Fixed by #34

Yes, My goal for a future version would be to decouple the UdpSocket from the server/client. I'm not sure about the approach yet. Maybe I'll do something similar to what...

I made #36 to move this discussion forward. What would be necessary to make a WASM compatible transport layer for renet? I made a simple Trait and impl it for...

My opinion about this: `Unreliable Sequenced`: I feel this should be implemented using Unreliable channels by the user, the implementation should be simple enough - adding a sequence value to...

When is the deadline? It's wrong in the description, `3rd of April`.

You can bind the socket to `0.0.0.0` (all interfaces). But `0.0.0.0` is not a valid destination to send packets to. You can check that [here](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml). So you would need to...

Public address configuration seems to be a recurring cause of confusion. Adding some common scenarios in the readme or the doc should help, especially about NAT, port-forwarding, dedicated server... Maybe...