Whitelisting Zones

INFO

This documentation covers FiniAC's detection whitelisting zones, which allow you to disable specific detections in defined areas.

Overview

Whitelisting zones are a powerful feature that allows you to disable specific FiniAC detections within defined areas. This is useful when your server has features that may normally be flagged as cheating.

Common use cases:

• Paintball/PvP arenas - Allow spectating and specific weapons
• CCTV scripts - Avoid Freecam detections
• Garages - Allow vehicle plate changes and other vehicle-related detections

How It Works

1. Define a zone with coordinates and radius
2. Specify which detection types to disable in that zone
3. When a player is within the zone, those specific detections are skipped
4. Detections outside the zone or other detection types work normally

TIP

Zones only affect the specific detection types you list - all other detections remain active.

Creating Zones

Using the Command (Recommended)

The easiest way to create a zone is using the fini zone server-side command. This automatically generates the JSON configuration for you.

Command Syntax:

fini zone <source> <detection_types>

Parameters:

• source - Player source ID whose position will be the zone center
• detection_types - Comma-separated list of detection types to whitelist (no spaces)

Example:

fini zone 16 Explosion,MenuDetection,Spectate

This creates a zone at player #16's position that disables Explosion, MenuDetection, and Spectate detections. Position yourself in the center of the zone before running the command.

Output:

The command generates a link to a JSON file:

Whitelisting zone: https://paste.fini.dev/xxxxx

Open the link and copy the JSON object to add to your config.

Manual Creation

You can also manually create zone objects in JSON format.

Zone Structure:

{
  "position": [x, y, z],
  "radius": 75,
  "whitelist": ["DetectionType1", "DetectionType2"]
}

Properties:

• position - Array of three numbers [x, y, z] representing the zone center
• radius - Number representing the zone radius in game units (meters)
• whitelist - Array of strings listing detection types to disable in this zone

Example:

{
  "position": [1500, 500, 25],
  "radius": 100,
  "whitelist": ["Explosion", "InvalidWeapon", "Spectate"]
}

Available Detection Types

The following detection types can be whitelisted in zones:

Whitelisting zone types

Zone Type	Description	Common Use Case
Explosion	Explosion events	Event zones with explosives
Entities	Entity spawning	Areas where props/vehicles can spawn
InvalidWeapon	Blacklisted weapon usage	Zones where special weapons allowed
SpoofedDamage	Invalid damage events	Special combat zones
GodModeV2	God mode (armor-based check)	Protected/invincibility areas
GodModeV3	God mode (invincible flag check)	Protected/invincibility areas
VehiclePlateChanged	Vehicle plate modifications	Mechanic shops, customization areas
Spectate	Spectator mode detection	Spectator areas in events
Freecam	Free camera detection	CCTV systems, camera scripts
InvisiblePed	Invisible player detection	Stealth mechanics, RP scenarios
BadDamageModifier	Damage modifier detection	Custom damage zones
GodModePed	God mode (ped invincibility)	Invincibility zones
FlyHack	Flying detection	Flight-enabled zones
InfiniteAmmo	Infinite ammo detection	Shooting ranges, training areas
Noclip	Noclip detection	Admin areas (use carefully)
MenuDetection	Cheat menu detection	Testing areas (use very carefully)

Configuration

Adding Zones to Config

1. Open your FiniAC web panel
2. Navigate to your server's Config page
3. Find the "Detection whitelisting zones" config option
4. Add your zones as a JSON array of zone objects
5. Save your configuration

Single Zone Example:

[
  {
    "position": [1500, 500, 25],
    "radius": 100,
    "whitelist": ["Explosion", "Spectate"]
  }
]

Multiple Zones Example:

[
  {
    "position": [1500, 500, 25],
    "radius": 100,
    "whitelist": ["Explosion", "Spectate"]
  },
  {
    "position": [-200, 300, 35],
    "radius": 50,
    "whitelist": ["InvalidWeapon", "BadDamageModifier"]
  },
  {
    "position": [800, -400, 10],
    "radius": 150,
    "whitelist": ["VehiclePlateChanged"]
  }
]

Important

The zones must be a valid JSON array. Make sure to include the square brackets [ ] around all zones and commas between zones.

Best Practices

Recommendations

• Use smallest radius possible - Only cover the necessary area
• Be specific with detections - Only whitelist what you need
• Document your zones - Keep notes about where each zone is and why

Security Considerations

• Zones completely disable the specified detections within their radius
• Cheaters within zones can exploit whitelisted detection types
• Keep zones small and specific to minimize abuse potential

Troubleshooting

Zone Not Working

Problem: Detections still trigger inside the zone.

Solutions:

1. Verify the zone configuration is valid JSON
2. Check that you saved the config in the web panel
3. Verify the detection type name is spelled correctly (case-sensitive)
4. Confirm the player is actually within the zone radius
5. Check server console for config errors

Zone Too Large/Small

Problem: Zone covers too much or too little area.

Solutions:

1. Adjust the radius value in your zone configuration
2. Use in-game coordinates to measure the desired area
3. Test with different radius values until it fits properly
4. Remember radius is in meters/game units

Getting Player Coordinates

Problem: Need to find exact coordinates for a zone.

Solutions:

1. Use the fini zone command - it automatically uses player position
2. Use in-game coordinate displays from developer tools
3. Use a vehicle/teleport script to get precise coordinates
4. Stand exactly where you want the zone center before running command