Install, update and customise your theme package

What is in the package

A single resource folder per product. Buying both gives you two folders in one zip, plus an ORDER.txt with your reference.

Install on a server that does not run it yet

1. Unzip the package and drop the resource folder into your resources directory.
2. Add it to server.cfg. ox_lib goes before everything that uses it; ox_inventory goes after ox_lib and oxmysql.

   ensure ox_lib
   ensure oxmysql
   ensure ox_inventory

3. Restart the server. That is the whole install — the theme is already inside.

Drop the theme onto an ox_lib or ox_inventory you already run

Check your version first: run version ox_inventory in the server console, or open fxmanifest.lua and read the version line.

Same version as the package

1. Copy web/build/oxs/ from the package into your own <resource>/web/build/.
2. Replace web/build/index.html with the one from the package — it carries two extra tags and the theme attributes.
3. Add the theme lines to the files block of your fxmanifest.lua:

   files {
       'web/build/oxs/*.css',
       'web/build/oxs/*.js',
       'web/build/oxs/*.json',
       'web/build/oxs/fonts/**/*',
       'web/build/oxs/img/*',
       -- your existing entries stay
   }

   ox_lib already has web/build/**/*, so there you can skip this step.
4. restart ox_inventory (or ox_lib) and clear the client cache once if the old look sticks.

Different version

Use the package as the resource itself — it is the official release with the theme added — or open your project in the studio again once we have rebased the templates onto your version.

Changing the theme after you bought it

Everything lives in web/build/oxs/theme.json. Open it, change a value, restart the resource.

{
  "vars": {
    "--oxs-accent": "#e5e7eb",
    "--oxs-radius": "10px",
    "--oxs-slot-size": "92px"
  },
  "flags": { "density": "cozy", "icons": "fontawesome" },
  "brand": { "name": "Los Santos RP", "placement": "centre" }
}

The runtime reads this file when the interface loads, so you are not locked into the choices you made at checkout. Reopening the project in the studio and exporting again gives you a fresh package with a clean configuration.

Logo, banner, fonts and extra buttons

When Overextended ships a new version

The theme layer is deliberately separate from the resource, so an update is a rebase, not a rewrite.

1. We pull the new release and rebuild the base.
2. An automated check verifies that every selector the themes rely on still exists, and that the manifest covers every file in the package.
3. You export your saved project again and get the new version with your settings intact.

Troubleshooting