Menu
HomeScriptsEscrowOpen SourceBundlesDocumentationFAQ
Join Discord
Currency
Rynex
HomeScriptsEscrowOpen SourceBundlesDocumentationFAQ
DISCORD
Rynex© 2026 Rynex. All Rights Reserved. We do not have affiliation with any real world brands.
ImpressumContactTerms of ServicePrivacy Policy
TebexThis website and its checkout process is owned & operated by Tebex Limited, who handle product fulfilment, billing support and refunds.
🎁Limited time offer— Use code RYNEX10 for discount at your first checkout.Shop now →
Rynex
  • Welcome to Rynex
rx-core
  • Welcome
  • Installation
  • API Reference
  • Troubleshooting

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.

Welcome to Rynex

Rynex is a small catalog of cross-framework FiveM scripts. Every script works on ESX, QBCore, QBox, ox_core, and Standalone — no forks, no separate purchases.

Installation

Every Rynex script installs the same way:

  1. Drop the resource into your server's resources/ folder
  2. Add ensure rx-core and ensure rx- to server.cfg
  3. Restart the server

Configuration lives in config.lua. Customization hooks live in the open/ folder. See each script's own docs for details.

Support

Discord: discord.gg/bFJ2v2wakz

Store: rynexscripts.com


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/welcome-to-rynex.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.

NextWelcome