Discovery Bot Logo Discovery Bot
Setup Guide

Launch Discovery Bot in Minutes

Follow this interactive checklist to invite the bot, activate your plan, register Nitrado servers, and verify logging so POIs, quests, bulletin boards, discovery zones, and discoverables work immediately.

Start Setup Open Dashboard More Info
Phase

Invite & Subscribe

Bot added, plan active, ticket confirmed.

Phase

Configure Server

/add_server completed, ADM logs flowing.

Phase

Power Features

POIs, quests, bulletins, zones, discoverables.

Live Checklist Phase 1 of 3
Connect Configure Finish

Setup Flow

Pick a phase to see detailed steps, copyable links, and hints tailored to first-time admins.

Step 1

Invite the Bot

Add Discovery Bot to the Discord guild you plan to manage.

You can also click the bot inside Discord and press “Add App” if you already share a guild.
Step 2

Subscribe

Purchase Standard or Premium from the website.

Look for the yellow “Subscribe” button in the top-right corner of every site page.
Step 3

Open a Ticket

Ping staff in create-a-ticket so they can verify your order.

Provide your Discord server name and order email to speed up activation.
Step 4

Staff Confirmation

Support flips your subscription live so you can proceed to configuration.

Once confirmed, you will see the bot respond to /add_server inside your guild.
Command

/add_server

Register your Nitrado credentials.

/add_server server_name:<Alias> token:<NitradoToken> server_id:<ID> [map:<Map>]
Token = long-life API token with “Service” checked. Server ID = numbers in your webinterface URL.
Accuracy

Double-check Inputs

  • Server Name: Friendly alias
  • Token: Long-life token
  • Server ID: Digits in URL
  • Map: chernarusplus / enoch / sakhal
A single typo will prevent ADM ingestion and file access—slow down and review once more.
Logging

Enable ADM Logs

Turn on logging in the Nitrado webinterface and play for ~5 minutes so the log rotates.

This prevents “ADM not found” errors when POIs or quests try to read player locations.
Power Users

Server JSON Presets

Need build-anywhere or unlimited stamina? Use the dashboard “Gameplay Presets” once servers are added.

Dashboard presets mirror /editgameplayjson but save backups automatically.

Log Channels

Use /setlog type:<...> channel:<#channel> for general/poi/quest/bulletin/economy/npc_feed logs.

Link Players

/linkplayer ties IGN to Discord for DM flows and stats.

First POI

/addpoi to verify map hooks + ADM routes.

Optional Extras

Enable extras: bulletins, quests, zones, discoverables, gathering/crafting economy, prison controls, pigeon coops, and auto-restarts.

Pro Tip

Keep Nitrado tokens private: only paste inside slash commands or the dashboard.

Reminder

Dashboard access = Admin permission or a role listed Staff,Moderator,Admin,Owner.

Safety

Every server file upload triggers an automatic backup you can roll back to.

Power Admin Toolkit

One-click access to the commands and resources you’ll use most often.

Commands

Server Lifecycle

/list_servers
/restart_server <name>
/set_map <name> <map>
Need guidance?
Commands

Auto Restarts

/setautorestart <server> <hours> <#channel> [message]
/viewautorestarts
/editautorestart
/removeautorestart
Resources

Important Links

Discovery-Bot.com ↗ Nitrado Tokens ↗ Nitrado Dashboard ↗

Advanced Systems Quick Start

After core setup is working, use these starter commands first. Full option lists are on the Commands page.

Gathering & Economy

Materials, Wallets, Crafting

/gather zone create <server_name> <zone_name> <x> <z> <radius> [cooldown_minutes]
/economy policy_set <server_name> [...]
/crafting recipe create <name>
  • Set policy first, then create materials/recipes.
  • Use gather zones to control where materials can be farmed.
Prison

Manual Queue / Release

/prison <server_name> @user
/prison <server_name> @user remove:true
  • Use optional fields only when you need case-specific overrides.
  • Default enforcement behavior remains active automatically.
Pigeon

Coops & Interception

/pigeon create_coop <server_name> <coop_name> <mode> <radius> <risk_multiplier> <weather_risk>
/pigeon send <server_name> <@player> <letter>
/pigeon intercept <server_name> <intercept|shootdown> [target]
  • Add optional location/tags/channels/role after initial coop creation.
  • Use interceptor role setup before enabling intercept gameplay.
Quests

NPC Quest Starter

/createquest <server_name> <x> <z> <quest_name> <dialogue>
/editquest <server_name> <quest_name> [field...]
  • Add gates/rewards/media after base quest creation.
  • Use edit options to tune role, item, and prerequisite logic.
Full Gathering & Economy Cmds Full Quest + Prison Cmds Full Pigeon Cmds

Reference Gallery

Visual cues for the exact screens you’ll use when collecting IDs and tokens.

Server ID: numbers in your Nitrado webinterface URL.
Long-life token: tick “Service” so the bot can restart servers.
Enable logging and let the server run 5 minutes to avoid ADM errors.

Setup Knowledge Base

Keep these reminders handy while progressing through the checklist. Every card links directly to the relevant action.

LLT

Long-Life Token (LLT)

Create one token per Nitrado account via Settings → Developer Access → Generate Token. Tick Service.

Open Portal
Server ID

Find Server ID

Inside the Nitrado webinterface URL: .../services/1234567/game/server. Use only digits.

Logging

ADM Logging Health

Enable logging, restart, then play 5 minutes to rotate logs before running /add_server.

Skip to Logging Step

Setup FAQ & Troubleshooting

Quick answers for the most common blockers while onboarding Discovery Bot.

How do I create a Long-Life Token? What is an LLT?

An LLT is a Long-Life Token that grants Discovery Bot API access to your Nitrado service.

  1. Login to Nitrado Developer Tokens.
  2. Click Create New Token, name it (e.g., DiscoveryBot).
  3. Select Service permission (mandatory) and generate.
  4. Copy the token immediately; paste it into /add_server token:<LLT>.
Where do I find my Nitrado Server ID?

Open your server dashboard. The URL shows /services/1234567/ — use those digits only.

Example: https://webinterface.nitrado.net/12345678/wi/gameserver/.

I made a typo in the ID or token. What now?

Just re-run /edit_server with the corrected values. No need to remove first.

If tokens leaked, revoke via the Nitrado portal and generate a new LLT.

I forgot to tick “Service” when creating the LLT.

The bot can’t restart servers without Service scope. Delete the old token and create a new one with the Service checkbox enabled, then run /edit_server.

Logs stopped or ADM says “not found”.

Ensure logging is still enabled, restart the server, then play 5+ minutes so fresh logs rotate. Re-run /setlog type:poi channel:#poi-logs (or the relevant type) if needed.

Full view