Download MajestatTopCore

Installation#

1. Download MajestatTopCore.cs (button above). Do not rename the file — Oxide and Carbon require it to match the class name.
2. Upload it to oxide/plugins/ (Carbon: carbon/plugins/).
3. If files from earlier, separate versions are still there, delete them: MajestatStats.cs, MajestatTopBuild.cs, MajestatTopGather.cs, MajestatTopLoot.cs, MajestatTopWeb.cs, MajestatTopMap.cs, MajestatTopVote.cs, MajestatTopInfo.cs, MajestatTopNet.cs — otherwise tabs and commands get duplicated.
4. After the first start fill in MajestatTopCore.json — especially NET - Server ID if the server is already listed (see Connecting to the Majestat network below) — and reload the plugin (oxide.reload MajestatTopCore / c.reload MajestatTopCore).

Connecting to the Majestat network — server ID and token#

First check whether your server is already listed. Public Rust servers are discovered automatically (Steam master list, A2S queries), so your server most likely already has an entry on rustserverlist.online. On first start the plugin gives itself a random ID — left like that, the same server would show up twice: once as an A2S entry and once as a plugin entry. To send plugin data to the existing entry, give the plugin that entry's ID.

The server is already listed (most common)#

1. Find your server with the search on the server list and open its profile.

2. Claim it: the “Claim this server” button on the profile (code in the server name, code in the description, or an RCON login). Once claimed, the server is on your Steam account.

3. Copy the server ID: profile → Server settings → the “Server ID (NET - Server ID)” field with the Copy button. (It is also the id= value in the profile address.)

4. In oxide/config/MajestatTopCore.json (Carbon: carbon/configs/MajestatTopCore.json) set:

   "NET - Master Integration": true,
   "NET - Server ID (empty = auto)": "<ID copied from the profile>",
   "NET - Admin / Owner SteamID64": "<your SteamID64>",

5. Reload the plugin (oxide.reload MajestatTopCore / c.reload MajestatTopCore). The console shows [Net] Server ID set from config: … and shortly after Heartbeat [OK]. From now on the same entry receives plugin data — a chart sample every minute, online players, chat, joins and leaves.

Forgot the ID? Nothing breaks. If the plugin reports with a new random ID from the same IP:port as an existing entry, the network does not create a second entry — it sends a console warning instead: [Net] DUPLICATE: a server with this IP:port already exists in the network as ID '<id>'. To merge the entries, set "NET - Server ID (empty = auto)": "<id>" in the config and reload the plugin. Put that ID in the config and reload the plugin.

The server is not listed (private / new)#

Leave NET - Server ID empty and put your SteamID64 in NET - Admin / Owner SteamID64. The plugin registers the server with its first heartbeat and assigns it to your account. You will see the assigned ID in Server settings — it is worth writing it into the config permanently (it survives deleting the data folder).

Where to get the token (NET - Token)#

The token gives verification: the green ✓ badge, MASTER mode (XP rates from the network) and player stats in the global ranking. Without a token the plugin still works and reports the server (chart, players, chat), but in LOCAL mode.

1. First link the server to the right ID (steps above) — the token is bound to the entry's ID. With a different ID the network rejects it (401 bad token).
2. Go to My account → next to the server click “Request verification”.
3. Once the admins decide, the token arrives in Messages (My account).
4. Paste it into NET - Token, make sure NET - Master Integration is true, and reload the plugin. Console: [Net] Verification: VERIFIED and Mode: MASTER.

Already have two entries for the same server?#

Set NET - Server ID to the ID of the entry you want to keep (usually the claimed one, with history and comments), reload the plugin, and delete the other entry: its Server settings → Danger zone → Delete server.

Updating#

Replace MajestatTopCore.cs with the new file — Oxide and Carbon reload the plugin automatically. Your config and player data stay; new config keys are added on their own.

The SHA-256 checksum listed with every version lets you confirm the file arrived intact:

sha256sum MajestatTopCore.cs          # Linux
certutil -hashfile MajestatTopCore.cs SHA256   # Windows