choose_your_own_adventure

cyber elysium, disco punk

Discord Bot Setup

To run the Discord bot, follow these steps to create and configure your own bot in Discord:

1. Go to the Discord Developer Portal
2. Click "New Application" and give it a name
3. Go to the "Bot" section and click "Add Bot"
4. Scroll to privileged gateway intents
   • Enable all 3 toggles: Presence, Server Members, Message Content
5. Reset token and copy it
6. In Developer Portal, go to OAuth2 > URL Generator
   • Select "bot" under scopes
   • Select needed permissions:
     • Send Messages
     • Send Messages in Threads
     • Read Message History
7. Discord admin can use the generated URL to invite the bot to your server
8. Confirm by going to server settings > Apps/Integrations > Bots & Apps

Once you have your bot token, add it to a .env file in your project root as:

DISCORD_BOT_TOKEN=your_token_here

(Optional) Find Your Discord Channel IDs

You may want to configure the bot to use different channels for gameplay and debugging. To do so, you need each channel's unique ID:

1. In Discord, go to User Settings > Advanced and enable "Developer Mode".
2. Right-click on the channel you want to use.
3. Click "Copy Channel ID".
4. Add them to your .env file as:

DISCORD_CHANNEL_ID=your_gameplay_channel_id
DISCORD_DEBUG_CHANNEL_ID=your_debug_channel_id

• DISCORD_CHANNEL_ID is for the main gameplay channel.
• DISCORD_DEBUG_CHANNEL_ID is for a dedicated debug/logging channel.

You can now use these variables in your code to specify where the bot should listen, send messages, or log debug output.

Continue with installation and running the bot as described below.

Watch Luigi win by doing nothing

cd backend
npm install
npm run play -- --mario-party-luigi

Play (CLI)

cd backend
npm install
npm run play

Full Stack Web UI (Development)

Note: Running both servers from the project root with a single command is not supported at this time. Please use the manual method below.

Manual (in separate terminals)

Backend:

cd backend
npm install
npm start

Frontend:

cd frontend
npm install
npm run dev

• Visit http://localhost:5173 in your browser to play.

API Health Checks

Test backend endpoints directly:

curl -i -X POST http://localhost:3000/api/dialog -H "Content-Type: application/json" -d '{"playerId":"player1","sceneId":"scene_intro"}'

Running Tests

Backend

cd backend
npm install
npm test

---

Backend LLM Setup

Option 1: Ollama (Local)

Ollama lets you run language models locally on your machine.

1. Install Ollama:
   Follow the instructions at ollama.com/download for your platform.

2. Run Ollama:
   Start Ollama by running:

   ollama serve

   or, to run the recommended/tested model for this project (gemma3:12b):

   ollama run gemma3:12b

   Note: This project has been tested with gemma3:12b and it is the recommended model.

3. The backend will connect to Ollama automatically if it’s running.

Option 2: OpenRouter (Cloud)

OpenRouter lets you access a variety of LLMs through a cloud API.

1. Sign up and get your API key:
   Go to openrouter.ai and sign up.
   After signing in, visit your API Keys page to create a key.

2. Set your API key as an environment variable:
   In your terminal, run:

   export OPENROUTER_API_KEY=sk-...yourkey...

   Or add this line to your .bashrc, .zshrc, or equivalent shell profile.

3. The backend will use OpenRouter if the API key is set.

Fallback: Lean Vault

If neither Ollama nor OpenRouter is configured, the backend will attempt to use Lean Vault.
Most users will not have Lean Vault installed, so it’s recommended to use one of the above options.