Installation

Release binaries

Download the archive for your platform from the releases page, unpack it, and put rune somewhere on your PATH:

tar xzf rune_*_linux_amd64.tar.gz
sudo mv rune /usr/local/bin/
rune -version

Builds cover Linux, macOS, and Windows (amd64 and arm64). Windows archives are zips containing rune.exe.

With Go

go install github.com/mmcdole/rune/cmd/rune@latest

From source

git clone https://github.com/mmcdole/rune
cd rune
go build ./cmd/rune/

Where things live

Config & scripts	~/.config/rune/ (%APPDATA%\rune on Windows)
Your main script	~/.config/rune/init.lua, auto-loaded at startup
Bookmarks & durable state	~/.config/rune/store.json
Session logs	~/.config/rune/logs/

Nothing is created until it’s needed; a fresh install is just the binary.

Use a different config directory

Pass --config-dir to keep everything Rune reads and writes in a different directory:

rune --config-dir ~/muds/tank aardwolf

Rune reads init.lua, store.json, world data, and logs from that directory. RUNE_CONFIG_DIR provides the same override for shell profiles and launchers:

RUNE_CONFIG_DIR=~/muds/tank rune aardwolf

When both are set, --config-dir wins.

Next

Your First Session covers connecting, bookmarks, and the basics of moving around.