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.

Installation

rx-core is a single resource. Drop it in, ensure it in server.cfg, and you're done.

Requirements

• A FiveM server
• One of: ESX, QBCore, QBox, ox_core (or run Standalone with limited features)
• oxmysql (for any Rynex script that touches the database)

Install steps

1. Download rx-core from your Tebex purchase or the latest release.

2. Extract the rx-core folder into your server's resources/ directory.

3. Open your server.cfg and add this line BEFORE any other Rynex script:

   ensure rx-core

4. Restart your server.

On startup, you should see this in the server console:

[rx-core] v1.0.0 loaded. Framework: . Inventory: .

If you see "none" for framework or inventory, see the Troubleshooting page.

Load order

rx-core must start BEFORE any Rynex script that depends on it. The recommended server.cfg order:

ensure oxmysql
ensure es_extended #(or your framework)
ensure ox_inventory #(if used)
ensure rx-core 
ensure rx-banking #(or any rx-* script) 
ensure rx-garage #(etc.)

Updating

When a new version is released:

1. Replace the rx-core folder in resources/.
2. Restart the server.

Configuration changes between versions will be noted in the release notes on GitHub. rx-core has no buyer-configurable settings — it auto-detects everything.

Uninstalling

Remove the ensure rx-core line from server.cfg and delete the rx-core folder. Any Rynex script still ensured will fail to start with a missing dependency error.

---

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/installation.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.