> For the complete documentation index, see [llms.txt](https://risk-scripts.gitbook.io/risk-scripts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://risk-scripts.gitbook.io/risk-scripts/scripts/editor/faq-troubleshooting.md).

# FAQ / Troubleshooting

* <mark style="color:yellow;">**Q:**</mark> <mark style="color:yellow;"></mark><mark style="color:yellow;">Console shows</mark> <mark style="color:red;">`@litz_radialmenu/client/bridge.lua:10: No such export getSharedObject in resource`</mark>\
  **A:** You have ESX-specific code in `bridge.lua`, but your server isn’t running a properly named/loaded **es\_extended**. Open `client/bridge.lua`, delete everything, paste the correct framework snippet from the [**Installation page**](/risk-scripts/scripts/editor/installation.md), save, and restart the resource.

* <mark style="color:yellow;">**Q:**</mark> *<mark style="color:yellow;">Some items don’t show up in the menu.</mark>*\ <mark style="color:red;">**A**</mark>**:** Check if they’re restricted by <mark style="color:red;">`jobs`</mark>. If you’re not in the correct job, you won’t see them. Also confirm there are no script errors in the console.<br>

* <mark style="color:yellow;">**Q:**</mark> *<mark style="color:yellow;">How do I add new categories/submenus?</mark>*\ <mark style="color:red;">**A**</mark>**:** In <mark style="color:red;">`items.lua`</mark>, simply add a new entry to the <mark style="color:red;">`Items`</mark> array. Give it a unique <mark style="color:red;">`label`</mark>, <mark style="color:red;">`icon`</mark>, and optionally a submenu<br>

* <mark style="color:yellow;">**Q:**</mark> *<mark style="color:yellow;">How do I execute custom commands?</mark>*\ <mark style="color:red;">**A**</mark>**:** In the <mark style="color:red;">`action`</mark> function, call <mark style="color:red;">`ExecuteCommand('yourCommand')`</mark> or run any other client code (e.g., <mark style="color:red;">`TriggerEvent()`</mark>, <mark style="color:red;">`print()`</mark>, etc.).<br>

* <mark style="color:yellow;">**Q:**</mark> *<mark style="color:yellow;">Can I change the default key from X to something else?</mark>*\ <mark style="color:red;">**A**</mark>**:** Yes—just update <mark style="color:red;">`Config.defaultMapper`</mark> in <mark style="color:red;">`config.lua`</mark>. You may also need to re-register the new key mapping in your script or via FiveM’s built-in keybinding system.<br>

* <mark style="color:orange;">**Q:**</mark> *<mark style="color:orange;">Will this script conflict with other radial menu resources?</mark>*\ <mark style="color:red;">**A**</mark>**:** Potentially. If you already have a resource that uses the same command or key mapping, you may need to change `Config.commandName` or `defaultMapper` to avoid overlap.

{% content-ref url="/spaces/raV0ahRHt9rGeSXy7pTb/pages/Oj5Vs4n50SIT0exZUrCu" %}
[Commands & Event Triggers](/risk-scripts/scripts/editor/commands-and-event-triggers.md)
{% endcontent-ref %}