FiniAC Documentation

Appearance

Entity Whitelisting ​

INFO

This documentation covers FiniAC's entity whitelisting system, which prevents unauthorized entity spawning on your server.

Overview ​

FiniAC's entity whitelisting system provides advanced protection against cheaters spawning entities (vehicles, props, peds) on your server. The system works by tracking which entities are spawned by legitimate resources and only allowing those specific entities from those specific resources.

How it works:

  • Records all entities spawned during normal server operation
  • Associates each entity with its source resource
  • Blocks any entity that doesn't match the whitelist pattern
  • Even if a cheater spawns an allowed entity, it will be blocked if it doesn't come from a whitelisted resource

Recording Entities ​

To build your entity whitelist, you need to record entities during normal server operation when all your scripts are running.

Commands ​

fini entities record ​

Starts recording all entities that spawn on your server.

Usage:

bash
fini entities record

What happens:

  • FiniAC begins tracking all entities created on the server
  • Each entity is recorded with its model hash and source resource
  • Recording continues until you run the show command or restart the server

When to use:

  • After a fresh server restart
  • When legitimate players are on your server

fini entities show ​

Outputs all recorded entities to a pastebin link.

Usage:

bash
fini entities show

Output:

  • Displays the number of entities recorded and recording duration
  • Generates a link containing the entity list in JSON format
  • The link will appear in your server console

Format example:

json
["my_car_script:1234567", "my_prop_script:7654321", "9876543"]

Entities are stored as:

  • resource:hash - Entity spawned by a specific resource
  • hash - Entity with no associated resource

Setup Guide ​

Step 1: Record Entities ​

  1. Start your server
  2. Run the command:
    bash
    fini entities record
  3. Let your server run normally for a while
  4. Try to make sure that all server features that spawn entities are tested.

TIP

Record for at least a few hours to ensure all entities are captured. For best results, repeat this process over multiple restarts.

Step 2: Export the List ​

  1. Run the command:
    bash
    fini entities show
  2. A link will appear in your console
  3. Open the link in your browser
  4. Click "View Raw" (top right corner)
  5. Copy the entire JSON array

Step 3: Configure Whitelist ​

  1. Open your FiniAC web panel
  2. Navigate to your server's Config page
  3. Find the "Entity list" config option
  4. Paste the entire JSON array into the text field
  5. Find the "Entity list type" config option
  6. Change it from Blacklist to Whitelist
  7. Save your configuration

Important

Make sure you copy the entire JSON array including the square brackets [ ]. The web panel will format it automatically.

Step 4: Verify ​

After saving your configuration:

  1. Monitor your server for any entity-related detections
    • BadEntityCreating
    • EntityProtection
  2. If any legitimate entities are blocked:
    • Repeat the recording process
    • Add the new entities to your entity list manually
    • Or add the entity's resource to Resource entity whitelist (see below)

Troubleshooting ​

Legitimate Entities Being Blocked ​

Problem: Players report vehicles or props not spawning.

Solutions:

  1. Check your server logs for BadEntityCreating or EntityProtection detections
  2. Note the hash and resource from the detection
  3. Add the entity to your whitelist:
    • Format: "resource:hash" or "hash"
    • Or add the resource to Resource entity whitelist
  4. Save and test again

Recording Shows No Entities ​

Problem: fini entities show reports 0 entities recorded.

Solutions:

  1. Verify you ran fini entities record first
  2. Make sure entities were actually spawned after running record
  3. Check that FiniAC is properly loaded
  4. Try recording for a longer period

Best Practices ​

Recommendations

  • Record during peak hours to capture all commonly used entities
  • Keep a backup of your entity list
  • Record again if you add new resources that might spawn entities
  • Monitor detections after enabling to catch false positives
  • Use the Resource entity whitelist sparingly, as resources added here have broad entity spawning capabilities