Upgrading from Older Versions

Radial Menu 2.x replaces the 1.x builds and the early 2.0 ones. The resource name and the exports are the same, but the configuration moved into config/, the interface was rebuilt, and everything the in-game editor saves now lives in the database instead of JSON files inside the resource folder.

Mixing old and new files does not work: an old interface with the new scripts, or the reverse, opens an empty editor or no editor at all. Replace the whole folder, then copy your own edits back in.

What Moved#

Every file you were likely to edit has a new home:

In older builds

Upgrading from Older Versions — Radial Menu | Quasar Store | Quasar Store

Back up the old folder
Copy qs-radialmenu somewhere outside resources/. You need its config.lua, menu.lua, any edited clothing or locale file, and every .json file in it.
Replace the folder
Stop the server, delete the old qs-radialmenu and put the new one in its place. Keep the same name. Make sure ensure oxmysql comes before it in server.cfg — older builds did not need it.
Carry your edits over
Copy your settings into config/main.lua value by value, and your menu tree into config/menu.lua. Do not drop the old config.lua over the new one: 2.x adds Config.CloseKeys, Config.DevOpenEditor and Config.Clothing.
Start it once
Start the server. The first start creates the qs_radialmenu table. If you never used the old /radialedit, you are done.
Bring the editor data across
Each old JSON file becomes one row, with exactly the same contents. Paste each file's text between the quotes and run it against your database (HeidiSQL, phpMyAdmin or your host's panel); leave out the lines for files you do not have:
sql
```
INSERT INTO `qs_radialmenu` (`name`, `data`) VALUES
    ('menu_overrides',  '<contents of menu_overrides.json>'),
    ('custom_registry', '<contents of custom_registry.json>'),
    ('server_defaults', '<contents of server_defaults.json>')
ON DUPLICATE KEY UPDATE `data` = VALUES(`data`);
```
If a label contains an apostrophe, double it (''). Then restart the resource — the rows are read when it starts. Prefer not to touch SQL? Open /radialedit and rebuild instead; Import from menu.lua gets you most of the way.
Save the permissions once
Old server looks used two switches, allowPlayersChangeColorsShapes and allowPlayersReposition. The current version reads neither, so both read as allowed until you open /radialedit → Permissions, set the three switches and save.

Before	Now
1.3 and earlier: admins saved the server's look from the player settings panel	/radialedit → Appearance, with a live preview
1.3 and earlier: two permission switches	Three — appearance, size and position, custom shortcuts — in /radialedit → Permissions, enforced on every player
1.4 and early 2.0: editor data in JSON files next to the resource	The database — it survives replacing the folder on every future update
Items added to a category by its label	By ID only — see below

What Moved#

Upgrading from Older Versions

What Moved#

Upgrading Step by Step#

Back up the old folder

Replace the folder

Carry your edits over

Start it once

Bring the editor data across

Save the permissions once

What Changes for Your Staff and Players#

For developers#

Checking the Upgrade#