
- ESX
By Luke

Use txAdmin’s player management to ban the correct player from your community server, recording the rule, reason and duration. This is a server moderation action; it does not create a global Cfx.re platform ban.
Confirm the applicable rule and evidence before acting. Use an account with the required txAdmin ban permission and keep staff privileges limited. See the official txAdmin permissions reference.
Match the player using the recorded identifiers and incident time, not a display name alone. In-game numeric IDs can be reused after a player leaves.
Check the action log and ban record to confirm the target, duration and staff account. On staging, use a test account to verify the rejection and later revocation path before relying on a new policy.
Give the affected player an appeal route and the reference needed to identify the decision. Do not promise a fixed response time that your team cannot meet.
Locate the exact action/ban record and use the revocation control supported by your version. Record why it was corrected and verify the final state. Do not delete unrelated player history or restart txAdmin’s monitor resource as a generic repair.
If a ban seems ineffective, check the actual record, profile, expiry/revocation state and connection logs. Avoid guessing at hardware identifiers or undocumented toggles. Use the official txAdmin documentation and source for version-specific behavior.





