MortuusVivensX's Wishlist

Bundle of four addons made  for Welcome Panel UI.  
All four addons including preset default config files as you see them on screenshots.






 












 
 

Heli Signals allows players with permission to call an Attack Helicopter to their location with a custom Supply Signal, where it will engage players and patrol, allowing players to fight it to win the valuable Heli crates.
The plugin comes with 8 default heli profiles, Easy, Medium, Hard and Elite, with a duplicate profile of each set up for calling multiple helis at once for each tier. In addition there is also 2 Wave Heli profiles, which will call in a wave of different helis one after the other. Each default profile has it's own custom supply signal skin (below). Server owners can add as many profiles as they like in the config by copying and pasting an existing profile within the config and editing to suit. This may require the server owner to create their own custom skin for the inventory item.
If you are setting up Multi heli signals, set the global and player limit in the config accordingly to accommodate higher numbers of helicopters per player.
There is also an option to have a BotReSpawn profile spawn at the crash site, just set the BotReSpawn profile name in the config.
IMPORTANT:
Each heli profile or wave profile in the config MUST have its own unique name and skin ID, otherwise you will have issues.
NOTE ABOUT SHOPS:
The profile name in the config should match the Custom Supply Signal name which the shop gives the player. The Helicopter Name is separate  and can be set independently from the Signal item. Also, when giving players items from shop plugins, if available, I always recommend  adding the item to the shop using custom name, skinID etc, rather than the console command, but either will work.
NOTE ABOUT DEEP SEA:

There are config options to allow or disallow calling a Heli Signal while in the Deep Sea. There is also a config option to retire a players active Heli Signals if they teleport to Deep Sea. If you allow players to teleport to Deep Sea with active helis and you have return to player set to true, the heli will eventually (after a good few minutes of flying) reach the players location in the Deep Sea.
 
Plugin default Supply Signal Skin ID's to add items to various shops, loot plugins, kits etc are:
Heli Signal (Easy) :  2920175997
Heli Signal (Medium) :  2920176079
Heli Signal (Hard) :  2920176050
Heli Signal (Elite) :  2920176024
Heli Signal (Expert) :  3099117081
Heli Signal (Nightmare) :  3099117372
 

 
Multi Heli (Easy) :  3083234542
Multi Heli (Medium) :  3083234833
Multi Heli (Hard) :  3083234755
Multi Heli (Elite) :  3083234647
Multi Heli (Expert) :  3099124338
Multi Heli (Nightmare) :  3099124426
 

 
Heli Wave Signal :  3099117224
Heli Wave Signal (Normal):  3104667036
Heli Wave Signal (Hard):  3104666951

 
Default Permissions:
helisignals.admin (to use give|hsclearcd command) helisignals.buy (to use /hsbuy command) helisignals.bypasscooldown helisignals.easy helisignals.medium helisignals.hard helisignals.elite helisignals.easy_multi helisignals.medium_multi helisignals.hard_multi helisignals.elite_multi helisignals.wave_normal helisignals.wave_hard Please note: Permissions above are with default config, permission for each Heli profile can be customised in the config.
Commands (Prefix with / to use in game):
hsgive <Profile ShortName> <Steam64ID> <Amount> hsbuy list hsbuy <Profile Shortname> hsreport (Get details of all active helis) hsretire (Retire all a player or their teams called Helis, no refunds) hsclearcd (clear all cooldowns) hsclearcd <SteamID|Name> (clear cooldown for player) (Buy and Retire command customisable in config)
 
Please note correct usage for Supply Signal name and Helicopter display name. These values CAN be different if you wish:

 
Loot Options:
Use the loot item example entries in the default config to create custom loot tables for crates.
How to Add Loot Table Items (Example):
 
For Other Developers:
The following hook is available to use in your plugins to check custom Supply Signals or Patrol Helicopters to avoid conflict with your plugins:
object IsHeliSignalObject(ulong skinID)
This will return true if the item is a Bradley Drop item/entity, or null if not.
Call it directly without referencing the plugin:
if (Interface.Call("IsHeliSignalObject", skinID) != null) return true; // IsHeliSignalObject Or reference my plugin and call like this:
[PluginReference] Plugin HeliSignals; if (HeliSignals.Call("IsHeliSignalObject", skinID) != null) return true; // IsHeliSignalObject To return some basic info about a Heli Signal object:

object GetHeliSignalData(Patrolhelicopter heli)

Returns object as Dictionary<string, object>.

Returned data is:
["heliProfile"] // string - Actual heli profile (from config) ["heliName"] // string - Heli display name ["skinId"] // ulong ["heliId"] // ulong (Net.ID.Value) ["owner"] // BasePlayer ["lastAttacker"] // BasePlayer ["calledPosition"] // Vector3 ["callingTeam"] // List Example usage:
var hdata = HeliSignals.Call("GetHeliSignalData", heli) as Dictionary<string, object>; string _heliProfile = hdata["heliProfile"]; string _heliName = hdata["heliName"]; string _heliSkin = hdata["skinId"]; string _owner = hdata["owner"]; etc  

Let your players shop from the safety of their own bases. Give them the ability to place & pickup their own drone Marketplaces, plus they look cool! With all the necessary configurable options, players will love this on any type of server, PvP or PvE.
To add Marketplaces to server shops, I recommend adding the item rather than the command. You can do this with the following:
Shortname: box.wooden.large SkinID:  2859284352  
Features.
Support for Friends, Clans, Teams Works with rewards shops like Server Rewards, Economics etc. Force on foundation (optional) Pickup by hitting a terminal with a  hammer or chat command Allow multiple marketplaces (optional) Allow players to craft (optional) Configurable crafting cost More control with optional permissions Drop item if building underneath destroyed (optional) Lose condition on pickup (optional) Checks for space before placing (prevents clipping through structures) Config option to add vending machines to Marketplaces Option to block damage to attached vending machines Important Note: Rotate attached vending machines by hitting with a hammer.
In-Game Commands (Remove / Prefix in F1 Console).
/marketplace.give (give to self) /marketplace.give <PlayerName>   or <SteamID>  (give to player) /marketplace.craft /marketplace.pickup (Or hit a terminal with hammer) /marketplace.clear  (Clear ALL stored marketplace data) /marketplace.clear <SteamID> (Remove marketplace data for player) Console/RCON Command.
marketplace.give <PlayerName> or <SteamID>  (give to player) marketplace.clear  (Clear ALL stored marketplace data) marketplace.clear <SteamID> (Remove marketplace data for player) (Use console command in reward shops or give custom skinned item)

Permissions (Optional).
personalmarketplace.admin (Required for give & clear commands) personalmarketplace.deploy personalmarketplace.pickup personalmarketplace.craft API:
Plugin devs can prevent conflict with this plugin by utilizing the following:
Interface.CallHook("MarketplaceCheck", skinID)
(where skinID = the skinID of the entity you are checking e.g. entity.skinID)
Returns true if the given entity's skinID matches an item used by this plugin (deployable wooden box item, or Marketplace entity) or null if it is not. Plugin devs can use this to prevent conflict with their plugins if dealing with large wooden boxes or other items which maybe be Marketplace related, now or in the future.

How to Place.

As there is no deployable marketplace item in Rust, the plugin uses the large wooden box planner to help guide and align the Marketplace where you want to place it. Keep in mind the marketplace is a very large item, so it is only a guide to help align it. Make sure to place it far away from where you stand and from buildings, if there is not enough room you will not be able to place and you will get a chat message to tell you this. If you don’t get the position right first time, no worries, just pick it up and try again until happy with the placement. Use caution if marketplace condition is enabled, picking up the marketplace too many times will cause it to break and it is NOT repairable!
Marketplaces are better placed in the middle of a 3x4 or larger foundation for best placement (see below image), but can be placed on open terrain or floors if allowed as such in the config:

 
Inventory item:


Custom Icon (to use in reward shops etc):  https://rustynuts.gg/pmicon.png


 

NEW for 1.3.0:
Please make sure you are updating from version 1.2.7, or your config may be corrupted.
New completely custom Bradley AI for a much more immersive and real experience! Each battle is different and fun! No more cheesing the event or hiding from Bradley!
PLEASE CHECK OUT THE NEW CONFIG STRUCTURE AND OPTIONS!
Bradley can now dynamically path find, re-path when stuck and actively hunt players who try and hide or retreat. New Fireball config options for damage, lifetime, chance to spread, etc Many new CH47 options, such as health, homing missile actions, can now use flares to counter homing missiles! Can now also specify Hackable crates to drop when destroyed. CH47 Scientist gunner options, such as health, damage, aimcone, kits, etc. Bradley can now counter high risk targets with smoke grenades, making it harder for them to target, with cooldown options in config. (players with rocket launchers, timed explosives, satchels etc) Bradley can now damage more obstacles by ramming, which is fully configurable in the config file Crate loot capacity is now resizable and can take up to 48 items for both Bradley and Hackable crates. Please carefully check config options for "Allow Players to Call Bradleys at Monuments". This config option has changed slightly. You can set allow at monuments true or false, then the monument list is to either block selected monuments when allowed is true, or allow when use at monuments is false. The monuments list is therefore now an exception to allow exception to the "Allow Players to Call Bradleys at Monuments" rule. Check this still works as you require. If you are unsure, reach out to me for help.
 
Bradley Drops allows players with permission to call a Bradley APC to their location with a custom Supply Signal, where it will patrol a set distance for a set time, allowing players to fight it to win the valuable Bradley crates.
A cargo plane will deliver and drop the APC via parachutes. The APC can be configured in different ways and there are many config options to suit all servers.
The plugin comes with 4 default settings for Bradley Drops, Easy, Medium, Hard and Elite, each with their own custom supply signal skin. But server owners can add as many options as they like in the config by copying and pasting an existing profile within the config. This would however require the server owner to create their own custom skin for the inventory item. (I will add more custom skins in the near future for this.)
BotReSpawn compatibility, with the option to specify a BRS spawn profile at the Bradley kill site.
IMPORTANT:
Each bradley profile or wave profile in the config MUST have its own unique name and skin ID, otherwise you will have issues.
NOTE ABOUT SHOPS:
The profile name in the config should match the Custom Supply Signal name which the shop gives the player. The Bradley Name is now separate  and can be set independently.
Plugin default Supply Signal Skin ID's to add items to various shops, loot plugins, kits etc are:
Bradley Drop (Easy) :  2905355269 Bradley Drop (Medium) :  2905355312 Bradley Drop (Hard) :  2905355296 Bradley Drop (Elite) :  2911864795 Bradley Drop (Expert) :  3361673979 Bradley Drop (Nightmare) :  3361674045  

 
 

 
Bradley Drop Wave (Normal): 3502926194 Bradley Drop Wave (Hard): 3502926112  
Default Permissions:
bradleydrops.admin (to use give|hsclearcd  command) bradleydrops.buy (to use /bdbuy command) bradleydrops.bypasscooldown bradleydrops.easy bradleydrops.medium bradleydrops.hard bradleydrops.elite  
Commands (Prefix with / to use in game):
bdgive <Profile ShortName> <Steam64ID> <Amount> bdbuy <Profile Shortname> bdbuy list bdreport (list all active Bradleys and their state) bddespawn (Despawn all Bradleys called by a player or their team, no refunds) bdclearcd (clear all cooldowns) bdclearcd <SteamID|Name> (clear cooldown for player) (Buy, Report and Despawn command can be customised in the config)
 
Please note correct use in config file for supply signal name and Bradley APC display name. These values CAN be different if you wish:

Custom Loot:
Check out the example loot items in the default config below to see how to add custom loot items to crates.
How to Add Custom Loot Table Item:
Config:
API: For Other Developers:
The following hook is available to use in your plugins to check custom Supply Signals, Cargo Planes and Supply Drops to avoid conflict with your plugins:
object IsBradleyDrop(ulong skinID)
This will return true if the item is a Bradley Drop item/entity, or null if not.
Call it directly without referencing the plugin:
if (Interface.Call("IsBradleyDrop", skinID) != null) return true; // IsBradleyDrop Or reference my plugin and call like this:
[PluginReference] Plugin BradleyDrops; if (BradleyDrops.Call("IsBradleyDrop", skinID) != null) return true; // IsBradleyDrop To return some basic info about a Bradley Drop object:
 
object GetBradleyDropData(BradleyAPC bradley)
Returns object as  Dictionary<string, object>.
Returned data is:
["apcProfile"] // string - Actual bradley profile (from config) ["apcName"] // string - Bradley display name ["skinId"] // ulong ["bradleyId"] // ulong (Net.ID.Value) ["owner"] // BasePlayer ["lastAttacker"] // BasePlayer ["calledPosition"] // Vector3 ["callingTeam"] // List ["ch47"] // CH47Helicopter ["plane"] // CargoPlane ["balloon"] // HotAirBalloon ["currentState"] // enum BradleyState (PATROL, ENGAGE, HUNT, MOVETOENGAGE) Example usage:
 
var bdata = BradleyDrops.Call("GetBradleyDropData", bradley) as Dictionary<string, object>; string _apcProfile = bdata["apcProfile"]; string _apcName = bdata["apcName"]; string _apcName = bdata["apcName"]; string _owner = bdata["owner"]; etc  

Dungeon Events adds fully procedural dungeon raids to your Rust server, creating high-replayability PvE content with unique layouts every time.
Each dungeon is dynamically generated with randomized rooms, corridors, NPCs, bosses, auto turrets, loot crates, and portal access. Whether you want automated world events or private player-purchased dungeon runs, this plugin gives you full control over difficulty, rewards, access, and cleanup.
Perfect for servers that want challenging, customizable, and rewarding endgame-style PvE content.
 
Main Features
Procedural Dungeon Generation - Every dungeon is generated dynamically, so each run feels different. Multiple Difficulty Tiers - Create fully customizable tiers such as Easy, Hard, Nightmare, or anything you want. Custom NPCs & Bosses - Configure health, damage, gear, custom names, movement, attack distance, and loot. Auto Turrets - Add dangerous turret encounters with configurable health, weapons, and behavior. Custom Loot System - Configure loot boxes, NPC loot, and boss loot with custom chances, amounts, names, and skins. Buyable Private Dungeons - Let players purchase their own dungeon using Economics, ServerRewards, or a custom item like scrap. Access Control - Lock dungeons to the buyer or first player, with optional support for teams and friends. Auto Spawn & Manual Spawn - Spawn dungeons automatically, by admin command, player purchase, or console/RCON. Smart Spawn Checks - Avoid bad locations, terrain issues, safe zones, rocks, monuments, and plugin-controlled areas. Automatic Cleanup - Remove dungeons when inactive, expired, or fully cleared. Reward Integrations - Supports Economics, ServerRewards, and SkillTree XP rewards. Live Dungeon UI & Map Markers - Show remaining time, entity counts, and map markers for active dungeons.  
Commands
Admin
/createdungeon <tierName> /removeinactivedungeons /removealldungeons /forceremovealldungeons /de.removenearest /de.reloadconfig /de.toggle Players
/buydungeon /buydungeon <tierName> /removedungeon Console
buydungeon <tierName> <playerID> spawnrandomdungeon spawnfixeddungeon <tierName> spawnfixeddungeon <tierName> <playerID>  
Permissions
dungeonevents.admin dungeonevents.buy dungeonevents.enter  
Hooks
void OnDungeonSpawn(ulong OwnerID, Vector3 Position, string Grid, string TierName) void OnDungeonDespawn(ulong OwnerID, Vector3 Position, string Grid, string TierName) void OnDungeonWin(ulong playerID, string tierName)  
Supported Integrations
Economics ServerRewards Friends Notify NightVision ZoneManager Duelist RaidableBases AbandonedBases RestoreUponDeath SkillTree  
Languages
EN PT-BR DE ES RU If you want a powerful, replayable PvE dungeon system with deep customization and strong plugin integration, Dungeon Events is built to deliver exactly that.
 
Plugin config, where you can change tiers, loot items, turret settings, dependencies, spawn logic, auto-removal conditions, economy integration, and more.