Roleplay
Applications, duty tracking, events, and member records migrating from PulseRP.
Start here
Set up duty and application review
PulseOne → Dashboard → select your server → Modules → Roleplay
Open Modules → Roleplay and expand Roleplay setup.
Set the staff review channels and optional leave/strike log channels in the configuration.
Open Application forms and reviews to create and test a draft application.
Use the roleplay duty controls to Clock in with a test department member.
Review the staff queue for the application and verify activity and role permissions in the intended department.
Practical example
Create an application for a test department, submit it as a member, then approve it from the staff review queue.
Before you begin
- No module dependency listed.
- Discord bot permissions for the operational slice: ViewChannel, SendMessages, EmbedLinks.
- Review staff roles and channel access in your server before using the feature.
Overview of the setup
Before you begin
Configure departments, permissions and application review roles before accepting public submissions.
Configure
Create a test application, change its review state and record a duty session.
Test and verify
Schedule an event and test RSVP/waitlist behavior; audit a rank change or staff strike.
Features explained
What each feature does and what to check before publishing or installing the result.
Applications, review queues, and department duty tracking
Applications and review queues keep recruitment decisions accountable; duty logs require correct department access.
Events, RSVPs, waitlists, recurrence, and reminders
RSVPs, waitlists and recurring events require an unambiguous timezone and cutoff.
Characters, leave requests, staff strikes, and rank history
Character records, leave requests, staff strikes and rank changes need restricted staff visibility.
If it still does not work
- Cannot clock in? The duty action requires a configured department.
- Review not visible? Check staff role permissions and log-channel access.
Troubleshooting and safety checks
- Member cannot access roleplay functions? Check department membership, role mapping and module grants.
- If a capability is unavailable in the UI, check the module's current rollout/availability instead of assuming every roadmap item is live.