Skip to content
D2D

Setting up D2D in your server

What this does

Your Discord server becomes a Sector the moment D2D joins it — registered automatically, no command needed. But gameplay commands (racing, marketplace, economy) only fire inside channels you’ve promoted to Systems. This guide walks you through that one-time setup.

Prerequisites

  • Server ownership or Administrator permission — you’ll need Manage Channels to enable systems.
  • The bot is not yet in your server, or you’re setting up a fresh channel.

Some commands work the moment the bot joins, before any system exists: /start, /profile, /inventory, /inspect, /hangar, /equip, /autoequip, /peek, and /sector_info. Racing, packs, the marketplace, and daily rewards require a live system and will fail with “Game not enabled here” until you complete step 3.

Step-by-step walkthrough

1. Invite the bot

Use the official OAuth2 invite link (ask in the D2D community for the current one). Select your server in the Discord prompt and confirm. The bot registers your server as a Sector automatically on join.

2. Understand the two-tier geography

TermWhat it maps toCreated how
SectorYour Discord serverAuto-registered on invite
SystemA single channel inside the serverYou enable it with /system_enable

A Sector starts with zero systems. Gameplay commands that require a system return a “Game not enabled here” message — your cue to enable the channel.

3. Enable a channel as a system

Go to the channel you want for gameplay, then run:

/system_enable

/system_enable requires the Manage Channels Discord permission. On success the bot confirms the new system’s name, how many systems are active out of the sector’s cap, and a brief description of the star type and planets it generated. You can enable more than one channel — each gets its own generated star system.

4. Verify setup

Run /sector_info from any channel for a Sector summary: name, active system count, and a line per system showing band, star type, and Lighthouse status.

For a deeper look at one system, run /system_info inside that channel (or pass the system name as an argument from anywhere).

5. Point players at the right channel

Tell your players which channel is the enabled system. Anyone can run /start there to create an account and pick a hull class. Inventory and build commands work from any channel; racing and economy commands only resolve in an enabled system.

What “success” looks like

  • /sector_info shows at least one active system.
  • /system_info in the enabled channel returns the star system description rather than a “not enabled” error.
  • A player running /start gets the onboarding flow.
  • /race in the enabled channel resolves normally; the same command in a non-enabled channel returns “Game not enabled here.”

Common gotchas & troubleshooting

“Only server admins (manage_channels) can enable systems.” You lack the Manage Channels permission. Ask a server admin to run /system_enable or to grant you that permission.

“This channel is already an enabled system.” The channel is already live. Use /system_info to confirm — no further action needed.

“Sector not registered. Try kicking and re-inviting the bot.” Automatic sector registration didn’t complete on join. Remove the bot and re-invite it; the sector registers on the next join event.

“Game not enabled here…” A player used a gated command in a non-enabled channel. The notice asks them to get an admin to enable it. Send them to the correct channel, or run /system_enable here to open gameplay in this channel.

System cap exceeded — “can only sustain N active system(s) at its current influence.” Disable an existing system with /system_disable to free a slot. The cap can be raised by the bot owner.

The system’s display name doesn’t match the channel name. Run /system_rename with a new_name argument (up to 100 characters) to update the in-game name without renaming the Discord channel.