RustyMain's Wishlist

Sputnik is a server event that allows players to contest fallen sputnik satellite fragments that fall around the map. Players will need to battle their way past patrol helicopters, NPCs, turrets, and mines to gain access to loot locked behind keycards that require 'Space Cards,' which can be added to loot tables or sold in a shop! Alternatively, you can use standard keycards.
 

Overview
By default, there are five types of debris that can fall in any quantity and combination. The fragment can be guarded by a helicopter, NPCs, turrets, and mines. For each preset, you can configure the location and number of crates. A radiation zone can be created around the fragment. By default, there is a card reader in one of the locations that open a locked crate. It is activated using the "Space card.” For more information, see the "Space card” section.
 
Space Card
A card reader can be placed on any type of sputnik debris. By default, it is activated using a purple "Space Card." This card reader opens the crates specified in a special section of the config. A custom card can be added to the loot tables of standard crates and crates of this event. It can also be given with the help of a command or sold in the server store. If necessary, the card reader can be removed, and the card can be replaced with any type of standard card.
 
Location presets
The location preset is specified for each wreckage preset separately. By default, a data file with five types of prefabs is included:
sputnik_1 debris_1 debris_2 debris_3 debris_4 They are shown in pictures 6 - 10.  The first location includes a locked crate that opens with the help of a "Space Map."
 
Chat commands (only for administrators)
/sputnikstart– launches the event in a random configuration /sputnikstart <eventPresetName> –   launches the event in the <eventPresetName> configuration /sputnikstop – stops the event /givespacecard – give yourself a "Space Card".  
Console commands (RCON only)
sputnikstart– launches the event in a random configuration sputnikstart <eventPresetName> –   launches the event in the <eventPresetName> configuration givespacecard <userID> – give a "Space Card" to player  
Config
en  –  example of plugin configuration in English ru  –  example of plugin configuration in Russian  
Dependencies (optional, not required)
True PVE PveMode GUI Announcements Notify DiscordMessages AlphaLoot CustomLoot Economics Server Rewards IQEconomic  
Hooks
OnSputnikEventStart () OnSputnikEventStop () OnSputnikEventWin (ulong userID) OnPlayerEnterSputnik{BasePlayer player} OnPlayerExitSputnik{BasePlayer player}  
My  Discord:  Adem#9554
Join the Mad Mappers Discord  here!
Check out more of my work  here!

DiscordRaidAlarm is a fully vanilla-friendly Rust plugin and Discord integration that alerts defenders when their base is under attack. It does not rely on Rust+ or any external "seismic sensors.” By detecting building damage in a standard Rust server (Oxide/uMod or Carbon), the system sends raid data to a PHP script with a MySQL database, and a Discord bot delivers real-time notifications to defenders via direct messages. You can either host your own single-tenant bot or register with our public multi-tenant bot (no hosting required). Once Steam-to-Discord mapping is in place, your players receive automated alerts about raids, even on completely vanilla Rust servers.If you need help configuring it, message me on Discord: CrypticRedhat.
 
1. Overview
DiscordRaidAlarm  notifies Rust players on Discord if their base is under attack. Its core components:
Rust Plugin: Captures damage events and posts them to a PHP script. PHP Script + MySQL: Stores raid data in a  raid_events  table. Discord Bot: Reads the table and DMs defenders. You can either use:
Our Public Multi-Tenant Bot  (simplest; no hosting required), or A Self-Hosted Single-Tenant  .exe  (full control, optional). This guide focuses first on the public multi-tenant bot approach—especially how to  invite  the bot and use  
/registertenant.
2. Prerequisites
Rust Server  supporting  Oxide/uMod  or  Carbon. A  web host  or cPanel environment for  PHP + MySQL. A  MySQL  database (username, password, DB name, etc.). Token  generated from  it-tools.tech/token-generator  (used across plugin & PHP script, and you’ll provide it to the multi-tenant bot). If you choose to self-host your own bot:  A  Windows  machine and optionally a  Discord Developer Portal  application for a custom bot token.  
3. Token Generation & Matching
Go to  it-tools.tech/token-generator  → click generate. Use  that random string for: Rust plugin config  (API Auth Token), PHP script  (API_TOKEN), And you’ll also provide it to the multi-tenant bot in  /registertenant  or your self-hosted bot config. All must match exactly or you’ll see 401/403 errors.
 
4. Rust Plugin Setup (Oxide/uMod or Carbon)
Obtain  DiscordRaidAlarm.cs. Place  in your Rust server’s plugin folder: Oxide:  oxide/plugins/ Carbon:  Carbon/Plugins/         3. Load  the plugin:
Oxide:  oxide.reload DiscordRaidAlarm  or restart. Carbon:  c.reload DiscordRaidAlarm.         4. Config:
Check  oxide/config/DiscordRaidAlarm.json  or similar. Set  "API URL"  to your  DiscordRaidAlarm.php  location, e.g. https://yourdomain.com/DiscordRaidAlarm.php. Set  "API Auth Token"  to the same token from Step 3. Verify  no errors. Run  oxide.plugins  or  carbon.plugins  to confirm it’s loaded.
 
5. PHP API Setup
Upload  DiscordRaidAlarm.php  to your web host. Edit  lines like: define('DB_HOST', 'localhost'); define('DB_NAME', 'my_database'); define('DB_USER', 'my_db_user'); define('DB_PASS', 'my_db_pass'); define('API_TOKEN', 'YOUR_RANDOM_TOKEN'); Make sure  API_TOKEN  matches your plugin.
Ensure  you can reach  DiscordRaidAlarm.php  in a browser (it may show an error, that’s normal with no parameters).
 
6. Database Creation
Create  a MySQL DB or use an existing one. Import  create_table.sql: mysql -u my_db_user -p my_database < create_table.sql         3. Check  for  raid_events:
SHOW TABLES; If it’s there, you’re set.
 
7. Using the Public Multi-Tenant Bot
If you don’t want to host a  .exe, our  public multi-tenant  Discord bot can poll your  raid_events  for you. Below are the  two  main steps: inviting the bot, then registering your tenant via the  /registertenant  slash command.
7.1 Invite the Bot to Your Server
Click  this invite link: Invite
It’s pre-configured with minimal but necessary permissions, including  Send Messages  (crucial for DM or channel posting) and other relevant scopes.
Select  your Discord server and authorize it. The bot will now appear in your server’s member list. If it can’t send messages or you want slash commands to work, ensure it has the right role/permission in the server. Typically "Send Messages,” "Embed Links,” "Read Messages History,” and "Use Application Commands” are enough. 7.2 Register Your Tenant with  /registertenant
Open  a text channel (or any channel)  in the same server  where you invited the bot. Type  /registertenant. You’ll see a form for:  
api_url   (required) – The URL to your  DiscordRaidAlarm.php.
 
api_token   (required) – The same token from your plugin +  DiscordRaidAlarm.php.
 
steamlink_url   (required) – If you’re using a steam-to-discord link system.  
 
steamlink_secret   (required) – Also for your steam link system.  
 
bypass_token   (optional) – For some advanced steam link usage.
 
poll_interval   (optional) – How often the bot checks your raids, in seconds. Defaults to the global fallback if omitted.
 
Fill  out each field carefully:
api_url: e.g., https://yourdomain.com/DiscordRaidAlarm.php api_token: your random token. steamlink_url  /  steamlink_secret: If you do not have a steam linking system, just enter placeholders. (Optional)  bypass_token  or  poll_interval  if needed. Press Enter. The bot will respond ephemerally with either  "Tenant registered/updated successfully!”  or an error message if something went wrong.
If successful, the bot automatically logs your server info (guild_id  + config) in its multi-tenant DB.
From this point on, the bot polls your  raid_events  table.
Done! Whenever your plugin logs a raid, the bot sees it and DMs the defenders (assuming you have steam-to-discord mapping set up).
Important: You  must  run  /registertenant  from  within  the server that the bot is invited to. The bot automatically captures your  guild_id  from the slash command, linking that guild to the  api_url  +  api_token  you provided.
 
8. Self-Hosted Bot (Optional)
If you prefer hosting your own single-tenant  .exe, skip Section 7 and do this:
Create a Discord bot  in the Developer Portal. Invite  it with permissions like Send Messages, etc. Edit  appsettings.json  or  .config: { "BotSettings": { "BotToken": "YOUR_BOT_TOKEN", "RaidApiUrl": "https://yourdomain.com/DiscordRaidAlarm.php", "RaidApiToken": "YOUR_RANDOM_TOKEN", "PollIntervalSeconds": "10" } } Run  DiscordRaidAlarmBot.exe. It polls your  raid_events  table, DMs defenders.  
9. Testing & Verification
Trigger  a test from your Rust server plugin if it supports a test command (like  /raidalarm.test). Otherwise, damage a building block. Check  your MySQL  raid_events  table: SELECT * FROM raid_events; If a new row is added with  processed=0, the bot should see it next poll cycle (every 10–30 seconds or your chosen interval). The bot (public multi-tenant or your own) sends direct messages to any defenders with known Discord IDs. If you see "Tenant registered/updated successfully!” from  /registertenant  but no raids are processed, check  Troubleshooting.  
10. Troubleshooting
No DMs: Possibly defenders’ privacy settings block DMs from that server’s members. The user might not be in the same Discord server. Steam ID → Discord ID mapping is missing if you rely on external link systems. "Tenant registration failed”  or 403/401 messages: Mismatched  api_token  between the Rust plugin, the  DiscordRaidAlarm.php, or the data you entered in  /registertenant. Typo in the  api_url  or server didn’t load the plugin. Bot Not Sending: For the public multi-tenant bot, confirm you typed  /registertenant  in the correct server, and it responded with success. For your self-hosted bot, ensure the  .exe  is running, the token is valid, and it’s in your server with  Send Messages  permission. Plugin Not Logging: Check the console logs for  DiscordRaidAlarm.cs  loading errors. Possibly it’s in the wrong folder for Oxide/Carbon, or you didn’t set "API Auth Token” in the plugin config.

The Cargo Convoy plugin creates a Cargo Ship with three different levels of defensive escorts.  In addition to this, the Cargo ship is equipped with a samsite, an autoturret, and a raidable door. If any of the escort ship's captains dies, that ship will stop. If the someone kills the Cargo ship's captain, the Cargo will stop, and if the PveMode plugin is enabled, they will become the owner of the event.
Supports the PveMode plugin.
Console Commands:
ccstart (random difficult event started)
ccstart.easy
ccstart.medium
ccstart.hard
ccstop
Contact:
Discord: https://discord.gg/C5CehdJMdK
Test Rust server: 213.181.206.21:27194  
Video:
Config:
{ "Plugin version": { "Major": 1, "Minor": 0, "Patch": 0 }, "Automatic event start": true, "Minimum time for event start": 3600.0, "Maximum time for event start": 7200.0, "Duration of the event": 3600.0, "Warning messages before event start": 300.0, "Warning messages before event end": 300.0, "Facepunch cargoship event enabled?": false, "Chat icon": 0, "Event Locked crates hack time": 900.0, "Autoturret setting Easy difficult": { "Health": 200.0, "Weapon ShortName": "smg.2", "Ammo ShortName": "ammo.pistol", "Number of ammo": 5000 }, "Autoturret setting Medium difficult": { "Health": 300.0, "Weapon ShortName": "rifle.lr300", "Ammo ShortName": "ammo.rifle", "Number of ammo": 5000 }, "Autoturret setting Hard difficult": { "Health": 400.0, "Weapon ShortName": "rifle.ak", "Ammo ShortName": "ammo.rifle", "Number of ammo": 5000 }, "Medium difficult door setting.": { "Door SkinID (0 - default, TugBoat and Medium difficult only use Sheet Metal Door skinID, Hard difficult only use Armored Door skinID! )": 1443957299, "Door Health": 250.0 }, "Hard difficult door setting.": { "Door SkinID (0 - default, TugBoat and Medium difficult only use Sheet Metal Door skinID, Hard difficult only use Armored Door skinID! )": 1130245250, "Door Health": 1000.0 }, "TugBoat door setting.": { "Door SkinID (0 - default, TugBoat and Medium difficult only use Sheet Metal Door skinID, Hard difficult only use Armored Door skinID! )": 1447958101, "Door Health": 250.0 }, "Elit crates setting on Easy difficult": { "Delete the Rust loottable loot?": false, "Add custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Elit crates setting on Medium difficult": { "Delete the Rust loottable loot?": false, "Add custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Locked crates setting on Medium difficult": { "Delete the Rust loottable loot?": false, "Add custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Elit crates setting on Hard difficult": { "Delete the Rust loottable loot?": false, "Add custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Locked crates setting on Hard difficult": { "Delete the Rust loottable loot?": false, "Add custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Elit crates setting on TugBoats": { "Delete the Rust loottable loot?": false, "Use custom loot?": false, "CustomLoot": { "Minimum items": 1, "Maximum items": 1, "Use minimum - maxium?": false, "List of items": [ { "ShortName": "xmas.present.small", "Minimum": 3, "Maximum": 6, "Chance": 100.0, "Give blueprint?": false, "SkinID": 0, "Displayname": "" } ] } }, "Setting the Captains": { "Name": "Captain", "Health": 300.0, "Attack Range Multiplier": 1.0, "Target Memory Duration [sec.]": 20.0, "Scale damage": 0.7, "Aim Cone Scale": 1.5, "Sense Range": 0.0, "Wear items": [ { "ShortName": "shoes.boots", "SkinID (0 - default)": 2454376365 }, { "ShortName": "burlap.trousers", "SkinID (0 - default)": 3027295270 }, { "ShortName": "burlap.shirt", "SkinID (0 - default)": 3027301658 }, { "ShortName": "burlap.gloves", "SkinID (0 - default)": 2454377972 }, { "ShortName": "hat.boonie", "SkinID (0 - default)": 3112171056 } ], "Belt items": [ { "ShortName": "syringe.medical", "Amount": 3, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" } ] }, "Setting the EASY Npc's": { "Name": "Cargo Soldier", "Health": 125.0, "Attack Range Multiplier": 4.0, "Target Memory Duration [sec.]": 20.0, "Scale damage": 0.7, "Aim Cone Scale": 1.5, "Sense Range": 150.0, "Wear items": [ { "ShortName": "shoes.boots", "SkinID (0 - default)": 800967386 }, { "ShortName": "pants", "SkinID (0 - default)": 681804489 }, { "ShortName": "hoodie", "SkinID (0 - default)": 963496340 }, { "ShortName": "burlap.gloves", "SkinID (0 - default)": 0 }, { "ShortName": "wood.armor.pants", "SkinID (0 - default)": 0 }, { "ShortName": "wood.armor.jacket", "SkinID (0 - default)": 0 }, { "ShortName": "bucket.helmet", "SkinID (0 - default)": 2929522461 } ], "Belt items": [ { "ShortName": "smg.thompson", "Amount": 1, "SkinID (0 - default)": 0, "Mods": [ "weapon.mod.flashlight", "weapon.mod.holosight" ], "Ammo": "" }, { "ShortName": "pistol.m92", "Amount": 1, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" }, { "ShortName": "syringe.medical", "Amount": 3, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" } ] }, "Setting the MEDIUM Npc's": { "Name": "Cargo Soldier", "Health": 200.0, "Attack Range Multiplier": 4.0, "Target Memory Duration [sec.]": 20.0, "Scale damage": 0.7, "Aim Cone Scale": 1.5, "Sense Range": 150.0, "Wear items": [ { "ShortName": "shoes.boots", "SkinID (0 - default)": 3251246600 }, { "ShortName": "pants", "SkinID (0 - default)": 3246192739 }, { "ShortName": "hoodie", "SkinID (0 - default)": 3246191692 }, { "ShortName": "burlap.gloves", "SkinID (0 - default)": 0 }, { "ShortName": "roadsign.kilt", "SkinID (0 - default)": 3260691772 }, { "ShortName": "roadsign.jacket", "SkinID (0 - default)": 3260693328 }, { "ShortName": "coffeecan.helmet", "SkinID (0 - default)": 3260694842 } ], "Belt items": [ { "ShortName": "smg.mp5", "Amount": 1, "SkinID (0 - default)": 0, "Mods": [ "weapon.mod.flashlight", "weapon.mod.holosight" ], "Ammo": "" }, { "ShortName": "syringe.medical", "Amount": 3, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" } ] }, "Setting the HARD Npc's": { "Name": "Cargo Soldier", "Health": 350.0, "Attack Range Multiplier": 4.0, "Target Memory Duration [sec.]": 20.0, "Scale damage": 0.7, "Aim Cone Scale": 1.5, "Sense Range": 180.0, "Wear items": [ { "ShortName": "shoes.boots", "SkinID (0 - default)": 2936561559 }, { "ShortName": "pants", "SkinID (0 - default)": 2933205831 }, { "ShortName": "hoodie", "SkinID (0 - default)": 2933205232 }, { "ShortName": "burlap.gloves", "SkinID (0 - default)": 2936561057 }, { "ShortName": "roadsign.kilt", "SkinID (0 - default)": 1624102935 }, { "ShortName": "metal.plate.torso", "SkinID (0 - default)": 2601631390 }, { "ShortName": "metal.facemask", "SkinID (0 - default)": 2601630796 } ], "Belt items": [ { "ShortName": "rifle.lr300", "Amount": 1, "SkinID (0 - default)": 0, "Mods": [ "weapon.mod.flashlight", "weapon.mod.holosight" ], "Ammo": "" }, { "ShortName": "rocket.launcher", "Amount": 1, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" }, { "ShortName": "syringe.medical", "Amount": 3, "SkinID (0 - default)": 0, "Mods": [], "Ammo": "" } ] }, "NPC Turret Damage Multiplier": 1.0, "Messages setting": { "GameTip message": "Cargo Convoy Inbound", "Message before the event starts.": "<color=#ff0000>Cargo Convoy</color> will start soon", "Message before the event stop.": "Cargo Convoy will end soon!!", "Message when someone stopped Cargo Convoy": "Someone stopped the Cargo Convoy", "Start message": "Cargo Convoy Event start! Kill the <color=#2296ff>Cargo Captain</color> to stop the cargo convoy and you will be the event owner", "Stop message": "Cargo Convoy Event end!", "Map marker name": "Cargo Convoy", "Map marker radius": 0.6, "Color": { "r": 1.0, "g": 0.0, "b": 0.0 } }, "PVE Mode Setting (only for users PveMode plugin)": { "Use PveMode plugin?": false, "Non owner can loot the crates?": false, "Non owner can loot the Npc's?": false, "Non owner can damage Npc's?": false, "Non owner can be attacked by Npc's?": false, "Non owner, can you enter the event zone?": false, "Allow a player who has an active cooldown of the Event Owner to enter the event zone?": true, "The time that the Event Owner may not be inside the event zone.": 300, "The time until the event owner can return to the event zone.": 60, "Block the RestoreUponDeath plugin in the event zone.": true, "After all this time, an event owner can be an event owner again.": 86400.0, "Darkening the sphere.": 15 } }  

Loadout controller is made to assist in allowing your Battlefield or even PVE community to thrive with customizable loadouts.

FEATURES
- Supports infinite permission groups - Easy UI system to modify permission groups - PERMISSION GROUP OPTIONS: - Item saving amount per item - Item saving amount per category (Weapons, attire, etc*) - Blacklisted ammo types loaded in weapons - Blacklied skin ID's - Priority settings - Max saves per permission - ETC* - Plyers can easily save their loadouts through the UI or chat commands. - The UI shows players exactly what items they can save, can't save, or can only save part of. - You can easily delete, override, select, or save new loadouts through the UI. - You can see what items are in your currently selected loadout in the UI - Loadouts automatically apply when a player respawns - Extremely performant UI system  
 
 

The radial menu is a customizable quick access panel with all popular and frequently used server commands. It makes it a lot easier and faster to interact with various server mechanics, be it teleportation, trades, setting house points and various panels.
 
Features
Allows to almost completely eliminate the manual entry of commands by the player. Automatic calculation and arrangement of any number of sections/subsections on a circle. Several display effects. Tracks a press of the MMB or on command (can be keyed to the same MMB). Checks for the privileges of a particular command, before executing it. Ability to use your own panel images. Full customization of the location and scale of icons and panel. Support for popular plugins (NTeleportation,  TeleportGUI, Clans, Friends and Rust teams). Executing console or chat commands.  
General settings
Track MMB presses to open a radial menu?  - if the player has a MMB bind, the plugin will not open the Radial Menu.
The command to open the radial menu  -  you can use both the command and the MMB tracking. When using MMB tracking and the command at the same time: If a player has a MMB bind, his bind will be executed when he clicks on it, and the Radial Menu will not open. If there is no bind, the player can use both the command and the MMB press.
Upload images to players when they connect?  - when a player connects to the server, the plugin will automatically download 3 images of menu rings to his client. This avoids displaying black rectangles when opening the menu while the plugin is downloading the images to the client.
Section/Subsection settings
The plugin has main sections (level 1), subsections at level 1 (level 2) and subsections at level 2 (level 3).
Section name - the name of the section, which is displayed under the icon.
Enable this section? – on/off section.
Section permission [required] - permission required for the plugin to work (without dots).  Add "_add" to the end of the name so that the plugin does not register or check permissions for child subsections.
Section icon - direct link to the icon (recommended size 64x64).
Fill icon with color below? -  Completely fills the icon with the color set below.
Inactive/active section color  [HEX or Unity RGBA] - The plugin supports 2 types of colors: HEX (e.g. "#57de54" or "#57de54ff") and  Unity RGBA ("0.34 0.87 0.33 1").
Command executed on behalf of the player - if you do not have subsections in this section, the command (without the "/" if chat) that will be executed for that player is specified here. You can specify multiple commands using commas (e.g. "radar ui, vanish, adminpanel hide"). If there are subsections in this section, the command is not specified.  Specify %steamid% or %username% so that the plugin replaces them with the data of the player on whose behalf the command is executed.  
Command type  - Where to run this command: true - chat, false - console.
Permissions for above command - if the command above is specified, you can specify the privileges of that command in this field (e.g. "removertool.normal, removertool.structure, removertool.external"). The plugin will check if the player has these privileges before executing the command.
Show this section only to those with permissions above?  -  allows to draw the section automatically (without giving permissions to this plugin) if the player has command permissions.
Show this section even to those who don't have permissions? - forcibly displays the section to all players, even those who do not have privileges to it (if you click on it, a message about lack of permissions will be displayed in chat).
Subsections layout [n - number] - this setting is responsible for how subsections are arranged.
0 - automatically. Suppose you have 10 subsections, then 360 degrees / 10 subsections = 36 degrees. The plugin will automatically position the 10 subsections every 36 degrees (clockwise, starting from the top). n - from the beginning. The plugin will arrange the subsections clockwise, starting from the top, not automatically, but in a certain step. For example, you have 3 subsections, but you do not want them to be automatically scattered all around the circle, you want them to be displayed at the top, with some small step, this step will be calculated due to the conditional number of subsections n (for example, 15). Now 360 degrees / 15 conditional subsections = 24 degrees, then your 3 subsections will be positioned from the beginning and there will be 24 degrees between them. -n - from the active item. The plugin will arrange the subsections relative to the active section. For example, you have 3 subsections, but you don't want them to be automatically scattered all around the circle, and you also don't want them to be arranged in some clockwise, starting from the top. By choosing this type of arrangement, the subsections will be located in the same place as the active section, in the increments you specify. It works the same way as above, only n is specified with a minus sign (for example, -15, the minus is needed for the plugin to understand what type of arrangement to use). All examples of the layout of the subsections are present in the standard config.
 
Permissions
It may be unclear how permissions work in this plugin. Let's figure it out with a simple example from the standard config.

It's not hard to figure out that this is the home point section of the standard config. To exclude identical names of permissions the plugin converts them to this form.
Because of the large number of permissions generated by the plugin, there are mechanics for reducing them. If you add "_all" to any section, in the "permission" field, the plugin will not register the permissions of child subsections. For example, if the player has the permission "_homes_all", then all displayed houses, all commands (add, remove, etc.), in general everything that belongs to the section "_homes_all" will obey and is checked by the permission "radialmenu._homes_all".  The "permission" fields of the child sections still have to be filled in for the plugin to work.
I strongly recommend using the "Permissions Manager" plugin to set privileges for players or groups. It draws a simple interface, through which it is very easy to add or remove permissions.
 
Teleportation
The plugin supports work with teleportation plugins (set/remove/teleport to home point) NTeleportation,  TeleportGUI and Teleportation by OxideBro (for RU server owners).
To do this, in the main section (level 1), you must specify the permission of the "_homes" section, this is necessary for the plugin to understand that it will work with the teleport plugin.
Next, in the subsection "_homes" (level 2) you must add the MAXIMUM number of displayed house points, for example 5. If the player has more house points than this number, then only the first 5 will be displayed, if less, then all of them will be displayed. For each such point, you must set its unique name, which begins with "home_n", where "n" is any unique number or word (e.g. home_1, home_2, etc.). In addition to the house points here you can place a section with the establishment of the house point, its name should be "home_add", and the command "home add {0}" (command your plugin teleport), where {0} - the name of the new house point, the plugin itself will set it relative to the square in which the player at the moment is (for example D3, if there are several in the square, then D3h1, D3h2, etc.).
After that, in the subsections (level 3) of each such house point, you can specify commands relating specifically to it. For example: "home {0}", "home remove {0}" or any other commands, where {0} is the name of the specific house, the plugin itself will substitute it when executing the command.
If you find all of the above complicated, you can take a look at the standard config as an example.
 
Friends
The plugin supports work with plugins Friends, Clans by k1lly0u and Rust teams.
Here everything is set up similar to Teleportation. But for the plugin to understand what to work with, in the main section (level 1) you must specify one of the three options:
"_teammates" - the plugin will work with Rust teams "_friends" - the plugin will work with the Friends plugin "_clans" - the plugin will work with the Clans plugin In subsections (level 2) you must add the MAXIMUM number of displayed friends, for example 8. If the player has more friends than this number, then only the first 8 will be displayed, if less, then all of them will be displayed. For each friend you must set its unique name, which begins with "friend_n", where "n" is any unique number or word (for example friend_1, friend_2, etc.).
After that, in the subsections (level 3) of each friend you can specify commands specific to him. For example: "tpr {0}", "trade {0}" or any other commands, where {0} is the nickname of the player, the plugin itself will substitute it when executing the command.
An example of the configuration of this section is also present in the standard config.
 
Plugin Config
Example of plugin configuration in English
Example of plugin configuration in Russian.  If you need Russian config, open it (RadialMenu.cs) before loading the plugin, and at the top set the variable "isRus = true".  Then save and upload this file to your server.