Roleplay community operations
PulseRP
Run applications, duty tracking, events, characters, staff workflows, and community modules.
Open PulseRPGetting started
The bot and dashboard share one MySQL database and one Discord permission model.
Invite the bot
Enable Server Members Intent, add the applications.commands scope, and start the bot with the same Discord application used by the web app.
Sign in to the dashboard
Select the guild, configure staff roles, and give administrator status only to trusted roles.
Enable modules
Turn on only the modules your server needs. Applications, clock tracking, and events start enabled by default.
Publish Discord surfaces
Use each module's setup command or dashboard action to post panels and messages after configuration is saved.
Modules
PulseRP currently includes ten independently configurable community tools.
Staff operations
Applications, clock in and out, leave of absence, and strikes and promotions.
Events and identity
Events and RSVPs plus member-managed character profiles.
Community tools
Suggestions, rules onboarding, giveaways, and live FiveM server status.
Verification ownership
PulseRP does not run member verification. Use PulseGuard for verification, risk scoring, and moderator review.
Discord cache and permissions
The web dashboard reads synchronized Discord state instead of calling Discord on every request.
Startup reconciliation
The bot refreshes guild metadata, roles, channels, members, and every member's roles when it starts.
Live events
Create, update, delete, join, role-change, and leave events keep the cache current while the bot is online.
Stale access cleanup
Deleted roles, departed members, and guilds removed while the bot was offline are purged from permission caches.
Web access
Guild owner, Discord Administrator, configured staff role, and configured admin role checks are evaluated from the synchronized data.
Troubleshooting
Bot and web deployments must point to the same database and Discord application.
Role or channel choices are empty
Confirm the bot has joined the guild, the database is shared, and startup cache synchronization completed.
A user has the wrong web access
Check Server Members Intent, the live Discord role, the configured staff roles, and the latest bot cache log.
A command remains after removal
Restart the bot so guild command synchronization overwrites the registered command set.
The dashboard cannot reach the bot
Verify the internal WebSocket URL and that BOT_INTERNAL_TOKEN matches on both deployments.