Skip to content
New here? 10% off your first order
Getting started

From checkout to a running script.

7 short steps from paying to running, for any OOS script. Each step says where the scripts differ.

7 steps ESX, QBCore, Qbox or standalone
  1. Before you buy

    Check what your server needs.

    Every OOS script runs on a regular FXServer. Check these before you buy, then look up the script you want below.

    • FXServer with OneSyncOOS Ride, OOS Autocab and OOS Advanced Chat need OneSync turned on.
    • oxmysqlFor OOS Ride. It starts before OOS Ride, which creates its tables on the first start.
    • A CFX accountYou log in with it at checkout, and your scripts are delivered to it.
    • Your framework, or noneESX, QBCore and Qbox are supported. OOS Ride also runs standalone or through a custom framework bridge, and OOS Notify works standalone.

    OOS Ride

    Job
    Resource
    oos-ride
    Needs
    OneSync and oxmysql
    Runs on
    ESX, QBCore, Qbox or standalone
    Read the docs

    Not sure which framework you run? Your server.cfg starts it: look for es_extended, qb-core or qbx_core.

    Talking passengers in OOS Ride use your own API keys. You set them as convars in server.cfg. The OOS Ride docs list which keys and what each one is for.

  2. At checkout

    Buy with your CFX account.

    Checkout runs on Tebex and starts with a FiveM login, because Tebex delivers to the CFX account you log in with. Use the account your server is linked to: your licence works on every server linked to it.

    • Buying for someone else? On the OOS Advanced Chat, OOS Notify and bundle pages, tick "Buy it as a gift" and enter their CFX username. It goes to their CFX Portal.
    • 120+ payment methods through Tebex, including cards, PayPal and iDEAL.
    • Want all of them? The All Scripts bundle costs less than buying the scripts one by one.
    First order? Take 10% off at the Tebex checkout with this code. One use per CFX account.
    Browse scripts See the bundle
  3. After you pay

    Download from the CFX Portal.

    Your scripts land in your CFX Portal under Granted Assets, usually within a minute of paying. Download the latest version there. You can come back and download it again any time.

    CFX Portal Granted Assets Log in with the same CFX account you used at checkout.
    Open the CFX Portal

    Nothing there after a few minutes? Check that you logged in with the right CFX account at checkout, then open a ticket with your Tebex Order ID.

  4. On your server

    Add it to your server and start it.

    Unzip the download and put the folder in your server's resources folder. Keep its name: OOS Ride looks for OOS Autocab by its resource name.

    Then add one line per script to server.cfg. OOS scripts start after oxmysql and your framework. OOS Ride also starts after your voice resource, and after your phone if you use one.

    server.cfg
    1. # database, framework and voice first
    2. ensure oxmysql
    3. ensure qbx_core# or qb-core / es_extended
    4. ensure pma-voice# your voice resource
    5. # then the OOS scripts you own
    6. ensure oos-ride
    7. ensure oos-autocab
    8. ensure oos-chat
    9. ensure oos-notify

    Restart your server. With OOS Ride, run its self-test in the server console. It checks the database and your API keys, and reports anything to fix before your first ride.

    oos_ride selftest

    OOS Advanced Chat needs server build 7290 or newer. Update your server artifacts first if you run an older build.

  5. In-game

    Set it up in-game.

    Most settings live in in-game admin panels, so you and your staff change them on a running server. OOS Notify is the exception: it uses a config file.

    • OOS RideRides, fares, passengers and the app.
      /rideadmin Panel docs
    • OOS AutocabThe Auto Cab page in OOS Ride's panel: fleet, area, look and pricing.
      /rideadmin Setup docs
    • OOS Advanced ChatCustom commands and live moderation.
      /chatmanager Panel docs
    • OOS NotifySounds, timing, position and colours, in the oos-notify folder.
      config.lua Config docs

    The panels open for players with the right ACE permission or one of your framework's admin groups. To give your admin group OOS Ride's panel:

    add_ace group.admin oos.ride.admin allow

    OOS Advanced Chat checks the oos.chat.staff permission the same way.

    OOS Ride's config/ files are first-start defaults. They are copied into the database once. After that, change settings in /rideadmin.

  6. Later on

    Update when a new version is out.

    New versions show up in your CFX Portal, and we announce each one in our Discord. Updating is a clean swap of the folder.

    1. StopStop the resource or the server.
    2. ReplaceDelete the old folder and put the complete new folder in its place.
    3. ReapplyCopy your own edits back in, such as changes to config.lua.
    4. StartRun refresh, then ensure the resource.
    refreshensure oos-script

    Don't copy new files over the old folder. Mixed old and new files cause errors that are hard to trace. Settings you made in /rideadmin are stored in the database, so they survive the swap.

  7. Any time

    Get help when you're stuck.

    Open a ticket in our Discord with your framework and the errors from your server console. Most tickets get a reply within a few hours, and the AI assistant answers any time of day.

    Open a ticket Read the docs

    Bought a script? Paste your Tebex Order ID in #get-customer-role to get the Customer role. More on support

That's it

You're ready to roll.

Your scripts are in and running. Your players can take it from here.

Browse scripts Join the Discord