Troubleshooting

Common Issues and Solutions

Players Not Getting Kicked

Possible Causes:

1. Player is whitelisted

2. Timer not reaching kick threshold

3. Detection is resetting too frequently

Solutions:

• Check Config.Whitelist.Groups - player's job may be whitelisted

• Enable debug mode and check console output

• Verify timer values in config (use minutes, not seconds)

• Check if player is actually moving (enable debug to see coordinates)

Warnings Not Appearing

Possible Causes:

1. Notification function not working

2. Message format issue

3. Chat system not loaded

Solutions:

• Check SendNotification function in config.lua

• Verify chat resource is running

• Test notification function directly:

  SendNotification("Test message")

• Try alternative notification method (see Customization)

False Positives (Players Kicked While Active)

Possible Causes:

1. Movement threshold too high

2. Detection not recognizing certain activities

3. Players in certain situations (e.g., menu, phone)

Solutions:

• This is rare but can happen in edge cases

• Check debug logs to see what the system detected

• Consider adding custom detection in client/editable.lua

• Verify player wasn't actually AFK (may have moved slightly but not enough)

Whitelist Not Working

Possible Causes:

1. Framework not detected

2. Job name mismatch

3. Framework not started before this resource

Solutions:

• Verify framework is running: GetResourceState('es_extended') or GetResourceState('qb-core')

• Check exact job names - they're case-sensitive

• Ensure framework starts before this resource in server.cfg

• Enable debug mode to see whitelist check results

Resource Not Starting

Possible Causes:

1. Syntax error in config.lua

2. Missing files

3. Incorrect folder structure

Solutions:

• Check server console for errors

• Verify all files exist in correct locations

• Check fxmanifest.lua syntax

• Ensure ensure LuaBeans-afk is in server.cfg

Debug Mode

Enable debug mode for detailed troubleshooting:

Config.Debug = true

Debug Output Includes:

• Current AFK time for each player (every 30 seconds)

• Warning triggers

• Kick events with player ID

• Whitelist check results

Interpreting Debug Output:

[AFK Debug] Time since last movement: 5m 30s

• Shows player's current AFK time

[AFK] Warning sent. Time remaining: 1 minutes

• Warning was successfully sent to player

[AFK] Kicking player 15 for being AFK

• Player is being kicked from server

Getting Help

If you're still experiencing issues:

1. Check Logs: Enable debug mode and review console output

2. Verify Configuration: Double-check all config values

3. Test in Isolation: Start with default config, test basic functionality

4. Check Dependencies: Verify framework integration (if using)

5. Review Recent Changes: Check what was modified in editable files

Failing that, you can Join our Discord