General · Before you start

Getting support

What to check first, what to include when you get in touch, and where to reach me.

Setup questions get answered. Sending the right information first time is what makes that fast.

Before you get in touch

Most install problems are one of three things, and all three are quick to rule out:

  1. Start order. Does the resource ensure after ox_lib, oxmysql, your framework and your inventory? See Requirements.
  2. Items registered. If the resource uses items, are they in your inventory's item list, with the images copied across? Broken icons mean the images were missed.
  3. The boot log. Resources here print which framework, inventory, targeting resource, menu and phone they resolved to at start. If one of those is not what you expected, that is usually the whole problem.

Each resource also has its own troubleshooting page keyed to the exact error strings it can print — for example dd-cards troubleshooting.

What to include

The more of this you send up front, the fewer round trips:

  • The resource name and version (from its fxmanifest.lua).
  • The full console error, copied as text rather than a cropped screenshot.
  • The boot lines showing which framework and inventory were resolved.
  • Your framework and inventory, and which targeting resource, menu and phone you run.
  • What you changed in config/, if anything.
  • What you expected to happen, and what happened instead.

Tip

Server console text pastes fine into Discord. A screenshot of a console is much harder to read than the text it contains, and error messages are usually the fastest route to an answer.

Where to reach me

Discord is the fastest, and is best for back-and-forth debugging. Email is fine for anything that is not urgent. Both are linked in the footer of every page on this site.

What is in scope

In scope: installation, configuration, compatibility with supported frameworks and inventories, bugs, and anything the documentation gets wrong or leaves out.

Not in scope, but still worth asking about: custom modifications, integrations with resources that are not supported, and feature requests. I would rather hear these than not — a missing config option is often a fix rather than a feature. See Escrow & editing for what can be adapted yourself in the meantime.