Everything you need to get started with RoleVerse and begin your AI-powered tabletop RPG sessions.
- What You Need
- 1. Sign In to RoleVerse
- 2. Set Up Fantasy Grounds (Virtual Tabletop)
- Using RoleVerse
- Supported Game Systems
- Troubleshooting
RoleVerse is a web app — there's nothing to install for the core experience. Fantasy Grounds integration requires the FG desktop app and a one-time sync setup.
| What | Why | Required? |
|---|---|---|
| A Google account | To sign in to RoleVerse | Yes |
| A modern web browser | Chrome, Firefox, Edge, or Safari | Yes |
| Fantasy Grounds Unity | Virtual tabletop integration (characters, combat, maps) | Optional |
- Open the RoleVerse web app in your browser.
- Click Sign in with Google.
- Choose your Google account and authorize access.
- You'll be taken to your Dashboard — that's it, you're in!
Tip: RoleVerse uses your Google account for sign-in. No separate password to remember.
Fantasy Grounds Unity is a virtual tabletop application. When connected to RoleVerse, your characters, combat state, dice rolls, and battle maps sync automatically to the web app.
- Go to fantasygrounds.com.
- Purchase and download Fantasy Grounds Unity.
- Install and launch it.
The Fantasy Grounds desktop sync is complete. A step-by-step setup guide for the desktop sync agent is coming soon.
- From your Dashboard, click New Campaign.
- Enter a campaign name (e.g., "The Lost Mines of Phandelver").
- Optionally add a description.
- Select a game system from the dropdown (see Supported Game Systems below).
- Click Create Campaign.
After creating a campaign, you'll see its overview page with:
- Campaign name, description, and game system details.
- Quick-action cards for starting sessions and viewing characters.
- NPC Roster — a persistent list of named NPCs in your campaign, with disposition and known facts.
From a campaign's overview page, click Start Session to enter the session view:
- Left sidebar — Session notes, party status, and Fantasy Grounds connection status.
- Center — Chat window for AI game narrative and scene display.
- Right — Character sheet panel (changes based on your game system).
Type a message or player action in the chat window and the AI will respond as your Dungeon Master. Five specialized AI agents handle different request types automatically:
| Agent | Handles |
|---|---|
| Narrator | Player actions, scene descriptions, exploration |
| Rules Arbiter | Rules questions and mechanical lookups |
| Lore Keeper | Recall of campaign facts, past sessions, NPC history |
| NPC Dialogue | Speaking to and voicing named NPCs |
| Encounter Builder | Designing and generating combat encounters |
You don't need to choose which agent to use — the router selects the right one based on your message.
When you create a campaign, choose from the following. AI rules support varies by system.
| System | Rules AI |
|---|---|
| D&D 5E (2014) | Full SRD — ~2,335 rules chunks ingested via Open5e |
| System | Rules AI |
|---|---|
| AD&D 2nd Edition | OSRIC-based stub + Claude training knowledge |
| Pathfinder 2E | Claude training knowledge (full data ingestion planned) |
These systems appear in the game system selector and work with the AI agents, but have no RAG-backed rules content beyond Claude's training knowledge:
- AD&D 1st Edition
- D&D 3.5 Edition
- D&D 4th Edition
- D&D 5E (2024)
- Pathfinder 1E
- Dungeon Crawl Classics
- The One Ring 1E & 2E
- Cyberpunk 2020
- Make sure you're using a supported browser (Chrome, Firefox, Edge, or Safari).
- Check that pop-ups are not blocked — the Google sign-in window may be prevented from opening.
- Try clearing your browser cache or using a private/incognito window.
- Try signing in again. Your session may have expired.
- If the issue persists, clear your browser cookies for the RoleVerse site and try again.
- Access may be restricted to specific accounts. Contact the RoleVerse administrator to have your Google email added to the allowed list.
- Make sure your browser is up to date.
- Try a hard refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS).
- If the problem continues, open an issue on GitHub.