ruBots v0.1.1 — control centre and bots

Unzip and run — nothing to install.

file	what it is
rubots-control.exe	the control centre: dashboard, radar, fleet, deploy, server, console, settings
rubots-bot.exe	one bot. The control centre launches copies of it; you can also run it directly

HOW-TO-RUN.md is in the zip and covers the rest.

What you need besides these two files

The bots connect over UDP as ordinary clients, so there has to be a server, and it must accept emulator tickets — Reunion with cid_RevEmu = 1. The repository ships a ready-made one:

cd testserver
docker compose up -d

Point the app at a cstrike folder (SETTINGS, key 7) so the radar can read the map's .bsp. Without it everything still runs — the radar just says "no map loaded".

What is in it

• Radar on the map's own nav lattice, with a replay scrubber over the last two minutes, layer toggles, and the sight lines a selected bot is watching (Tab cycles bots).
• Deploy that launches bots staggered on purpose — a mass connect from one IP trips ReAuthCheck and gets the address banned for an hour.
• Server view with the game's own A2S query, so you can see whether the server accepted your bots rather than guessing.
• Console with every bot's output in one filtered stream.

Changed from v0.1.0

Demo recording and the replay view are removed. If you downloaded v0.1.0, take this one instead.

Known limits

• Windows x64 only for now.
• The bots' navigation is a work in progress and the write-ups in docs/ say where: vertical-navigation.md and looking-around.md carry the measurements behind the recent fixes, including what is still open.

🤖 Generated with Claude Code

What's Changed

• Revert the demo recording and replay feature by @DemOnJR in #9

Full Changelog: v0.1.0...v0.1.1

ruBots v0.1.0 — control centre, bots, demos

Superseded by v0.1.1 — take that one.

This build shipped a demo-recording feature that was removed straight after. Everything else in it is the same.

V1

v1

docs: add installation tutorial, server setup, and workspace updates