https://github.com/sjml/wasmbots
wasm. bots. 🤖🧙♂️🧚🧙♀️⚔️🏰🤖
https://github.com/sjml/wasmbots
assemblyscript c golang roguelike rust svelte typescript webassembly zig
Last synced: about 1 month ago
JSON representation
wasm. bots. 🤖🧙♂️🧚🧙♀️⚔️🏰🤖
- Host: GitHub
- URL: https://github.com/sjml/wasmbots
- Owner: sjml
- License: mit
- Created: 2024-10-03T03:33:20.000Z (7 months ago)
- Default Branch: main
- Last Pushed: 2025-02-06T16:49:05.000Z (3 months ago)
- Last Synced: 2025-03-28T23:03:53.518Z (about 1 month ago)
- Topics: assemblyscript, c, golang, roguelike, rust, svelte, typescript, webassembly, zig
- Language: TypeScript
- Homepage: https://shaneliesegang.com/projects/wasmbots
- Size: 7.34 MB
- Stars: 164
- Watchers: 5
- Forks: 12
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# WasmBots
(NB: this repo is active, but progress may be a little slow. [see this video for more specifics.](https://www.youtube.com/watch?v=rcWSoCT37MQ))
[A multi-wizard arena where all the competitors are bots!](https://shaneliesegang.com/projects/wasmbots/) (Always a latest build at [GitHub Pages](https://sjml.github.io/wasmbots/), but that site is the canonical deployment.)
[The programming interface is described here](./docs/interface.md), and there are [pre-made libraries in a bunch of languages](./libraries/) to get you started. You can also peruse [the code for the example bots](./example_bots_src/).
The [documentation can also be useful](./docs/), or maybe just [the development history](./docs/history.md).,
## Development
It's a big ole monorepo. Sorry about that; it's what happens when a proof-of-concept just grows organically. I presumptively registered a [wasmbots org on GitHub](https://github.com/wasmbots) just in case this becomes A Thing™ in which case I'll split things out more productively.
### Devbox
You can always build and run with [devbox](https://www.jetify.com/devbox). ([Installation instructions are here.](https://www.jetify.com/docs/devbox/installing_devbox/))
Run `devbox shell` to be in a usable environment where you can run
### Docker
The [Dockerfile](./Dockerfile) just pipes everything through devbox, but makes it a little more turnkey, especially if you're already a Docker user.
```sh
# produces a container with a built frontend,
# including example bots, served with Caddy
docker build -t wasmbots .
# to actually get it serving:
docker run -d -p 8080:80 wasmbots
# Then look for it in your favorite browser at:
# `http://localhost:8080`
# (change out the port number to whatever you want)
```
```sh
# this will drop you into a shell within the container
# where all the tools are installed and paths are set
# and everything.
docker build --target dev -t wasmbots-dev .
docker run -it -v $PWD:/code wasmbots-dev
```
### Manual Installation
If you don't want to install a whole other package manager, here's what I (used to) use to get up and running with [Homebrew](https://brew.sh/) on macOS. Modify appropriately if you're using something else.
```sh
brew install deno node wabt emscripten rust zig go tinygo-org/tools/tinygo
```
### Simple Checks
Regardless of how you get your dev environment running, you can verify everything is working as expected by running:
```
./scripts/_build_wasms.sh
./scripts/_validate_wasms.sh
```
That will build and validate all the example bots; it doesn't check their functionality at all, just that WebAssembly modules were produced that conform to [the expected interface](./engine/src/data/guestAPI.json).