cards for humanity
Find a file
2024-10-09 01:53:23 -04:00
client less specific versioning 2024-10-09 01:52:33 -04:00
data tragic 2024-08-29 21:38:39 -04:00
lib change everything -- use thaw ui 2024-09-09 19:46:56 -04:00
server less specific versioning 2024-10-09 01:53:23 -04:00
tools/socket_blaster add basic stress testing tool 2024-10-08 21:33:21 -04:00
.gitignore gotta go fast 2024-08-28 22:55:16 -04:00
build automate deployment 2024-10-07 20:14:41 -04:00
CAH_PrintPlay2021-GameRules.pdf add rules 2024-04-07 01:01:55 -04:00
Cargo.lock add basic stress testing tool 2024-10-08 21:33:21 -04:00
Cargo.toml add basic stress testing tool 2024-10-08 21:33:21 -04:00
LICENSE license 2024-04-07 00:50:05 -04:00
readme.md update readme 2024-10-08 21:59:48 -04:00
tailwind.config.js use workspaces 2024-07-20 23:00:19 -04:00
test add basic stress testing tool 2024-10-08 21:33:21 -04:00
Trunk.toml jsoooonn 2024-07-21 22:48:15 -04:00

Cards For Humanity

Live at https://cards.doordesk.net

A game master server for the popular game Cards Against Humanity using data from Chris Hallberg's project JSON Against Humanity (everyone say "Thanks, Chris!")

This started as a problem trying to play games with friends who are all on different platforms. This shall be as cross-platform as it gets. I want it to work on anything that can establish a connection and allow anyone to write any front-end they can dream up whether it be a web page, chat bot, VR, etc. Any clients who share a master server can play together across any platform.

Test/Dev:

Server

With auto-reload:

Then:

./test

Without auto-reload:

cargo run -p server

Client

Then:

trunk serve --open

Build:

Client

trunk build --release

Server

cargo build --release

  • The server automatically serves the built client from /dist at 127.0.0.1:3030. When building for release the client automatically points to doordesk.

  • Configure any custom clients to connect to ws://127.0.0.1:3030/websocket for local testing or wss://cards.doordesk.net/websocket to use my server.

Tools:

There is a tool named socket_blaster used for stress testing the server.

Run

cargo run -p socket_blaster -- -h

to see available options.

Then

cargo run -p socket_blaster -- [COMMAND]

to run a command.

TODO:

  • prevent zombie users after browser crash
  • figure out proper auth - client's problem?
  • use db
  • test bincode and probably move away from json
  • make typescript sdk
  • support card text editing
  • prevent import of cards that have been seen already and edited
  • handle duplicates
  • efficiency
  • make demo clients for multiple platforms and screens