Springfield State RP / Management

Overview

● Dashboard preview
S
⚠
CAD backend added · staff sign-in requiredThe dedicated CAD & Dispatch page now has a secure Worker API, Discord staff sign-in, live ER:LC player data, dispatch calls and patrol units. Other management sections remain read-only previews until their controls are connected. No fake server stats are shown.
Bot status ◉
—
Waiting for Worker API
ER:LC players ♙
— / —
Live server count unavailable
Pending applications ▤
—
D1 connection required
Open tickets ▣
—
Discord API connection required

System health

Connection checks for Springfield services
Cloudflare Workerspringfield-state-rp-assist
Not checked
Discord botBot gateway and permissions
Not checked
ER:LC APIServer key stored as Worker secret
Not checked
D1 databaseApplications, sessions and moderation
Not checked

Quick links

Management shortcuts
Staff applications

Review submitted applications and record decisions with a reason.

CAD & Dispatch

Open the dedicated CAD board to manage incidents, patrol units, priorities and dispatch notes.

Session control

Manage session announcements and check current status.

Staff training

Read the same command guide available through /training.

Bot commands

Command catalogue from the Springfield bot.

COMMANDGROUPDESCRIPTIONSTATUS
/ping, /helpGeneralHealth check and command helpIn bot
/erlc, /servercount, /playersER:LCServer status and player informationIn bot
/ticket-setup, /ticket-open, /ticket-closeTicketsSupport ticket workflowIn bot
/session start, /session endSessionsSession announcements and statusIn bot
/apply, /application-setupApplicationsDM application and staff reviewIn bot
/trainingStaffStaff command guideIn bot
/warn, /timeout, /kick, /banModerationModeration actions and recordsIn bot

Staff applications

Applications are currently reviewed in your configured Discord review channel.

Live application records will appear here after the authenticated dashboard API is connected.

Current workflow: members run /apply, answer five DM questions, and staff use Accept or Decline with a reason in Discord.

Support tickets

Discord ticket channels and their current status.

Ticket management will appear here when Discord channel access is connected to the dashboard API.

Current commands: /ticket-setup, /ticket-open, /ticket-add and /ticket-close.

Session management

Session announcements and current session state.

Live session controls are not connected yet.

Current Discord workflow: /session start, /session end and /session status.

ER:LC server

Live server information from the ER:LC API.

Players online
—
Maximum players
—
Server information will load after the Worker dashboard endpoint is connected. The ER:LC key stays on Cloudflare and is never sent to this page.

Moderation

Warnings and moderation records.

Moderation records will appear here after secure staff authentication is implemented.

Current bot commands include /warn, /warnings, /timeout, /kick, /ban, /unban and /modlogs.

Staff training

Quick reference for Springfield staff.

Tickets

Use /ticket-setup to post the panel. Members can open a ticket, staff can add members, and the opener or staff can close it.

Sessions

Use /session start to announce a session, /session end to end it, and /session status to check the saved status.

Applications

Members run /apply. Review the five-question application in the private channel configured by /application-setup. Accept or decline with a clear reason.

Moderation

Use moderation commands only when authorised. Record clear, factual reasons, follow server rules, and keep member information private.

Settings & connections

Setup information for the dashboard and bot.

Cloudflare Worker

Worker name: springfield-state-rp-assist
Dashboard API: not configured
Database binding: DB

ER:LC API key

Store the key as a Cloudflare Worker Secret named ERLC_SERVER_KEY. Never paste it into this website, GitHub files, a public variable, or a browser form.

Discord connection

Bot credentials remain in Cloudflare Worker secrets. Dashboard sign-in and staff permission checks must be implemented server-side before enabling controls.

Database

Use the existing D1 database binding named DB. The bot uses it for applications, settings, sessions and moderation records.