Johan Klokkhammer Helsing
Johan Klokkhammer Helsing
Closes: #419 Blocked by: https://github.com/gschup/bevy_ggrs/pull/106 and bevy_ggrs crates.io release
Depending on bevy without `default-features` have so many footguns and tend to break on every bevy upgrade, and break in different ways on wasm and native. Depending on default features...
It would be good if there were fewer manual steps involved in releasing. Current manual steps: 1. Update bevy version support table in readme 2. Release on crates.io ``` cargo...
With Axum 0.7, some high-level API we depended upon was removed, so the upgrade is not trivial. `Server` iirc. See failed dependeabot PR: https://github.com/johanhelsing/matchbox/pull/383
Cross-play appears to be broken in this very specific case. To reproduce: 1. Start signaling: `cargo run -p matchbox_server` 2. Run native client: `cargo run -p bevy_ggrs_example` 3. Run Firefox...
I want this because I want to tell my players why their latency is bad. It looks hairy, but doable. Not sure what the API will be.
It would be nice if we built and published the bevy_ggrs example when merging to main and/or tagging. Could perhaps use github pages for hosting. To actually build and bundle...
We are waiting for ice gathering completion before we start ice trickling. In theory, this should not be needed, and it's probably slowing down connection times on wasm, especially if...
Currently we stop anything related to ice once the data channel has opened, however It's possible to return to the ice gathering state, and we should probably handle that. Ref...
It's a bit confusing to have an instance property getter clear static state. Change the name and signature to better reflect what it does. Also changes some of the methods...