For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Troubleshooting

Common issues and fixes for rx-core.

"Framework: none. Inventory: none." on startup

[rx-core] Framework: none. Inventory: none.

rx-core couldn't detect your framework or inventory. Causes:

• Your framework resource isn't running. Verify ESX/QBCore/QBox/ox_core is ensured before rx-core in server.cfg.
• Your framework resource started but with errors. Check the console for framework startup errors.
• You're running a custom fork that uses non-standard exports. rx-core supports stock framework versions only.

If you're running Standalone intentionally, this message is expected. Money, jobs, and inventory features will warn when called.

"attempt to index nil value (global 'Core')"

A Rynex script started before rx-core finished loading. Causes:

• rx-core is ensured after the script in server.cfg. Fix the order — rx-core must come first.
• rx-core failed to start. Check the console for [rx-core] errors at startup.

"Core function is not available on standalone framework"

You're running Standalone, and a script called a function rx-core only implements on real frameworks (money, jobs, inventory). Either:

• Switch to a real framework (ESX/QBCore/QBox/ox_core), or
• Use a different script that doesn't depend on those features.

Wrong framework detected

If you have multiple frameworks installed simultaneously, rx-core picks the first one in this priority order:

1. ox_core
2. qbox
3. qbcore
4. esx
5. standalone (fallback)

This is rarely intentional. Remove the framework you don't use.

Update warning in console

[rx-core] Update available: v1.0.0 -> v1.0.1

rx-core checks GitHub for new releases on startup. To update, download the latest release and replace your rx-core folder, then restart.

Support

Discord: discord.gg/bFJ2v2wakz

---

Agent Instructions

This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the ask and goal query parameters:

GET https://docs.rynexscripts.com/rx-core/troubleshooting.md?ask=<question>&goal=<user_goal>

ask is the immediate question: it should be specific, self-contained, and written in natural language. goal is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with ask=how do I create an API token, a goal like automate deployments from our CI pipeline lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.