← Back to Docs

// Guide

AI Story (RPG)

AI-driven Star Citizen text-RPG adventures that run in private Discord threads, with a persistent character and mobiGlas status readout.

TierElite
You'll needElite subscription; an adventure channel set with /config-ai.

AI Story turns your Discord into a Star Citizen tabletop. A member runs /aistory start, the bot spins up a private thread just for them, and an AI game master narrates a persistent adventure in the 'verse — the member types what their character does, and the story responds. Each player gets a saved profile (callsign, ship, credits, location) that carries across sessions and shows up as a mobiGlas readout on every narration.

Elite feature

AI Story requires an Elite subscription. On Free and Pro servers, /aistory start replies with an upgrade prompt instead of starting an adventure. See Tiers for what's included in each plan.

Setup (admin)

  1. 1
    Pick a home channel for adventures. Choose (or create) a text channel where story threads should be created — something like #adventures. Threads are private, so the channel itself stays clean; it just hosts them.
  2. 2
    Point the bot at it. Run /config-ai channel:admin and select the channel. Every new /aistory start will create its thread there. (If no channel is configured, the thread is created wherever the member ran the command — set one so stories don't sprout all over the server.)
  3. 3
    Or use the dashboard. Open your guild dashboard's Features tab, find the AI Story card, click Configure, set Adventure Channel, and click Save Changes.
Features tab — AI Story
FeaturesPermissionsServer StatsAnalyticsEventsTokens
AI Story
AI-driven Star Citizen RPG adventures in threads
Configure
Configure AI Story
#adventures

New story threads are created in this channel.

CancelSave Changes
CancelSave Changes
The AI Story card's Configure modal on the dashboard.

Starting an adventure (members)

/aistory start

What happens next depends on whether you've played before:

  • First time — a character-setup modal asks for your name/callsign and starter ship. That becomes your persistent RPG profile.
  • Returning player — the bot skips straight to creating your thread and greets you by callsign.

Either way, the bot creates a private thread named 📜-story-<your username>, adds you to it, and posts a welcome embed with adventure category buttons:

  • ⚔️ Combat & Mercenary
  • 📦 Cargo & Smuggling
  • ⛏️ Industrial & Salvage
  • ⚕️ Medical & Rescue
  • 🎭 Social & Exploration
  • 🏴‍☠️ Crime & Piracy
  • …or write your own opening scenario.

Playing

There are no commands during play. Just type what your character does in the thread — "I hail the Cutlass and demand they cut engines", "I dock at Grim HEX and look for a fence" — and the AI game master narrates the outcome, keeping the last several turns as context. Every narration opens with your mobiGlas status block: citizen ID, current location, ship, and credits.

SB
StarBotApp
📜 The Yela Belt
The asteroid tumbles past your canopy as Viper's Buccaneer breaks hard to starboard, kicking a plume of ice crystals across your sensors. Your quantum interdiction snare holds — he's not jumping anywhere. A comm request blinks on your mobiGlas: he wants to talk. What do you do?
Citizen ID
Vex_Marlowe
Location
Yela Belt, Crusader
Ship
Avenger Titan
Credits
14,250 UEC
AI Story · reply in this thread to act
A turn inside a story thread: the player typed an action, and StarBot narrates the result with the mobiGlas readout.
Threads are per-player

Each /aistory start creates a fresh private thread for that member. Your profile (callsign, ship, credits, location) persists between adventures, so you can end a session and pick up your character later.

Troubleshooting

/aistory start shows an upgrade embed — the server isn't on Elite. AI Story is tier-gated at runtime; check /check-sub or the Tiers page.

Threads appear in the wrong channel — no adventure channel is configured, so the bot falls back to the channel the command was run in. Set one with /config-ai channel: or the AI Story card.

The bot stops responding mid-story — the same Elite check runs on every turn, so a lapsed subscription pauses adventures until it's renewed.

Related