Appearance
Glossary and external documentation
| Term | Meaning here |
|---|---|
| Account | Login identity, security settings and staff level |
| Character | A roleplay identity owned by an account |
| UCP | Player User Control Panel |
| ACP | Staff Admin Control Panel |
| Agent | Private Node service that owns/controls the game process |
| API scaffold | Optional Fastify /health service, not the ACP control bridge |
| SQL ID | Persistent database record identifier |
| Enum ID | In-memory Pawn array index |
| Engine ID | Temporary ID of a connected player/spawned vehicle/object |
| Faction type | Organisation family such as LEO or EMS |
| Capability | Bit flag granting a reusable faction action |
| Faction tier | Member authority, with 1 higher than 4 |
| Staff level | Account privilege, with 8 higher than 2 |
| Armory type | Named loadout/category assigned to physical lockers |
| Locker | A placed world access point to faction equipment/uniforms |
| Interior / virtual world | Location contexts checked alongside XYZ |
| Artwork | Downloadable model/texture assets registered by the game |
| SMTP | Mail submission/delivery transport |
| STARTTLS | Upgrade an established connection to TLS |
| Web 2FA | The framework’s emailed one-time-code login step |
Authoritative external references
Use these for upstream runtime/software details. The framework guides describe the project-specific choices around them.
- open.mp installation and Linux installation
- open.mp config.json reference
- sampctl
- YSI includes
- ColAndreas and Wizard
- EasyPanel App services
- Docker Mailserver installation
- Nodemailer SMTP
- VitePress documentation
Upstream packages and deployment panels can change. Match their documentation to the versions you deploy, especially runtime/plugin builds and mail-server configuration.