🚀 Quick Start
Get the bot running from scratch in about 5 minutes.
Prerequisites
- Node.js 18+ (
node --versionto check) - A Fluxer bot application with a token
- Developer Mode enabled in Fluxer (Settings → Advanced → Developer Mode)
- The bot invited to your server with the following intents:
- Message Content Intent
- Server Members Intent
- Guilds and Channels read access
Step 1 — Clone & install
git clone https://github.com/your-org/fluxer-ticket-bot.git
cd fluxer-ticket-bot
npm install
Step 2 — Run the setup wizard (recommended)
npm run setup
The wizard will ask for:
- Your bot token (from Fluxer → User Settings → Applications → Bot)
- Your Guild (Server) ID — right-click your server → Copy ID
- The Panel Channel ID — right-click the channel → Copy ID
- An optional Log User ID to receive copies of every transcript
At the end it creates .env and config.json for you.
Skip the wizard
If you prefer manual setup, copy the example files instead:
cp .env.example .env
cp config.example.json config.json
Then edit both files by hand — see Configuration Overview.
Step 3 — Edit config.json
Open config.json and replace the placeholder IDs in each ticket type:
{
"ticketTypes": [
{
"id": "general",
"label": "General Inquiry",
"categoryId": "123456789012345678", // ← right-click category → Copy ID
"supportRoles": ["987654321098765432"] // ← right-click role → Copy ID
}
]
}
See Ticket Types for all available fields.
Step 4 — Start the bot
npm start
You should see:
[TicketBot] ✅ YourBot#0000 is online
[TicketBot] Guild: 123456789012345678
[TicketBot] Panel channel: 987654321098765432
[TicketBot] Command prefix: !ticket
[TicketBot] Ticket types: general, billing, bug-report
[TicketBot] Archiving: enabled
Step 5 — Post the panel
In any channel your bot can write to, type:
!ticket panel
The bot will post the ticket selection embed in the configured panel channel and add the numbered reactions automatically.
That's it! ✅
Your users can now react to the panel to open tickets. Staff can react with 🔒, 🔓, or ❌ on the welcome message to control tickets.
Next steps:
- Configure ticket types to match your server's needs
- Set up archiving so transcripts are preserved
- Learn all admin commands