TX · OPERATIONS BRIEF

Lines Police CAD
Discord Bot.

Run panic alerts, Signal 100, dispatch status, civilian look-ups, and the full economy loop — without leaving Discord. Built for police-RP communities, wired into the same CAD your members already use.

Add to your server 3-step setup
02 · INITIATE LINK

Get the bot online in three steps

Total time: under 2 minutes. Full walkthrough also lives on linespolice-cad.com/discord-bot.

  1. 01/

    Add the bot to your Discord server

    Click the button below to invite the Lines Police CAD bot. You'll need Manage Server on Discord to install bots there.

    Add Bot to Server

  2. 02/

    Authorize the bot

    Pick the Discord server you want it in, then click Authorize. Discord will add the bot with the permissions it needs to post embeds and run slash commands.

  3. 03/

    Connect your account

    Open your LPC profile and click Connect Discord to link your account. Every member who wants to run commands has to do this for themselves.

    WATCH FOR You are not logged in. — that error means this step isn't done yet.

03 · COMMAND REFERENCE

Every slash command, in one place.

Pulled directly from commands/*.js in the bot repo. If a command changes, this list rebuilds — no drift, ever.

04 · FAQ

Common rejections, decoded.

"You are not logged in." — what now?

Your Discord account isn't linked to a Lines Police CAD account. Sign in at linespolice-cad.com, open Account → Connections, and connect Discord. Then retry the command.

"You must join a community to use this command."

Almost every command runs against your active community (dispatch status, search, economy, etc.). Join one on the website, then re-run.

"You are not allowed to use the bot in this channel."

A server admin has restricted the bot via /channels set. Run /channels view in any channel the bot can post in to see the allowlist, or have an admin add the current channel.

"You don't have permission to use this command."

The bot keeps its own allowed-roles list, set with /roles. This is separate from Discord's permissions — once any role is added, only members who have one of those roles can run commands. Being a server admin or owner doesn't bypass it, and Discord's per-command permission overrides won't change it either. That's usually why "I'm an admin and it still blocks me" happens.

The bot now names the required role(s) right in the error. To fix it, anyone with Manage Server should:

  1. Run /roles view to see which role(s) are required.
  2. Run /roles remove role:@TheRole for each one — removing the last role turns the restriction off entirely and everyone can use the bot again.
  3. Prefer to keep it restricted? Run /roles set role:@YourStaffRole with a role your members actually have.

If the gating role was deleted from the server, the restriction clears automatically the next time any command is run.

"Economy is not enabled in your community."

The economy suite (/clock-in, /wallet, /inbox, /pay-fine, /contest-fine, /send-money) requires the community owner to enable economy on the website.

"You already have an active shift. Use /clock-out first."

Only one shift can be active at a time. Run /clock-out to end it, then /clock-in again for the new department.

05 · CONTACT

Need a hand? We're on the radio.

Live chat Join the Discord Real-time help from the team and other community owners. Got an idea? Request a feature Suggest a new command, integration, or quality-of-life improvement. Something broken? Report a bug File it on GitHub — auto-tagged and routed to the right repo.