Skip to main content
  • Confirm the folder is named exactly fzd_actionwheel.
  • Confirm ensure fzd_actionwheel is in server.cfg.
  • Confirm the distributed web/dist directory was uploaded.
  • Check the server console and client F8 console for errors.
An empty Config.Actions produces an empty normal wheel. Add configured actions or start resources that register their actions. After restarting FzD Action Wheel, restart runtime integrations so they register again.
Check the exact resource name, start order and that the call is made from a client script. Add dependency 'fzd_actionwheel' when the wheel is required.
Confirm it is not a visual placeholder, verify the event/command exists, check F8 for errors and confirm the action is not disabled.
Select the correct framework, start it before FzD Action Wheel, use the exact internal job name and verify the minimum grade. Standalone mode has no job information.
Check Config.Inventory, resource start order, exact item names and required quantities. Player metadata conditions are not inventory-item metadata.
Definitions are snapshotted when a menu opens. Close and reopen after registering, removing or replacing definitions. Current-state conditions still refresh while the menu is open.
Every action and nested child needs a unique ID. Namespace IDs, for example my_garage:repair.
Check the Font Awesome Free Solid icon name. Pro, Brands and Regular icons are not bundled.
This is intentional. FzD Action Wheel only displays choices and dispatches events. Production purchase logic belongs in the shop resource and must be validated server-side.