Server and hosting
"People die, but paperwork is forever."
— Clerk Second Class Umi Dray
Running a StoryForce server means running a Jedi Academy dedicated server with the StoryForce game module. Alongside it sit a SQLite database and a config file that does a lot of work.
Getting it running
- Installing a dedicated server: bare metal, Windows and Linux
- Docker hosting: running on a NAS or VPS
- What ships in each download: client zip, server zip and the pk3
Configuring it
- Server configuration: the settings that matter and why the config file is not optional
- Identity labels: naming the statuses, factions and ranks your setting uses
- LLM NPC setup: enabling AI NPCs, and what they cost
Running it
- Admin ranks and membership: who can do what
- Permission bits: the mask system, with a calculator
- Director locks: locking tools to whoever is running the scene
- Managing accounts: creating, promoting, retiring and disabling
- Managing community characters: building and pruning the shared pool
- Kick and ban: removing someone, temporarily or permanently
- The audit trail: what staff did, and when
Keeping it
- The database: where it lives and what is in it
- Backups and D1 sync: local snapshots and the Cloudflare mirror
Start your server with
+exec storyforce_server.cfg. Without it 7 admin commands, including kick and ban, are unavailable, and the narrower permissions get written into your server's saved settings permanently. See server configuration.