Since 2MB of oxide.users.data is the equivalent to 50K unique users, there have been server owners who have 50MB or above worth of that with hundreds of thousands of users of which percentage of active players is expectedly low.

All of these users would be not only loaded in the memory, but also saved again and again with each server save (which was to ensure consistent permission data being stored). Migrating to SQL will no longer need the database to be saved on server save.

The migration process is as simple as running a command on the server.

The c.migrate_perms_sql command will:

1. Copy over all of your groups and group permissions associated
2. User info with their associated groups and permissions
3. Switching your server Permissions serialization setting to SQL without requiring a server restart or plugin reloads.

You can continue using the server as you normally would. Your permissions system is now fully switched to SQL.

You can also switch back to the Protobuf-based permissions database with c.migrate_perms_proto which works just the same way (it imports all users, groups and their perms into the in-memory Protobuf database straight from the SQL database).

We've also added a new module named AdminExtensions which is dedicated to give a configurable and first-hand chat command permission-based access to Carbon Admin Module features that you would normally need to click through.

Here are the following commands you can configure:

• /spectate: Will spectate a player (syntax: /spectate someplayer), requiring configurable permission adminextension.spectate for it to work
• /blind: Will blind/lock down a player (syntax: /blind someplayer), requiring configurable permission adminextension.blind for it to work
• /empower: Will maximize all positive stats on a player (syntax: /empower someplayer), requiring configurable permission adminextension.empower for it to work
• /cpm: Will send a private message to a specific player (syntax: /cpm someplayer message), requiring configurable permission adminextension.cpm for it to work
• /lock: Will lock up one or all of the inventory containers of a player (syntax: /lock someplayer [main|belt|wear|all] [0|1]), requiring configurable permission adminextension.lock for it to work
• /tpm: It's a toggle command which will teleport the player when they're placing a map marker to the marker position, requiring configurable permission adminextension.tpm for it to work

We've added a new configuration option in Carbon's config file under the SelfUpdating section called RedirectURI, designed for the self-updating process to use as Carbon's endpoint it will automatically update from. This could be ideally used to build and maintain your own Carbon build in-house.

  "Analytics": {
    "Enabled": true
  },
  "SelfUpdating": {
    "Enabled": false,
    "HookUpdates": true,
    "RedirectUri": "https://my.endpoint/carbon.tar.gz"
  },
  "Debugging": {
    "ScriptDebuggingOrigin": "",
    "HookLagSpikeThreshold": 1000
  },

With the exposing, polish and cleanup of some of our duplicated Admin Module code, we've also introduced a few new Carbon-only hooks plugins can use.

- OnCarbonBlinded (BasePlayer invoker, BasePlayer target)
- OnCarbonUnblinded (BasePlayer invoker, BasePlayer target)
- OnCarbonEmpowerPlayerStats (BasePlayer invoker, BasePlayer target)
- OnCarbonLockPlayerContainer (BasePlayer invoker, BasePlayer target, ItemContainer container, bool locked)
- OnCarbonPrivateMessage (BasePlayer invoker, BaesPlayer target, string message)
- OnCarbonSpectateStart (BasePlayer invoker, BaesPlayer target)
- OnCarbonSpectateEnd (BasePlayer invoker, BaesPlayer target)

ModerationTools has also been merged all within AdminExtensions as it makes the most sense, and it's better to keep it all contained.

- OnCarbonBanPlayer (BasePlayer invoker, BasePlayer target, string reason, long expiry)
- OnCarbonUnbanPlayer (BasePlayer invoker, BasePlayer target)
- OnCarbonKickPlayer (BasePlayer invoker, BasePlayer target, string reason)
- OnCarbonMutePlayer (BasePlayer invoker, BasePlayer target, bool wants reason, string reason)

We've addressed a short-lasting issue where the profiler would cause Out of Memory crashes on certain Ubuntu distros.