> For the complete documentation index, see [llms.txt](https://ikcscripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ikcscripts.gitbook.io/docs/support/getting-help.md).

# 🆘 Getting Help

If you are having trouble with an iKCScripts resource, gathering the right information first can make troubleshooting much faster.

### Check the Documentation

Before requesting support, check the documentation for the resource you are using.

Pay particular attention to:

* Requirements
* Installation
* Configuration
* Troubleshooting

Make sure all required dependencies are installed, started in the correct order, and configured correctly.

### Information to Include

When requesting help, include:

* **Resource:** The iKCScripts resource you need help with
* **Framework:** Qbox, QBCore, ESX, standalone, or other
* **Inventory:** ox\_inventory, qb-inventory, ESX inventory, or other
* **Interaction:** ox\_lib, ox\_target, qb-target, or other
* **Server Error:** Complete server console error
* **Client Error:** Complete F8 error, if present
* **Steps:** What you were doing when the issue occurred

If there is no error, describe exactly what you expected to happen and what happened instead.

### Screenshots and Videos

Screenshots are useful for:

* UI problems
* Incorrect positioning
* Console errors
* Configuration issues

Short videos are especially useful for problems involving:

* Player interaction
* Animations
* Placement
* Synchronization
* Audio
* Issues that happen only during a sequence of actions

{% hint style="warning" %}
Never publicly share passwords, license keys, API secrets, database credentials, server tokens, or other private credentials when requesting support.
{% endhint %}

### Modified Resources

If you modified the resource before the problem appeared, mention what was changed.

This helps separate an installation issue from a problem introduced by custom modifications.