Migrating from v2

v3 is a rewrite. Radio audio runs on the zerio-voice server instead of pma-voice, the config moved from shared/ (Shared.*) to configs/ (Config.*), and channels are stored in the database.

Your database upgrades itself on the first start. Your config doesn’t: copy your values over using the tables on this page.

Before You Start

1. Back up your database. v3 changes the v2 tables in place on its first start.
2. Keep your old zerio-radio folder somewhere outside resources. You’ll copy values out of its shared/ folder.
3. Don’t copy any v2 files into v3. v3 doesn’t load shared/main.lua or the other v2 config files.

Upgrade Steps

Database

You don’t run any SQL by hand. On the first start v3 creates its new tables and upgrades the v2 ones:

The server console prints a [zerio-radio] Migrated … line for every change. Contacts, favorites and recent channels keep working.

Once you’ve checked everything works, you can drop the columns v3 no longer uses. This is optional:

ALTER TABLE zerio_radio_settings
  DROP COLUMN size, DROP COLUMN useMouse, DROP COLUMN allowDrag,
  DROP COLUMN positionX, DROP COLUMN positionY, DROP COLUMN position2X, DROP COLUMN position2Y;
ALTER TABLE zerio_radio_messages DROP COLUMN timestamp_v2;

Channels

In v3 you manage channels in the admin menu (/radioadmin), and they’re stored in the zerio_radio_channels table.

While zerio_radio_channels is empty, v3 imports every entry in Config.Channels on start: the label, the access rules (jobs, gangs, whitelisted, discordRoles, acePermissions) and noTalkOver. From then on, use the admin menu. Config.Channels is ignored as soon as the table has any channel in it, so you can empty the file, and a channel you delete in the admin menu doesn’t come back on restart.

Two things don’t come across:

• customCheck functions can’t be stored in the database. A channel that had one is imported locked, so nobody can join it until you set its access in the admin menu and unlock it. Use ACE permissions or a whitelist instead. The console prints a Locked channel … line for each one.
• Decimal frequencies such as [145.5] are skipped, because channel frequencies must be whole numbers. The console prints a Skipped Config.Channels[…] line for each one.

Config Options

Every v2 option, and where it is in v3. Default changed means the shipped value is different, so check it even if you never changed the v2 option.

shared/main.lua

shared/channels.lua

See Channels.

shared/framework.lua

This is now configs/framework.lua and works the same. Leave it alone.

shared/animation.lua

This is now configs/features/animation.lua. Shared.Animation becomes Config.Animation, with the same OpenProp, TalkProp, OpenAnimation and TalkAnimation fields, so you can copy your values straight over. New in v3: ClothingAnimations, which changes the talk animation based on clothing.

shared/opentype.lua

shared/scanner.lua

Shared.Scanner becomes Config.Scanner in configs/features/scanner.lua.

New in v3: FrequencyRange, BackgroundScan, LockOn and ScanSpeed.

New in v3

These have no v2 equivalent. The Configuration Guide explains each one.

• configs/admin.lua: who can open /radioadmin (the zerio.admin ace, or the QBCore/ESX admin group by default).
• configs/gameplay.lua: Config.MaxChannels, how many channels a player can be on at once (default 3), and the push-to-talk keys.
• configs/main.lua: Config.DefaultTheme and Config.DefaultSkin, with the themes in configs/themes.lua.
• configs/features/: towers, underground signal loss, weather, jammers, repeaters, battery, man-down, GPS, groups, speakers and more.