https://github.com/bradeneverson/spjorts

Server Architecture for hosting WASM-built games over the web, supporting communication through physical controller hardware
https://github.com/bradeneverson/spjorts

bevy hardware htmx wasm wii-sports

Last synced: 5 days ago
JSON representation

Server Architecture for hosting WASM-built games over the web, supporting communication through physical controller hardware

• Host: GitHub
• URL: https://github.com/bradeneverson/spjorts
• Owner: BradenEverson
• Created: 2024-12-20T00:25:00.000Z (19 days ago)
• Default Branch: main
• Last Pushed: 2025-01-02T00:54:50.000Z (6 days ago)
• Last Synced: 2025-01-02T01:26:15.075Z (6 days ago)
• Topics: bevy, hardware, htmx, wasm, wii-sports
• Language: Rust
• Homepage:
• Size: 9.58 MB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Spjörts 🏂🎾⛳

![rust](https://img.shields.io/badge/Rust-000000?style=for-the-badge&logo=rust&logoColor=white) 

![bevy](https://img.shields.io/badge/Bevy-232326?style=for-the-badge&logo=bevy&logoColor=white) 

![htmx](https://img.shields.io/badge/%3C/%3E%20htmx-3D72D7?style=for-the-badge&logo=mysl&logoColor=white) 

![wasm](https://img.shields.io/badge/WebAssembly-654FF0?style=for-the-badge&logo=WebAssembly&logoColor=white) 

## Server Architecture for hosting WASM-built games over the web, supporting communication through physical controller hardware 💃

This project exists because I really wanted to make [Wii Sports](https://en.wikipedia.org/wiki/Wii_Sports), while also learning more about the Bevy game engine, WASM and optimized embedded systems that need to continuously stream timely data. 

Using the Deku binary format, optimized websocket streams are able to communicate button presses and gyroscope angle readings over from a Raspberry Pi controller to the server itself, which then streams from another websocket to all frontend "listener" streams, which finally are then fed into the WASM games via a standardized `Sender` struct that comes along when a game is initialized.

Long story short there's a large chain of communication that essentially goes from 

`[ Controller ] -> [ Web Server ] -> [ Js Frontend ] -> [ WASM Game ]`

# Implemented Games

- [x] THE CUBE 🧊

  * "Game" meant for early debugging purposes.

  * Controls a cube floating in the void, pitch roll and yaw updates determine the cube's rotation and pressing the two controller buttons moves it along the X axis in different directions.

    ![cube world gaming](https://github.com/user-attachments/assets/86f86865-55c0-4a04-b40d-34314352b6b0)

- [ ] Bowling 🎳

  * Implementation of a standard bowling game, currently supports moving along the x axis for aiming.

  * "Throwing" the ball via aiming with the physical controller's angle data and hitting the A button for release propels the ball forward at that angle with velocity according to the rate at which the ball is thrown

  * Rapier3d is used for all physics simulation, which allows for (somewhat) accurate bowling!

  - [ ] **Still in progress**: Implementing proper score handling and external game state info, basically everything that isn't aiming and throwing a ball 

   

    ![bowling](https://github.com/user-attachments/assets/9c7f337f-12df-41a8-a688-176bfd200f43)