Commit Graph

10 Commits

Author SHA1 Message Date
129e9ccc5e Spawn the gameplay elements
Now to start wiring them in for basic operation, then to pipe it all
through the WebSocket.
2025-10-21 08:37:18 -05:00
8b290fdd0d Implement menu despawner 2025-10-20 08:07:58 -05:00
845765513d Sort derive macro items
For consistency, or something.
2025-10-19 09:58:34 -05:00
857aefda03 Wire the 'Start' button to a state changer 2025-10-19 09:57:57 -05:00
7f651481f6 Quiet some lints, remove some dev logging 2025-10-19 09:57:36 -05:00
9b71fff4eb Begin work on a main menu & UI systems 2025-10-18 15:04:54 -05:00
09e05c9f8e autofmt 2025-10-18 11:00:04 -05:00
7128377924 Dummy client to learn the other half of WebSockets
This is mostly a copy of ambiso/bevy_websocket_example:
https://github.com/ambiso/bevy_websocket_example/tree/main

It demonstrates how to hold and use a (Tungstenite) WebSocket in a Bevy
app. I've altered it slightly (and skipped impl'ing the send function)
to fit my own chatroom dummy target.

This is completely useless as a chatroom app, but it's not supposed to
be one. Now I can move on to building the actual Pong game!
2025-10-18 10:57:22 -05:00
0ebc137369 Dummy server to support proof-of-concept client
I'm planning to use WebSockets for game networking because it can be
used both on native and web environments.

I need some time and tools to figure out how to make Bevy hold and use a
WebSocket. I've taken the Axum WS text chat for use as a dummy activity
so I can build out a Bevy app which implements the text chat behavior.
2025-10-17 09:13:29 -05:00
88e6a8db5d Begin project, basic README & placeholder crates 2025-10-16 12:32:29 -05:00