dirtrallybot

dirtrallybot

A Discord bot that generates random rally challenges — a stage, weather and car — for DiRT Rally 2.0 and EA Sports WRC, and tracks the times people set against each challenge.

Originally handwritten, now slopwritten.

Commands

• /newstage-dr2 — open the challenge builder for DiRT Rally 2.0
• /newstage-wrc — open the challenge builder for WRC

The builder lets you pin any of location, distance, stage, weather, drivetrain, class or car, or leave each on "random". Submitting posts the challenge to the channel with buttons to enter a time (⏱️) and to list everyone's times (📋).

Challenge viewer

While the bot runs it also serves a read-only web page at WEBADDR (default http://localhost:8080) listing every stored challenge — date, track, distance, weather and car. The date comes from the challenge's Discord message ID, which is a snowflake. Set WEBADDR=off to disable it.

Each challenge has a collapsible panel of its completions, sortable by lap time or submission date. Sorting is driven by htmx, vendored at internal/bot/web/static/htmx.min.js and served by the bot — no external requests. Completions recorded before the bot stored submitter names and submission times show a dash in those columns.

A /feedback page shows the running 👍 / 👎 tally that biases generation, grouped by item type (location, stage, distance, weather, class, car, drivetrain) and ordered by net score within each group. Only items that have been voted on appear.

Configuration

Configuration is read from a .env file in the working directory (the process environment takes precedence). A missing .env is a fatal error. Copy default.env to .env and fill it in:

cp default.env .env

Challenges are stored in the bbolt file named by DBPATH.

biased leans generation towards stages, cars and weather that have had good 👍 / 👎 feedback; random picks uniformly; deterministic replays a fixed sequence (for debugging).

Running

make run      # go run ./cmd/dirtrallybot
make build    # go build ./...
make test     # go test ./...
make generate # regenerate the templ views after editing a .templ file

make generate needs the templ CLI: go install github.com/a-h/templ/cmd/templ@latest. The generated *_templ.go files are committed, so this is only needed after editing a .templ file.

Docker

The Dockerfile builds a static binary on a distroless base (~12 MB, non-root). The image ships an empty .env, so every value is supplied through the environment instead — the keys are the same as default.env. DBPATH is set to /data/rallybot.db, so mount a volume at /data to keep challenges across restarts.

With docker-compose.yml — put the real values in a local .env first, then:

docker compose up -d --build

It reads .env, forces WEBADDR=:8080, publishes the viewer on http://localhost:8080 and persists the database in the rallybot-data volume.

Without Compose:

docker build -t dirtrallybot .
docker run -d --name dirtrallybot --restart unless-stopped \
  --env-file .env -e WEBADDR=:8080 \
  -p 8080:8080 -v rallybot-data:/data dirtrallybot

bbolt takes an exclusive lock on the database file: run only one container against a given volume, and prefer a local named volume over a bind mount to a networked filesystem (NFS and the like break bbolt's file locking).

Layout

• cmd/dirtrallybot — entry point
• internal/bot — Discord session wiring and interaction routing
• internal/bot/handler — the slash command, component and modal handlers
• internal/bot/render — turns domain values into Discord message content
• internal/bot/web — the local challenge viewer (templ views)
• internal/model — the domain: games, locations, stages, classes, cars, …
• internal/randomiser — challenge generation (deterministic, seeded)
• internal/store — persistence (port interface, boltstore, memorystore)

See docs/ for the data model and outstanding work.