π LRRP Admin | Complete RedM Administration Notebook | VORP | FREE + PREMIUM
LRRP_Admin is a complete database-backed administration system for RedM + VORP, built around an immersive two-page Western notebook.
Instead of cramming dozens of buttons into a conventional admin menu, LRRP Admin uses a clean category β profile β action structure. Player management, staff management, reports, cases, punishments, Law integration, Community Service, inventory administration, troll tools, logs and server controls are all handled through the notebook.
The UI is specifically designed around the physical book β nothing crosses the centre seam, nothing spills onto the leather, and large lists use pagination and drill-down pages to remain clean and readable.
π FREE and PREMIUM contain the same administration features.
The only difference is presentation:
πΈ FREE β LRRP-branded notebook with protected/fixed UI
πΈ PREMIUM β clean unbranded notebook
β MAIN FEATURES
β
Complete two-page Admin Notebook
β
Persistent Player Profiles
β
Persistent Admin Profiles
β
Staff hiring & firing
β
Staff promotion & demotion
β
Configurable staff ranks
β
Granular rank permissions
β
Individual staff permission overrides
β
Admin duty system
β
Player reports
β
Full admin Cases system
β
Warnings
β
Kicks
β
Temporary & permanent bans
β
Unban management
β
Punishment history
β
Staff notes
β
Restricted/senior notes
β
Full audit logging
β
Player management tools
β
Inventory management
β
Economy management
β
Job/character administration
β
Community Service integration
β
Law & Bounty integration
β
Built-in cinematic Kidnap system
β
Troll tools
β
World/server controls
β
Developer/admin utilities
β
Online + offline player searching
β
Database-backed histories
β
Pagination/search/filtering
β
Optional integrations automatically detected
π TWO-PAGE NOTEBOOK UI
LRRP Admin is designed as an actual notebook rather than a normal web panel placed over a book image.
π Left and right pages are completely separate UI containers.
β
Nothing crosses the centre spine
β
Nothing renders onto the leather
β
Nothing leaves the parchment
β
Long lists use pagination
β
Large sections use subcategories
β
Context-sensitive player actions
β
Search and filtering
β
Resolution-friendly scaling
Instead of displaying every possible action at once:
Players β Select Player β Profile β Category β Action
This keeps even a very large admin system easy to navigate.
ποΈ NOTEBOOK CATEGORIES
π Dashboard
Server overview, online players, admins on duty, reports, active cases, recent activity and quick information.
π₯ Players
Online players, offline search, player profiles, notes, history and player-specific administration.
π© Reports & Cases
Unclaimed reports, assigned reports, active cases, resolved cases and historical case records.
βοΈ Moderation
Warnings, kicks, bans, Community Service, Kidnap and punishment management.
β Law
Optional LRRP Law & Bounty administration and player law information.
π‘οΈ Staff
Staff profiles, hiring, firing, promotions, demotions, duty, ranks and permissions.
π οΈ Admin Tools
Administrative and developer utilities including teleport/spectate-style functionality and other staff tools.
π€ Troll
Separated troll/player-effect tools with independent permissions and audit logging.
π World & Server
World administration, announcements and protected server controls.
π Logs
Searchable administrative actions, punishments, staff changes, integrations and audit history.
βοΈ Settings & Integrations
Rank permissions, optional integrations and configurable administration settings.
π€ PERSISTENT PLAYER PROFILES
Every player can have a persistent administrative profile stored in the database.
Profiles can contain:
πͺͺ Character/player information
π Staff notes
β οΈ Warning history
βοΈ Punishment history
π Cases
π© Reports
βοΈ Community Service information
β Law information
π Inventory administration
π° Economy administration
π οΈ Player actions
Historical information is retrieved on demand rather than loading every player profile into server memory.
This makes the system suitable for servers with large historical player databases.
π‘οΈ COMPLETE STAFF SYSTEM
Built-in hierarchy:
π Owner
β Manager
π΄ Snr Admin
π΅ Admin
π’ Snr Mod
π Mod
βͺ Trial-Mod
Authorized staff can:
β
Hire staff
β
Fire staff
β
Promote staff
β
Demote staff
β
Suspend/reinstate staff
β
View Admin Profiles
β
Configure lower-rank permissions
β
Apply individual permission overrides
β
Review administrative history
Staff records are persistent.
Firing somebody does not destroy their staff history. If they are rehired later, their previous administrative record can remain available.
π GRANULAR PERMISSIONS
Permissions are not limited to broad groups such as simply admin or moderator.
Individual abilities can be controlled separately.
Examples include:
πΈ Warn
πΈ Kick
πΈ Ban
πΈ Permanent Ban
πΈ Community Service
πΈ Kidnap
πΈ Inventory viewing
πΈ Inventory editing
πΈ Economy controls
πΈ Law actions
πΈ Staff hiring
πΈ Staff firing
πΈ Rank management
πΈ Troll tools
πΈ Server/world controls
π Owner can configure rank permissions.
β An authorized Manager can manage permissions for ranks below Manager, but can only grant permissions that the Manager personally possesses.
Staff cannot manage equal/higher ranks.
All sensitive actions are validated server-side.
π ADMIN CASE SYSTEM
Reports and incidents can become proper persistent administrative cases.
Cases can contain:
π₯ Involved players
π‘οΈ Assigned staff
π Staff notes
β οΈ Warnings
βοΈ Punishments
π© Related reports
π Timeline/history
π Case status
This allows staff to review what happened previously instead of relying on Discord messages or individual staff memory.
β οΈ WARNING SYSTEM
Issue persistent warnings directly through a player's notebook profile.
Warnings can be stored with:
π Reason
π‘οΈ Issuing staff member
π
Date/time
π Related case
π Administrative notes
Historical warnings remain accessible from the player's profile.
βοΈ BUILT-IN CINEMATIC KIDNAP
LRRP Admin contains the LRRP cinematic Kidnap experience directly inside the resource.
No separate Kidnap resource is required.
Includes:
π NPC kidnap sequence
π₯ Multiple kidnappers
π Mounted pursuit handling
π Grab/punch sequence
πΌοΈ Full-screen βYou Have Been Kidnappedβ sequence
π Delivery in front of the admin
βοΈ Built-in restraint state
π Kidnap/bag behaviour
π Admin release/free functionality
π Audit logging
π« The gag feature is not included.
Kidnap is available from the selected player's profile and can be individually permission-controlled.
βοΈ LRRP COMMUNITY SERVICE INTEGRATION
LRRP Admin automatically detects:
LRRP_comps
When installed, authorized admins can issue and release Community Service through the notebook.
LRRP Admin uses Community Service's supported exports, meaning the Community Service resource remains responsible for its own FREE/PREMIUM limits and sentence rules.
If Community Service isn't running, LRRP Admin fails safely with:
βPlease install LRRP Community Serviceβ
Community Service is optional and is not required to run LRRP Admin.
β LRRP LAW & BOUNTY INTEGRATION
LRRP Admin automatically detects supported components from the LRRP Law & Bounty System.
Supported integration architecture includes:
βοΈ LRRP Law
π° Bounty systems
π Law records/status
βοΈ Jail actions
π΅ Fine actions
π― Wanted/Bounty information
π Lawpad integration
Law permissions can be configured independently for each staff rank.
The Law package remains optional.
LRRP Admin continues functioning normally without it installed.
π LRRP INVENTORY SUPPORT
Native support for:
β
LRRP_Inventory FREE
β
LRRP_Inventory PREMIUM
LRRP Admin automatically detects LRRP_Inventory and uses its public inventory exports directly.
Authorized admins can access inventory tools through the selected player's profile.
Includes:
π View inventory
β Add items
β Remove items
βοΈ Carry-capacity checks
π Administrative audit logging
If LRRP Inventory isn't running, compatible vorp_inventory installations can be used as a fallback.
LRRP Inventory is always preferred when both are detected.
π€ TROLL TOOLS
Troll tools have their own notebook category rather than cluttering normal moderation.
They can be independently permission controlled.
Server owners can choose which ranks can access troll functionality or disable access entirely.
Troll actions are also recorded in the Admin Audit Log.
π DATABASE-BACKED ADMINISTRATION
Persistent information is stored in MySQL, including systems such as:
β
Player profiles
β
Admin profiles
β
Staff notes
β
Warnings
β
Punishments
β
Bans
β
Reports
β
Cases
β
Case/player associations
β
Staff ranks
β
Rank permissions
β
Individual permission overrides
β
Duty sessions
β
Audit logs
LRRP Admin does not load every historical player profile into server memory.
Records are queried when required and large histories use pagination.
π FREE EDITION
β
Full admin system
β
Full Player Profiles
β
Full Admin Profiles
β
Reports & Cases
β
Staff management
β
Rank permissions
β
Community Service integration
β
Law integration
β
LRRP Inventory integration
β
Kidnap
β
Troll tools
β
Logs
β
Server/admin tools
π¨ Uses the LRRP-branded notebook.
π FREE UI presentation/branding is protected and cannot be customized.
π FREE DOWNLOAD:
https://the-lost-riders-mmorpg.tebex.io/category/free
π PREMIUM EDITION
Everything included in FREE.
β¨ Clean/unbranded notebook
β¨ Designed for servers wanting their administration interface without LRRP presentation branding
There are no additional gameplay/admin powers locked behind PREMIUM.
π PREMIUM DOWNLOAD:
https://the-lost-riders-mmorpg.tebex.io/category/premium
βοΈ CFX / REDM REQUIREMENTS
Required
π΄ RedM Server
βοΈ CFX cerulean FX version
π RDR3 / RedM
π¦ CFX Asset Packs support
-
/assetpacks -
/assetpacks-redm
π§ Lua 5.4
ποΈ VORP Core
-
vorp_core
ποΈ oxmysql
-
oxmysql
πΎ MySQL/MariaDB database
π Run the included:
sql/install.sql
Optional integrations
π LRRP_Inventory β preferred inventory system
π vorp_inventory β compatible fallback
βοΈ LRRP_comps β Community Service
βοΈ LRRP_law β Law integration
π° LRRP_BountyHunting β Bounty integration
π Compatible LRRP Lawpad resources
Optional integrations are not required for the base Admin resource.
π¦ INSTALLATION
1οΈβ£ Download your FREE or PREMIUM edition.
2οΈβ£ Extract the resource.
3οΈβ£ Do not rename the resource.
The folder must remain:
LRRP_Admin
4οΈβ£ Place LRRP_Admin inside your RedM resources folder.
5οΈβ£ Import:
sql/install.sql
into your server database.
6οΈβ£ Make sure the required dependencies start before LRRP Admin.
Recommended order:
ensure oxmysql
ensure vorp_core
ensure LRRP_Inventory (if used)
ensure LRRP_comps (if used)
ensure LRRP_law (if used)
ensure LRRP_BountyHunting (if used)
ensure LRRP_Admin
7οΈβ£ Configure the editable settings and permission configuration.
8οΈβ£ Restart the server.
π§ CONFIGURABLE WITHOUT EXPOSING THE CORE
Important server configuration remains editable while the core administration logic remains protected.
Escrow-ignored configuration includes:
βοΈ config.lua
π shared/permissions.lua
ποΈ SQL installation files
π README / installation documentation
This allows server owners to configure LRRP Admin without exposing unnecessary core implementation.
π CFX MANIFEST INFORMATION
β
fx_version 'cerulean'
β
game 'rdr3'
β
Lua 5.4
β
RedM asset-pack requirements
β
vorp_core dependency
β
oxmysql dependency
β
NUI notebook interface
β
CFX Asset Escrow-ready structure
β
Config/permissions/SQL documentation escrow ignored
π FREE VS PREMIUM
Feature
π FREE
π PREMIUM
Admin Notebook
β
β
Player Profiles
β
β
Admin Profiles
β
β
Reports & Cases
β
β
Staff Ranks
β
β
Custom Permissions
β
β
Warnings / Kicks / Bans
β
β
Community Service
β
β
Law & Bounty Integration
β
β
LRRP Inventory Integration
β
β
Cinematic Kidnap
β
β
Troll Tools
β
β
Audit Logging
β
β
Database Persistence
β
β
LRRP Branding
β
β
Clean Notebook
β
β
Same functionality. Different presentation.
π SUPPORT
Need help installing or configuring LRRP Admin?
π¬ LRRP Studios Support:
https://discord.gg/RMPMrdzy8k
π DOWNLOADS
π FREE
https://the-lost-riders-mmorpg.tebex.io/category/free
π PREMIUM
https://the-lost-riders-mmorpg.tebex.io/category/premium
π LRRP_Admin β Administration built like an actual staff notebook.
π₯ Manage players.
π‘οΈ Manage staff.
π Investigate cases.
βοΈ Moderate your server.
π Connect your LRRP systems.
π Keep a permanent administrative history.