AstroShield reads a few FiveM ACE permissions. This page lists all of them.
| ACE | Who needs it | What it does |
|---|---|---|
resource.AstroShield command | The AstroShield resource itself | Required. Lets it run console commands. Without it the resource does not connect. |
add_unsafe_child_process_permission AstroShield | The AstroShield resource itself | Required. Lets it write files for updates and astroinstall. |
astroshield.admin | Your staff | Opens the in-game panel and lets them use all of it. |
astroshield.bypass | Trusted staff | Marks a player as an admin for the txAdmin whitelist. |
The first two are the lines from the installation.
Give staff access to the panel#
You can do this in the dashboard, with the Ingame Panel permission, or with an ACE:
add_ace group.admin astroshield.admin allow
add_principal identifier.discord:123456789012345678 group.adminThe ACE route works without any dashboard account. The player only needs to be in the group.admin group, here through their Discord ID. Replace the ID with your own.
Exempt admins from detections#
Admins do things that look like cheating: they teleport, spectate, fly and spawn vehicles. Switch on txAdmin Whitelist under Configuration, General, so that admins are ignored by the detections, by custom rules and by punishPlayer.
A player counts as an admin when one of these is true:
- they are a txAdmin admin who is signed in to the server,
- they hold the ACE
astroshield.bypass, - they hold the ACE
txAdmin.botCompatibility, - they hold the global
commandACE, which is what the usual admin group of a txAdmin recipe has.
# Only needed if your staff are not txAdmin admins
add_ace group.moderator astroshield.bypass allowAdmin status is read when a player joins and when txAdmin reports a change, so give the ACE before the player connects.
Check who counts as an admin#
astroshield players in the server console prints admin: true or admin: false for every online player. See Console commands.
Other ways to exclude things#
Admins are one case. If a resource or a single event triggers detections that you know are harmless, ignore it instead of whitelisting a person:
- Ignored Resources and Ignored Events in Network & Moderation. See Event protection.
- Tell AstroShield about legitimate actions of your own scripts. See Allowances.