From 6669e198567891ab9d3acadd6dd9880fed9f7f27 Mon Sep 17 00:00:00 2001 From: Johan Klokkhammer Helsing Date: Fri, 31 Mar 2023 09:14:50 +0200 Subject: [PATCH] docs: Update for bevy_matchbox --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 750e1baf..92fb4ae2 100644 --- a/README.md +++ b/README.md @@ -48,8 +48,8 @@ All of this, however, is hidden from rust application code. All you will need to - Create a new socket, and give it a signaling server url - `.await` the message loop future that processes new messages. - - If you are using Bevy, it can be spawned as a Bevy io task (see the [`bevy_ggrs`](examples/bevy_ggrs/) example). - - If you are using WASM, `wasm-bindgen-futures` can help (see the [`simple`](examples/simple/)). + - If you are using [Bevy](https://bevyengine.org), this is done automatically by `bevy_matchbox` (see the [`bevy_ggrs`](examples/bevy_ggrs/) example). + - Otherwise, if you are using WASM, `wasm-bindgen-futures` can help (see the [`simple`](examples/simple/)). - Alternatively, the future can be polled manually, i.e. once per frame. You can hook into the lifecycle of your socket through the socket's API, such as connection state changes. Similarly, you can send packets to peers using the socket through a simple, non-blocking method.