Discord

Troubleshooting

Troubleshooting

Common issues and solutions for the ATM Owner System.

Network & Performance Issues

Kicked for Reliable Overflow

Error Message:

Kicked for reliable overflow

Causes:

  • Too many network events on server restart

  • Large number of ATMs being synced simultaneously

  • Network congestion

Solutions:

  1. Ensure Latest Version:

    • Chunked/latent streaming is enabled by default in latest version

    • Update to latest script version if using older version

  2. Reduce Player Concurrency:

    • Stagger player joins on restart

    • Use player queue system if available

    • Reduce simultaneous coordinate requests

  3. Verify Chunked Streaming:

    • Check server console for chunked sync messages

    • Verify TriggerLatentClientEvent is being used

    • Check network statistics in console

  4. Optimize ATM Count:

    • Reduce total number of ATMs if possible

    • Use chunked import for bulk operations

    • Consider disabling blips if not needed

Prevention:

  • Script uses automatic queue system

  • Chunked streaming prevents overflow

  • Throttling limits request frequency

Reliable Network Event Overflow on Restart

Symptoms:

  • Players kicked on server restart

  • Network overflow errors in console

  • ATMs not loading for some players

Solutions:

  1. Chunked Streaming (Automatic):

    • Script uses chunked latent per-player streaming

    • Queue system prevents overflow

    • Verify you're on latest version

  2. Reduce Concurrency:

    • Limit simultaneous player joins

    • Stagger coordinate requests

    • Use player queue system

  3. Check Network Stats:

    • Monitor network statistics in console

    • Look for coords_requests and coords_chunks_sent counts

    • Verify chunked streaming is working

Configuration:

  • Chunk sizes automatically adjust based on ATM count

  • Queue processes one request at a time

  • Minimum 5-second interval between pushes

Permission & Entitlement Issues

"You Lack the Entitlements Required to Use"

Error Message:

Causes:

  • Wrong CFX account or organization

  • License key mismatch

  • Resource not properly purchased

Solutions:

1.1 Logging in with Wrong Account

Verify Account:

  1. Ensure server is running under correct CFX account

  2. Verify license key matches owning account

  3. Check Keymaster organization settings

Steps:

  1. Log into correct CFX account

  2. Verify resource ownership

  3. Update server license key if needed

  4. Restart FiveM server

1.2 Purchased but Cannot Use

Solutions:

  1. Restart Server:

    • Restart FiveM server after purchase

    • Allows Keymaster to validate product ID

    • Wait for validation to complete

  2. Check Asset Escrow:

    • Ensure resource folder name is unchanged

    • Verify fxmanifest.lua is intact

    • Check for file modifications

  3. Verify Purchase:

    • Confirm purchase in Keymaster

    • Check resource is assigned to correct account

    • Verify license key is correct

Map & UI Issues

ATM Blips Don't Show on Map

Symptoms:

  • No ATM blips visible on map

  • Blips not appearing after restart

  • Blips disappear randomly

Solutions:

  1. Check Configuration:

  2. Refresh Blips:

    • Run /toggleatmblips command

    • Toggles blips on/off to refresh

    • Wait for coordinate sync to complete

  3. Wait for Sync:

    • After server restart, wait 1-2 seconds

    • Chunked coordinate sync needs time

    • Blips appear after sync completes

  4. Verify ATMs Exist:

    • Check database for ATM records

    • Verify coordinates are valid

    • Check server console for errors

  5. Check Blip Settings:

UI Pin or Map Position Looks Off

Symptoms:

  • Map pins appear in wrong location

  • Pins don't show when hovering

  • Map offset is incorrect

Solutions:

  1. Pin Visibility:

    • Pins only appear when hovering card's info button

    • Hovering other areas won't show pins

    • This is by design

  2. Map Offsets:

    • Adjust in web/script.js:

    • Tune MAP_OFFSETS_* and MAP_GEOM_CORRECTION values

    • Adjust slightly if using different base image

  3. Debounced Map Init:

    • Map initialization is debounced

    • Prevents jitter after restarts

    • Give it 1-2 seconds to stabilize

  4. Base Image:

    • Verify you're using correct map base image

    • Different images require different offsets

    • Check MAP_ANCHOR_WORLD coordinates

Error Fetching Coordinates... Using Fallback

Error Message:

Causes:

  • ATM not in client cache yet

  • Coordinate sync not complete

  • Network delay

Solutions:

  1. Wait for Cache:

    • NUI first resolves from client caches

    • Fallback means ATM wasn't in cache yet

    • This is retried silently

  2. Avoid Rapid Clicks:

    • Don't click multiple cards immediately after restart

    • Wait for coordinate sync to complete

    • Give system time to cache coordinates

  3. Reopen UI:

    • Close and reopen management UI

    • Triggers coordinate refresh

    • Updates cache with latest data

  4. Refresh Blips:

    • Run /toggleatmblips to reinitialize

    • Forces coordinate cache update

    • Resolves most coordinate issues

Database Issues

Database Errors or Missing Tables

Error Messages:

Solutions:

  1. Import SQL File:

    • Import atm.sql to create required tables

    • Verify all tables were created:

      • owned_atms

      • atm_transactions

      • atm_employees

      • atm_admin_logs

      • atm_movements

      • atm_permissions

  2. Check Database Connection:

    • Verify oxmysql is running

    • Check database credentials

    • Test connection manually

  3. Verify Table Structure:

  4. Name Lookups:

    • QB uses players table

    • ESX uses users table

    • Missing tables fall back to raw identifiers

  5. Check Foreign Keys:

    • Verify foreign key constraints

    • Check CASCADE delete settings

    • Ensure indexes are created

Tax & Permission Issues

Cannot Change ATM Tax

Symptoms:

  • Tax slider doesn't work

  • "You don't have permission" error

  • Tax changes not saving

Solutions:

  1. Check Owner Status:

    • Only owner can change tax if Config.RequireOwnerForTax = true

    • Verify you're the ATM owner

    • Check database for owner field

  2. Check Configuration:

  3. Check Permissions:

    • If employee, verify manage_tax permission

    • Or manage permission (if AllowTaxChangeByManagers = true)

    • Check employee permissions in database

  4. Check Level Limits:

    • Tax rate limited by owner's level

    • Level 1: 0-10%

    • Level 5+: 0-39%

    • Verify you're within allowed range

  5. Check Logs:

    • Review admin logs for tax change attempts

    • Check for "tax_change_denied" entries

    • Verify level-based restrictions

Localization Issues

Localization Doesn't Load

Symptoms:

  • UI shows key names instead of translations

  • Language not changing

  • Missing translations

Solutions:

  1. Set Locale:

  2. Verify Locale File:

    • Check locales/en.lua exists (or your language)

    • Verify file is properly formatted

    • Check for syntax errors

  3. Check Locale Loader:

    • Verify locales/loader.lua includes your language

    • Check locale registration

    • Verify locale table structure

  4. Clear Cache:

    • Restart resource to reload locales

    • Clear browser cache if using web UI

    • Verify locale strings are loaded

  5. Check NUI Loading:

    • Verify getLocaleStrings callback works

    • Check browser console for errors

    • Verify locale strings are sent to NUI

Employee Management Issues

Employees Not Receiving Permissions

Symptoms:

  • Employee added but no permissions

  • Permissions not saving

  • Employee can't access features

Solutions:

  1. Verify Employee Added:

    • Check atm_employees table

    • Verify employee identifier is correct

    • Check employee record exists

  2. Check Permissions JSON:

    • Verify permissions field in database

    • Check JSON format is valid

    • Ensure permissions are set

  3. Refresh UI:

    • Close and reopen management UI

    • Triggers permission refresh

    • Updates employee list

  4. Check Permission Structure:

  5. Verify Server ID:

    • Ensure correct server ID was entered

    • Player must be online when added

    • Check identifier resolution

Revenue & Transaction Issues

Tax Not Being Collected

Symptoms:

  • No tax deducted from transactions

  • Revenue not increasing

  • Transactions not detected

Solutions:

  1. Check Auto-Detection:

  2. Check Proximity:

    • Player must be within Config.ProximityRadius

    • Default is 1.0 meters

    • Verify player is close enough to ATM

  3. Check Tax Rate:

    • ATM must have tax rate > 0

    • Verify tax is set in database

    • Check tax rate in management UI

  4. Check Transaction Type:

    • Only deposit/withdraw transactions are taxed

    • Transfers may not be detected

    • Verify transaction type

  5. Check Server Console:

    • Enable Config.Debug = true

    • Look for transaction processing messages

    • Check for errors

Revenue Not Updating

Symptoms:

  • Revenue balance not increasing

  • Withdrawals show incorrect balance

  • Revenue statistics not updating

Solutions:

  1. Refresh UI:

    • Close and reopen management UI

    • Triggers revenue refresh

    • Updates from database

  2. Check Database:

    • Verify revenue field in owned_atms table

    • Check atm_transactions for tax amounts

    • Verify transactions are being logged

  3. Check Permissions:

    • Verify you have access to view revenue

    • Owner or view_logs permission required

    • Check employee permissions

  4. Wait for Sync:

    • Revenue updates may take a moment

    • Allow time for database sync

    • Check again after a few seconds

Performance Issues

High Server Resource Usage

Symptoms:

  • High resmon usage

  • Server lag

  • Performance degradation

Solutions:

  1. Reduce Proximity Radius:

  2. Disable Auto-Detection:

  3. Disable Blips:

  4. Optimize Database:

    • Add indexes to frequently queried columns

    • Optimize SQL queries

    • Clean up old transaction logs

  5. Reduce ATM Count:

    • Limit total number of ATMs

    • Remove unused ATMs

    • Optimize coordinate sync

Client-Side Performance Issues

Symptoms:

  • UI lag

  • Slow map rendering

  • High FPS impact

Solutions:

  1. Reduce Blip Count:

    • Disable blips if not needed

    • Use short-range blips only

    • Limit visible ATMs

  2. Optimize Map Rendering:

    • Reduce map update frequency

    • Limit visible pins

    • Optimize coordinate calculations

  3. Check Browser Performance:

    • Clear browser cache

    • Disable browser extensions

    • Check for JavaScript errors

General Issues

Script Not Starting

Symptoms:

  • Resource fails to start

  • Errors in server console

  • Dependencies not loading

Solutions:

  1. Check Dependencies:

  2. Check File Structure:

    • Verify all files are present

    • Check fxmanifest.lua is correct

    • Verify folder structure

  3. Check Console Errors:

    • Review server console for specific errors

    • Check for missing files

    • Verify database connection

  4. Verify Framework:

    • Ensure framework is running

    • Check framework compatibility

    • Verify ic3d_lib detection

UI Not Opening

Symptoms:

  • Management UI doesn't open

  • NUI not responding

  • Blank screen

Solutions:

  1. Check NUI Files:

    • Verify web/ATM.html exists

    • Check web/script.js and web/style.css

    • Verify file permissions

  2. Check NUI Focus:

    • Verify SetNuiFocus is being called

    • Check for conflicting UI scripts

    • Ensure NUI is enabled

  3. Check Browser Console:

    • Open F8 console in-game

    • Look for JavaScript errors

    • Check for missing resources

  4. Verify ox_lib:

    • Ensure ox_lib is running

    • Check for version compatibility

    • Verify UI components work

Getting Help

Before Asking for Help

  1. Enable Debug Mode:

  2. Check Server Console:

    • Look for error messages

    • Note specific error text

    • Check for warnings

  3. Verify Configuration:

    • Review config.lua settings

    • Check for typos

    • Verify all required settings

  4. Test Basic Functionality:

    • Test with default settings

    • Verify dependencies work

    • Check database connection

Information to Provide

When reporting issues, provide:

  • Error messages from console

  • Steps to reproduce

  • Configuration file (sanitized)

  • Server framework and version

  • Script version

  • Debug output

Still having issues? Review the FAQ or check the Configuration Guide.

PreviousFAQ

Last updated