Appearance
ACP players, bans and access lists
Open /acp from an authorised staff account. The primary areas group player tools, faction tools, operations and audit screens. Tabs change with your role and current section.
Find the right player
Use Players → Search to find an account. Open its account detail, then the relevant character. The account ID, character SQL ID and temporary in-game player ID are different values. Confirm names and IDs before editing or applying a penalty.
Account detail tabs expose characters, connections, administrative records, supported settings, penalties and related logs. Character pages support viewing, investigation and authorised editing. Some operations require the target to be offline; follow the error rather than changing the database behind the game.
Penalties
Active-penalty views help identify restrictions already in force. Use the supported forms for offline jail and restriction flags. Enter a meaningful reason and check the intended scope: an account-wide restriction can affect multiple characters.
Use the permissions guide for rank values. Action-level checks can be stricter than the page’s navigation requirement.
Account/IP bans versus engine bans
| Store | Meaning | ACP area |
|---|---|---|
| Database ban records | Account/IP restrictions checked by application/game logic | Bans |
Root bans.json | IP entries managed by open.mp itself | bans.json |
Permanent database bans use an unban time of 0; a future unban time is a temporary active ban. The web login/session checks include both forms. Expiry is not the same as deleting the audit history.
The engine-ban screen uses the agent to manage the file in the game root. It is not merely another view of the SQL ban list. A connection blocked before account login may need investigation in both places. Follow engine reload/restart behaviour when editing its ban file.
Shared IPs and whitelists
Shared-IP information supports investigation; an IP match alone is not proof of misconduct. Registration checks can prevent multiple accounts from the same address. Use the account-registration whitelist tools when your community intentionally permits an exception.
VPN exceptions use the vpn_whitelist database table, managed through ACP. The removed vpn_whitelist.ini is not used. The retained geoip.db is optional offline country/ISP data, not a currently active local VPN-detection database.
After an edit
Review the confirmation and relevant audit record. For offline character edits, have the player load the character again. For staff promotions/demotions, verify access with the affected role. Never share your own session or authentication code to let another staff member perform a task.