AI Director — quests, dailies & events
Multi-option quests, barter, main-character gating, token economy, server-flavored events. Alpha polish: clearer dailies, reliable event cadence, better quest quality, smoother rewards.
Home · Whitepaper
PUBLIC ROADMAP · ALPHA → BETA · EPISODES
GrAiRiO Whitepaper
Plans, pillars, episode unlock timeline, and polish targets for Alpha and Beta.
Last updated: 2026-07-10 · Fully AI-operated Pre-Renewal · Episode 1 · English Alpha
Vision
GrAiRiO is classic Pre-Renewal where an AI Director runs quests, dailies, events, and support — with personality, not scripts alone. Players bring a clean full kRO; GrAiRiO provides the package, patch host, website, and AI systems.
Content unlocks episode by episode so the world grows with the community — then past the official Pre-RE line, into custom episodic eras shaped by player feedback, maps, and AI-assisted systems. Long-term: Director loops and companion play stable enough for open Beta, sustainable enough to keep shipping content.
Episode unlock roadmap
A core server feature: gradual episodic unlocks. Right now the world is locked to Episode 1 (Alpha). After the live release cadence settles, each next episode opens on a schedule — bigger drops get more build time. The AI Director only knows what is unlocked (no spoilers).
How unlocks work
- ▸ Maps, dungeons, towns, and related content gate behind the current episode.
- ▸ Episode Manager + AI tools stay aligned with what is open.
- ▸ Dates are targets, not promises — quality and stability can stretch a window.
- ▸ Announcements land on Discord + the site when an episode actually flips live.
Official Pre-Renewal line (target cadence)
Baseline from the original project plan, refined for bigger late-game work. Early episodes move faster so the world feels alive; later ones need more time.
| Band | Target spacing | Notes |
|---|---|---|
| Episodes 1 → 6 | 1–2 weeks each | Faster early unlocks (e.g. Ep1 for 1–2 weeks, then Ep2, then Ep3…) |
| Episodes 7 → 10 | ~3 weeks each | More content weight; more polish before open |
| Episodes 11 → ~13.2 | ~4 weeks each | Largest official Pre-RE slices; longer build & test windows |
We’ll follow the classic Pre-Renewal content line as far as it stays fun and maintainable, then move into custom eras. Target ceiling for the classic line is around Episode 13.2; if a slice is too incomplete or unstable, it may be skipped, merged, or delayed.
Custom episodic era (after ~13.2)
Community-shaped
Maps · AI systems · feedback
Once the official Pre-RE line is exhausted (or no longer practical), GrAiRiO shifts to custom episodes — new or existing custom maps, new systems, and themes the community actually wants to play.
- ▸ Cadence target: about 4–6 weeks per custom drop (roughly one month to a month and a half).
- ▸ Spacing flexes with how much can ship cleanly, how players feel about AI-generated systems / art, and overall sustainability.
- ▸ Direction comes from player feedback, vision threads, and what the AI Director can support honestly.
- ▸ Map bank + new design work both in play — quantity never beats “fun and stable.”
Custom episodes are a long-term feature of the server, not a one-off event. If a cycle needs longer (or a shorter experimental drop), the AI systems will say so publicly.
Now
Episode 1 live in Alpha. Later maps stay gated.
Post-release
Start rolling Ep2+ on the early 1–2 week band once ready.
Horizon
~13.2 official line → custom episodic releases with the community.
Development stages
Now
Alpha testing
Live stack, rebalances expected. Polish Director systems and install reliability.
- Game + web + Discord online
- Director events / dailies / quests
- Client package simplification
Target
Beta testing
Wider testing when core loops and Companions meet a release bar.
- Director loop solid for daily play
- AI Companions release-ready
- Trusted patch pipeline
Actively polishing (Alpha)
Client package & patch host
A clear first install, small later updates, and docs that match what players actually get.
Stability & auto-heal
Monitored game, web, patch API, edge proxy, and database with auto-recovery and maintenance mode for deploys.
AI Companions — Beta readiness
Needs deep work
Target: Beta release-ready
Companions are a signature feature and are not in a good place yet. Deferred until Director polish and install stability improve, then rebuilt toward a Beta bar: summon, behave, dismiss, tokens — without constant breakage.
Expect experimental or offline companion features during parts of Alpha.
What “Beta ready” means
- ▸ Director dailies / quests / events are the default fun loop.
- ▸ Companions meet a release bar for wider testing.
- ▸ Install and patches match documentation.
- ▸ Economy survives longer sessions without constant emergency rebalances.
- ▸ Episode unlock pipeline is trusted (announce → gate → AI knows the new world).
Alpha expectations
Wipes, rebalances, and feature flags may change with little notice.
Director content is tightening; Companions are not the current focus.
Episode timing above is guidance — Alpha may stay on Episode 1 longer while install and Director polish settle.
Report issues and episode wishes in Discord so systems can improve from patterns.
Follow development
Announcements and Alpha feedback on Discord.