Reporting Issues

Good bug reports are faster to solve. If important information is missing, support first has to ask basic questions before the real debugging can start.

Before Reporting

Before opening a ticket, quickly check:

• The resource is installed correctly and starts in server.cfg.
• Required dependencies start before it.
• You are not using ensure [sky_scripts] for Sky-Systems resources.
• Recent config edits were checked for syntax mistakes.
• SQL was imported if the resource needs it.
• Old conflicting resources are stopped.
• You can reproduce the issue after a restart.

What We Need

Include this information in your report:

Resource:
Version:
Framework: ESX / QBCore / Qbox
Inventory:
Target:
SQL resource:
Server artifacts version:
OneSync enabled: yes/no

What happened:
What you expected:
Steps to reproduce:
Console errors:
F8 errors:
Relevant config changes:
Other resources involved:

Example Report

Resource: sky_ambulancejob
Version: 2.18.0
Framework: ESX
Inventory: ox_inventory
Target: ox_target
SQL resource: oxmysql
Server artifacts version: 12345
OneSync enabled: yes

What happened:
When a player crashes into a wall and is ejected by our seatbelt script, the deathscreen says Gunshot.

What you expected:
It should show a vehicle or unknown cause, not gunshot.

Steps to reproduce:
1. Enter a car.
2. Drive into a wall at high speed.
3. Seatbelt script ejects the player.
4. Deathscreen opens.

Console errors:
No server console errors.

F8 errors:
No F8 errors.

Relevant config changes:
VehicleImpactProtection is enabled. We use a custom seatbelt resource.

Other resources involved:
custom_seatbelt

Logs

Send the actual error text, not only "there is an error". For visual or UI bugs, add a screenshot or short video.

If the console shows many errors at once, include the first error after the resource restart. Later errors such as Locales nil, ToggleFeatures nil, or table expected, got nil are often follow-up errors from a broken config file.

Send the full startup log around the first error and mention what config file you edited before the issue started. For examples, see Common Console Errors.

What Not To Send

Avoid sending only this:

It does not work.
Fix pls.
There is an error.

We need enough context to reproduce or understand the issue.

Sensitive Data

Do not post database passwords, license keys, Tebex secret keys, Discord webhook URLs, or tokens in public channels. If support asks for sensitive data, send it only through the requested private channel.