Troubleshooting
Check the installation requirements and dependency startup order first. Change one configuration option at a time and repeat the same test to confirm the result.
Resource does not start
- Install the complete supplied package under the resource name
f5_airdrop. - Start your framework, inventory, target and database driver before F5 Airdrop.
- Confirm that the selected configuration modes match the resources installed on your server.
- Check the server console for the first startup error.
See Installation for example startup sequences. Restore missing or modified protected files from the original package.
Database connection fails
Check that the database driver is running, its connection settings are correct and its account has the permissions required to prepare and save data. A manual SQL import is normally unnecessary.
If previously saved presets or calendar entries are affected, preserve a backup before attempting recovery. See Saving and Backups, or provide the error message to support.
Administrator panel is unavailable or actions fail
Check the staff permission selected by Config.CommandPermission and the ACE permissions listed in Commands and Permissions. An administrator role alone may not supply every required permission.
If an action times out, refresh the relevant list before repeating it. Check whether the drop, preset or calendar entry was created to avoid duplicates.
No helicopter appears
Direct container placement is expected when no player is near the destination. To test helicopter delivery, remain near the drop location before the dispatch countdown ends.
Check the configured player radius, model availability and game build. Use an open destination with sufficient clearance and compare the result with the supplied models and settings.
No automatic drops appear
Check whether automatic drops are enabled, the configured locations are valid and the minimum-player requirement is met. TimeBetweenAirdrops is measured in minutes; enabling the rotation does not immediately start a delivery.
Calendar entries run independently. See Drop Experience.
A drop disappears before players can loot it
Airdrop.lifetime includes flight and lock time. Increase it if delivery and the lock leave too little time for looting. Administrator removal and resource restarts also clear active drops.
A countdown does not match the expected arrival
The announcement countdown ends at dispatch or direct placement, not at helicopter landing. The lock countdown starts after the container lands or is placed.
If a world countdown is not visible, check its enabled state, height and display distance in Per-Drop Settings.
A flare or its sound ends earlier than expected
Review the flare and sound durations together. Removing a flare also ends its remaining sound, so the sound cannot continue beyond the flare's lifetime.
The container has no interaction
Wait for the lock to finish, approach the front doors and aim at the entrance. Check that the selected target resource is running and that Config.Target.system is not none.
If a custom target or container model is in use, test the supplied configuration first. Refer to Framework and Target Integration and Containers and Cargo.
The container opens but loot is unavailable
Confirm that the drop has configured items, the opening scene has finished and the installed inventory supports shared stashes. Native ESX inventory alone is insufficient. For QB installations, review QB inventory compatibility.
Test with one registered item, a 100% chance and a positive quantity. Verify that stash capacity is sufficient for the selected items.
Items or quantities differ from the configuration
Each item has its own chance and quantity range. A drop can therefore contain fewer items than its configured list, or no items if every chance roll fails. Reopening the container does not reroll its contents.
Check item names, quantities, stash capacity and inventory-specific item properties. Decorative cargo does not show the actual loot. See Items and Inventory.
Item search or images are unavailable
Check the selected inventory integration and Config.Inventory.imageUrl. The item list uses your inventory's catalog, not the items carried by the administrator.
Close and reopen the panel after changing the inventory setup. Missing pictures do not prevent entering an item's registered name manually. Custom inventories require a completed integration in the open bridge.
The opening animation is missing or fails
The default animation requires game build 3407 or newer. Changing the enforced build requires a server restart and player reconnection. Alternative models may need a later build or a compatible opening profile.
Check config/container_opening.lua and test the supplied model before troubleshooting custom models. See Containers and Cargo.
Decorative cargo is missing
Cargo requires a supported container interior and compatible decorative models. Check the model palette in config/container_cargo.lua and test a supplied container model. Changing the loot list does not change the decorative boxes.
An announcement is missing or overlaps another interface
Check Config.AnnouncementEnabled and the audience rules in config/announcement.lua. Test with a player who meets those rules when a new drop is created. Joining later does not replay an earlier announcement.
If another resource's interface overlaps the banner, provide screenshots and the names of the affected resources to support. Announcements can be disabled in the configuration when needed.
A calendar entry uses the wrong time or does not run
Use the server time and UTC offset displayed in the calendar. Check that the entry is enabled, its next occurrence is in the future and the minimum-player requirement will be met.
Missed events are not replayed after downtime. Check the entry's result and any database errors before rescheduling. See Calendar and Scheduling.
A scheduled drop still uses old preset settings
Calendar entries keep the drop settings selected when they are created. Editing the original preset does not update existing entries. Create a new entry from the updated preset to use the revised settings.
Recent actions or automatic-drop settings reset
This is expected after a resource restart. Presets and calendar entries remain saved, while active drops and recent action history are cleared. Automatic drops become enabled again.
Contact support
Provide the resource version, framework, inventory, target, database driver and game build, together with the relevant error message and steps to reproduce the issue. Include a screenshot when it helps show the problem. Remove passwords, license keys and other credentials from shared logs.
If support requests diagnostic logging, enable Config.Debug temporarily in the configuration and disable it after collecting the requested information.