rictic/airlock.chat

An exercise in learning wasm and rust and game development by cloning the game among us

airlock.chat's Issues

Blender model WIP

rust-us.zip

Chat!

A basic chat interface, with the ability to send, receive, and display messages.

Lots of options for how. Could implement this part in JS and call into with the Rust for communication

Add a super basic server

To keep things simple for now, we'll start with a centralized server that rebroadcasts messages. This emulates a peer to peer system like WebRTC but without the complexity of getting a WebRTC connection established.

From here we could go full centralized, where the server maintains a sim of the game and can e.g. reject cheating, or we can go the fully peer to peer route

When one client disconnects, the server sometimes disconnects other clients too?

Good first bug for someone who wants to learn about async in Rust!

I have basically no idea how the current server works, it's mostly just adapted from https://github.com/snapview/tokio-tungstenite/blob/master/examples/server.rs

Changing the name

Would you consider a name-change? Rust Us is fine, but it's not very searchable and the relation to Among Us is not clear until actually reading the description. I thought maybe the us in rust-us stood for US(A) when I first found it.

Some suggestions:

• Among Crabs 🦀
• Among Rustaceans
• Among Rust

Add killing

Add the ability for a player to kill another.

Add a new button input Q to kill. The simplest initial thing would be to then find the closest other player, and if within a certain distance of that player, that player is deleted.

(lots of stuff to add on top of this eventually of course, bodies, ghosts, only imps can kill, etc)

Feature request: community contributed maps

Allow the community to create their own maps.

Place client crate at the same level as server crate in the repo structure

What do people think about that change?

Add kill cooldowns

A player shouldn't be allowed to kill more often than once every K ms