Appearance
What is OpenRP Framework?
OpenRP Framework is an open-source Pawn roleplay framework developed for open.mp. It combines game systems with a Next.js public server website, User Control Panel (UCP), Admin Control Panel (ACP) and a small server-control agent. ORP Framework is the short name.
You supply the community identity, map configuration, server rules and world content. The framework supplies the systems those decisions use. SA-MP may require compatibility changes; the documented target is open.mp.
What you receive
| Component | Location in the framework | Responsibility |
|---|---|---|
| Gamemode | gamemodes/ | Accounts, characters, roleplay, staff tools and world systems |
| Clean database | database/schema.sql | Structure, settings and starter faction records |
| Dependency configuration | pawn.json | sampctl dependencies and compiler settings |
| Community web platform | web-platform/web/ | Public server site, UCP and ACP in one application |
| Server agent | web-platform/samp-agent/ | Game process ownership, console stream, model files and engine ban file |
| API scaffold | web-platform/api/ | Optional Fastify service with a health endpoint |
| Voice template | web-platform/livekit/ | Optional external voice-service configuration |
The OpenRP Framework project website and this documentation are maintained separately from the downloadable framework. Do not confuse that site with the community website template in web-platform/web/.
Gameplay foundations
The source includes account and character persistence, vehicles and dealerships, houses and businesses, furniture, jobs, banking, phones, chat, injuries, medical care, police tools, factions, armories, uniforms, attachments, staff reports and logging. Optional gang systems can be enabled by the server owner.
Only SAPD and FDSA are seeded as starter legal factions. FDSA uses the EMS faction type for fire and medical access. News and other supported types remain available for communities to create their own factions.
What “blank framework” means
There are no shared administrator credentials, seeded player characters or ready-made properties and persistent vehicles. Bespoke mapping and custom character models are not supplied. Stock model systems remain, along with small UI assets needed by the game interface.
Many map-specific positions are deliberately 0, 0, 0 with a TODO: set coordinates for your map marker. This is configuration work, not a finished playable map. Fuel pump, vending machine and basketball replacements are deliberate exceptions to restoring stock world objects.
Recommended reading order
Start with the setup checklist. Configure the world, then complete the production checklist. Staff should read the permissions guide before receiving privileged access.