aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorHenauxg <19689618+Henauxg@users.noreply.github.com>2023-01-20 13:23:40 +0100
committerHenauxg <19689618+Henauxg@users.noreply.github.com>2023-01-20 13:23:40 +0100
commitff2809001a09eb56e53a1235d1d403b58a8dea4c (patch)
tree3ba2397a039a052128c0da07caf4305a5f6a38ef /README.md
parentef3e2df0e2850cd2b5de976bd2f9382c258a4e1e (diff)
[example:breakout] Make use of Unreliable and UnorderedReliable channels
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/README.md b/README.md
index 962f33a..b47218c 100644
--- a/README.md
+++ b/README.md
@@ -300,6 +300,8 @@ This demo is a modification of the classic [Bevy breakout](https://bevyengine.or
It hosts a local server from inside a client, instead of a dedicated headless server as in the chat demo. You can find a [server module](examples/breakout/server.rs), a [client module](examples/breakout/client.rs), a shared [protocol](examples/breakout/protocol.rs) and the [bevy app schedule](examples/breakout/breakout.rs).
+It also makes uses of [`Channels`](#channels). The server broadcasts the paddle position every tick via the `PaddleMoved` message on an `Unreliable` channel, the `BrickDestroyed` and `BallCollided` events are emitted on an `UnorderedReliable` channel, while the game setup and start are using the default `OrdrerdReliable` channel.
+
Start two clients with `cargo run --example breakout`, "Host" on one and "Join" on the other.
![breakout_versus_demo_short](https://user-images.githubusercontent.com/19689618/199804335-17df365c-32aa-49b1-94f1-11b8c7162ae3.gif)