GangstaPichu's Wishlist

The Rebel ship   is ready to go,  the puzzle needs a blue card to get into the full loot.
Features:
Installation on water; Great detail; A lot of content; Loot is divided into rooms; Optimized fps. General Info:
Prefabs count: ~3k; Type: for looting; Modifiers: Topology. Loot:
Oil barrels 5; Food Crates: 5; Barrels: 30; Ordinary crates: 13; Military crates: 3; Elite crates: 1; and 1 red card. Other works:
 
 
 

Adds a cargo plane crash event to your server. The crash site is guarded by NPCs that patrol the area and can chase players.
You can also set up custom loot using the "SimpleLootTable" plugin.

Features:
Support for third-party plugins Great customization options in the config
Console commands:
callcargoplane -  force the event to start callcargoplane {steamID/name} - the event will be reserved for one player crashcargoplane -  force a cargo plane to crash cpc_stop -  force the event to end
Chat commands(need admin privileges):
showcrashzone -  displays the crash area setcrashzonecenter -  set the center of the crash zone to where the player is callcargoplane -  force the event to start callcargoplane {steamID/name} - the event will be reserved for one player crashcargoplane -  force a cargo plane to crash cpc_calltome - force an event to start (the cargo plane will go to the player's coordinates) cpc_stop -  force the event to end cpc_add_crashzone - adds a new zone at the location where the player is, can be used if you use multiple zones(you can set the name and radius - /cpc_add_crashzone "name" "radius") Hooks:
void CargoPlaneCrashStarted() // called when the event starts
void CargoPlaneCrashCrashed() //  called when a cargo plane crashes
void CargoPlaneCrashEnded() //  called when the event ends
CargoPlaneCrashEventWinner(BasePlayer player) //  called at the end of the event, returns the event winner
 
CargoPlaneCrash config:
{ "PVE mode (crates can only be looted by the player who first dealt damage to the NPC)": false, "Give event ownership to the owner's teammates if he is no longer the owner. Only if teammates are within the event radius (for PVE mode)": true, "Radius for event(for PVE mode)": 380, "Create a dome for PVE mode": false, "Dome transparency (the higher the value, the darker the dome, recommended 4)": 4, "Time after which the owner of the event will be deleted if he left the dome or left the server (for PVE mode)": 300, "Message when a player enters the event dome(only for PVE mode if there is a dome)": "You have entered the Cargo Plane Crash Event", "Message when the event owner leaves the event dome (only for PVE mode if there is a dome)": "Return to the event dome, otherwise after 300 seconds you will no longer be the owner of this event", "Do not allow other players into the event(only for PVE mode if there is a dome) Be careful, if the crash site is near the player's base and the player is not the owner of the event, he will be ejected from his base outside the dome": false, "Message when a player is ejected from the event dome(only for PVE mode if there is a dome)": "You cannot be here, you are not the owner of this event", "Allow admin to be in event dome (only for PVE mode if there is a dome)": true, "Triggering an event by timer (disable if you want to trigger the event only manually)": true, "Time to event start(in seconds)": 3600.0, "Random time to event start": false, "Minimum time to event start(in seconds)": 600, "Maximum time to event start(in seconds)": 10800, "CargoPlane speed(recommended 4 to 6)": 5.0, "Minimum amount of online players to trigger the event": 1, "Minimum crates amount(spawn after crash)": 1, "Maximum crates amount(spawn after crash)": 1, "Crate simple loot table name(plugin SimpleLootTable is required)": "", "Minimum number of items in a crate(plugin SimpleLootTable is required)": 0, "Maximum number of items in a crate(plugin SimpleLootTable is required)": 0, "Crates lifetime(in seconds). The crate will not be destroyed if it has been activated": 3600, "Crates timer(in seconds)": 900, "Remove crates after being looted by a player(in seconds)": 300, "Minimum airdrops amount(spawn after crash)": 1, "Maximum airdrops amount(spawn after crash)": 1, "Airdrop simple loot table name(plugin SimpleLootTable is required)": "", "Minimum number of items in an airdrop(plugin SimpleLootTable is required)": 0, "Maximum number of items in an airdrop(plugin SimpleLootTable is required)": 0, "Airdrops lifetime(in seconds)": 3600, "Fireballs amount(spawn after crash)": 5, "Passengers amount(spawn after crash)": 2, "Explosion marker on the map(spawn after crash)": true, "Explosion marker lifetime(in seconds)": 300, "Enable signal smoke(spawn after crash)": true, "Signal smoke lifetime(in seconds, max 214)": 214, "Map size(crash zone size), you can see the zone, use the chat command /showcrashzone": 4500.0, "Starting altitude, defaults to map size, can be increased if cargo plane hits high ground(no more than 10000 recommended)": 4500.0, "Crash zone center. Use chat command /setcrashzonecenter to set to player position. You can check crash zone center, use the chat command /showcrashzone": { "x": 0.0, "y": 0.0, "z": 0.0 }, "Use multiple zones": false, "Select a zone from the list sequentially(if false, then the crash zone will be chosen randomly)": false, "Zones list": [ { "name": "0", "radius": 300, "center": { "x": -300.0, "y": 0.0, "z": 0.0 } }, { "name": "1", "radius": 200, "center": { "x": 100.0, "y": 0.0, "z": 0.0 } } ], "Event message(if empty, no message will be displayed)": "CargoPlane event started", "Crash message(if empty, no message will be displayed)": "Cargo plane crashed", "Event end message(if empty, no message will be displayed)": "CargoPlaneCrash event ended", "Message about coordinates(will display the coordinates of the crash site. If empty, no message will be displayed)": "", "Kit name(you can use kits for passengers if you have Kits plugin)": "", "Passenger name": "Mister bot", "Use NPC prefab for passengers": false, "Minimum NPCs amount(spawn after crash)": 2, "Maximum NPCs amount(spawn after crash)": 2, "NPCs lifetime(in seconds)": 3600, "NPCs type(NPCs prefab, experimental setting, it is not known how the NPCs will behave) 0 - tunneldweller; 1 - underwaterdweller; 2 - excavator; 3 - full_any; 4 - lr300; 5 - mp5; 6 - pistol; 7 - shotgun; 8 - heavy; 9 - junkpile_pistol; 10 - oilrig; 11 - patrol; 12 - peacekeeper; 13 - roam; 14 - roamtethered; 15 - bandit_guard; 16 - cargo; 17 - cargo_turret_any; 18 - cargo_turret_lr300; 19 - ch47_gunner": 8, "NPCs health(0 - default)": 0, "NPCs damage multiplier": 1.0, "NPCs accuracy(the lower the value, the more accurate, 0 - maximum accuracy)": 2.0, "NPCs attack range": 75.0, "Radius of chasing the player(NPCs will chase the player as soon as he comes closer than the specified radius, must be no greater than the attack range)": 60.0, "Minimum distance to NPC damage": 75.0, "Message if the player attacks far away NPCs": "NPC is too far away, he doesn't take damage", "Kit for NPCs. The NPC will use the weapon that is in the first slot of the belt(requires Kits plugin)": "", "Default displayName for NPC(for SimpleKillFeed/DeathNotes plugin)": "Crashsite NPC", "List of displayNames for each NPC(for SimpleKillFeed/DeathNotes plugin)": [ "Crashsite NPC1", "Crashsite NPC2", "Crashsite NPC3" ], "Will NPCs attack zombies": true, "Remove NPC corpses": false, "Prohibit building near the crash site": false, "Building prohibition radius": 20.0, "How long construction is prohibited near the crash site(in seconds)": 1800, "Event marker on the map(spawn an event marker at the crash site)": false, "Display approximate end time of event on marker": false, "Event marker name": "Cargo plane crash site", "Event marker lifetime(in seconds)": 3600, "Event marker transparency(0-1)": 0.75, "Event marker radius": 0.5, "Event marker color.R(0-1)": 1.0, "Event marker color.G(0-1)": 0.0, "Event marker color.B(0-1)": 0.0, "Do not spawn crates and NPCs when a cargo plane falls under water (if the water depth is greater than)": 0.5, "Do not choose a crash site near monuments": false, "If possible, the crash site will not be chosen near player bases": true, "SteamID for chat message icon": 0, "Complete the event if all crates were destroyed after looting": false, "Use Notify plugin for messages": false, "Notify message type": 0 }

Turn player engagement into a clear, visual reward journey with configurable catalogues, secure claims, and administrator-controlled delivery.
At a glance
Create independent reward types with their own points, catalogue, commands, permission, language, and visual theme. Let players browse paginated rewards, see locked or claimed states, and claim eligible rewards from an in-game UI. Deliver items, server commands, permission grants, and group grants through one reviewed reward definition. Keep point ownership compatible with integrations such as Vote System while retaining administrator control. Recover safely from reloads and partial delivery without replaying completed actions. How it helps
Custom Rewards gives server owners one reusable reward layer instead of a separate UI and claim implementation for every event. Each reward type can represent voting, playtime, seasonal progress, VIP benefits, or another server-owned points source.
Key features
Multiple reward catalogues, each stored in its own JSON file. Configurable show commands and dynamic customrewards.<type>.use access. Common, Rare, Epic, and Legendary presentation with configurable colours. Per-page browsing with visible available, locked, and claimed states. Server-side eligibility checks repeated when a reward is claimed. Item, command, permission, and group actions. Owner-scoped point APIs for integrations. Durable claim progress and administrator-visible reconciliation when an external action has an uncertain result. Safe migration of supported legacy player data. Player workflow
An administrator enables a reviewed reward type and grants its use permission. The player runs one of that type's configured chat commands. The UI displays the current catalogue and the player's claim state. The player changes page if needed and selects an eligible reward. The server validates points, prerequisites, and claim state again before delivery. The visible screen distinguishes rewards that are available, already claimed, or unavailable. Administrators decide which commands display each catalogue and which groups can access it.
How it works
Each file in oxide/data/CustomRewards_rewards/ defines one reward type. Its filename is the exact type used by permissions and integrations. Player balances and claim progress are stored separately so an interrupted delivery can resume without repeating confirmed actions.
customrewards_give VoteSystem 76561198000000000 5
The example grants five owner points to the VoteSystem reward type. Run administrator commands from the server console or with the administrative permission.
Requirements and compatibility
Rust server using Oxide or Carbon. The standalone CustomRewards.cs file from this product. No required plugin dependency. Optional integrations must use the documented compatibility APIs and the same reward-type name. Setup
Back up existing oxide/data/CustomRewards_* files. Install CustomRewards.cs in the framework plugin directory. Let the plugin create oxide/data/CustomRewards_rewards/. Copy and rename the supplied example configuration for each reward type you need. Review every item name, server command, permission change, group change, image URL, and eligibility rule. Set Enabled to true only after that review. Grant customrewards.<type>.use and test the configured show command with a non-administrator account. Commands and permissions
CommandPurposeAuthorization
Reward-type show commandsOpen the configured catalogue UIAdministrator or customrewards.<type>.use
customrewards_give <type> <player> <quantity>Add points to one playercustomrewards.admin
customrewards_wipe_owner <type> <owner>Remove one owner's contribution from a balancecustomrewards.admin
customrewards_wipe_all <type>Clear all balances for one reward typecustomrewards.admin
customrewards_changepageInternal player paging actionPublic, arguments validated by the server
customrewards_claimInternal player claim actionPublic, eligibility rechecked by the server
The historical CustomRewards.Admin and CustomRewards.<Type>.Use forms remain accepted for existing installations.
Configuration highlights
New reward types are disabled by default. Start with a small catalogue and a test-only permission:
{ "Enabled": false, "Commands for show UI": ["vote_rewards"], "UI Settings": { "Max Reward By Page": 5, "Show Description": true }, "Rewards Settings": { "Rewards List": [ { "Rarity (Common - Rare - Epic - Legendary)": "Common", "Quantity": 100, "Item Shortname (optional)": "wood", "Server command (optional)": [], "Grant Permissions :": [], "Grant Groups :": {}, "Needed Permissions :": {}, "Needed Groups :": {} } ] } }
Only %steamid% is accepted as a command placeholder. Keep reward configuration restricted to trusted administrators because configured commands and access changes are privileged actions.
Practical tutorials
Example: create a voting catalogue
Create VoteSystem.json in oxide/data/CustomRewards_rewards/. Set a safe show command such as vote_rewards. Add one low-value test reward and leave the type disabled. Reload Custom Rewards and resolve every validation error. Grant customrewards.votesystem.use to a test group. Enable the type, add test points, open the UI, and claim the reward. Add the remaining catalogue only after the complete test succeeds. Example: integrate another points source
Use the owner-points API with a stable owner name. Keep the reward type identical in both plugins, check that it is enabled, and open the UI through the structured UI method so a failure can be reported without exposing an incomplete screen.
Troubleshooting
The show command is unknown: confirm the reward type is enabled and its command is unique. The UI says access is denied: grant customrewards.<type>.use or test with an administrator. A catalogue does not load: review the first validation error for invalid actions, empty rewards, unsafe placeholders, or contradictory access rules. A claim is pending review: inspect the administrator diagnostic before retrying; do not edit player data to bypass an uncertain external action. Images do not appear: verify direct HTTPS image URLs and keep custom URLs under administrator control. FAQ
Can two reward types use different themes?
Yes. Each reward-type file owns its catalogue, UI settings, colours, commands, and access permission.
Can a reward combine actions?
Yes. One reward can contain an item plus reviewed commands, permission grants, or group grants. Each action is tracked separately during delivery.
Does Custom Rewards require Vote System?
No. Vote System is an optional points source. Custom Rewards can run with administrator grants or another compatible integration.
Support
Use the Codefling support section with the plugin version, framework, reward-type name, the first relevant error, and a redacted configuration excerpt. Never include API tokens or private player data.

Raid Time Manager  ·  Rust  ·  Oxide  ·  Carbon Your best players get raided at 4am and never log in again You set the hours raiding is open. Outside them the damage, the ladder stacks, the ceiling drops and the turret placements all stop — and everyone can see the schedule on screen. A full week is configured out of the box, and every hour of it is editable from a calendar in game. The HUD Six layouts, one of them fits your screen Switched live from the settings screen — every player's HUD is redrawn on the spot.         How it goes From install to the night before wipe MINUTE ONE It works before you open the config Raid time is set to 18:00–22:00 Monday to Friday, 10:00–22:00 Saturday, 08:00–22:00 Sunday. Every hour outside that is safe time, and the restrictions are already on. Your timezone, by offset or by name, daylight saving included Several raid windows in one day, or none at all for a full safe day Nothing to fill in first — edit the week later, or never EVERY DAY Nobody has to ask when raid time is A HUD shows today's windows as a bar, a marker for where the clock sits inside them, and a green or red dot for whether raiding is open right now. Six positions, switched live. Players can hide it, and it hides itself on cameras and drones Every player reads it in their own language, on a 12- or 24-hour clock An alert on screen the moment raid time opens, and again when it closes An optional Discord webhook warns your players a set time before it opens WHEN THEY TRY Blocking damage alone does not stop a raid Someone who cannot blow a wall will stack ladders, drop a ceiling inside your compound, or park a turret on your door instead. Thirteen switches, so you block what matters on your server and leave the rest alone. Damage. Other people's buildings, your own, twig, boats, tugboats, fire Raids with no player behind them. Patrol helicopter, MLRS, SAM sites and auto turrets, each its own toggle Building tricks. Ladders and ceilings inside someone else's privilege, cupboards and turrets placed next to one They are told why. A blocked shot or placement puts the reason on the player's screen Your own exceptions. A prefab list that stays damageable whatever the clock says, and a separate switch for other people's sleeping bags WIPE DAY The exceptions are where a schedule earns its keep A fixed week is fine until wipe day, a holiday, or the first complaint about being raided ten minutes after joining. All four of those are settings. Set hours for one specific date from the calendar — it beats the weekly rule Safe days after a wipe, written into the schedule for you New players protected for a few hours, if you want them to be Or block offline raids only, with a shorter grace period for your donators   Alongside the rest It fits what you already run All optional, all off until you point at them. ✓  TruePVE — its ruleset is switched with the schedule, so the two never disagree   ✓  ZoneManager — confine the whole thing to listed zones, or apply it everywhere except them ✓  Raidable Bases — event bases stay raidable around the clock, safe time never locks players out   ✓  Your own commands — run any server command the moment raid time opens, and again when it closes   Reference One command, and it is yours to rename Everything else is a screen you click through in game. Chat /rtm Open the raid calendar. Admins also get a settings button on it. Chat /rtm hud Hide the HUD, or bring it back Perm rtm.vip Shorter offline grace period. Rename it or add more groups.     Straight answers Asked before every purchase Do I need TruePVE? No, it blocks the damage itself. TruePVE is optional and only makes the two systems agree if you already run it.   Can I still raid people who are online? Turn on offline-only mode and safe time protects a base only while the owner and their whole team are away. Do I have to edit config files? Not for the schedule. The calendar and settings screens change the hours, the toggles and the HUD position from in game.   Is it English only? No. Days, months, AM/PM and every message are language file entries, so you translate once and each player sees their own. What about NPCs and scripted raids? One switch lets non-player raiders through at any hour, and the prefab list covers anything that must always stay damageable.   Will the HUD annoy my players? Six positions including a compact one, they can dismiss it themselves, and you can switch it off server-wide.   13 actions you can block 6 HUD layouts 3 integrations — TruePVE, ZoneManager, Raidable Bases 1 dependency — ImageLibrary

Immerse yourself in the world of Rust with the VehicleBuy plugin! This powerful tool allows authorized players to easily access the /vehiclebuy command, which opens an intuitive interface for purchasing a variety of vehicles. With multiple payment options, including Items, Economics, and Server Rewards, you can enjoy a smooth gaming experience. Additionally, the Buy Cooldown feature helps maintain balance in the game.
Upon purchasing a vehicle, players receive a unique gift: a skinned crate for land vehicles or a lifebuoy for water vehicles, which can be conveniently stored in their inventory.
 

 
🌟  Features  of VehicleBuy
User-Friendly Interface: Access vehicle purchases through an easy-to-navigate GUI. Flexible Payment Methods: Choose from various payment options to suit your preferences. Customizable Settings: Administrators can adjust prices and fees as needed. Convenient Vehicle Recall: Use the /callback command to quickly retrieve your vehicle. Easy Re-packaging: Re-package vehicles using the /pickup command or by hitting them with a hammer.  
🎮  Commands
/vehiclebuy: Open the vehicle purchase interface (for players) /callback "VehicleName": Retrieve your purchased vehicle /pickup: Re-package your vehicle or hit it three times with a hammer Admin Command: (VehicleName.add SteamID): Spawn vehicles directly into players' inventories vehiclebuy.template [fullscreen/inmenu]: Customize your UI templates with options for fullscreen or in-menu displays (only server console)  
🛡️  Permissions
vehiclebuy.use: Allows players to use the /vehiclebuy command and access the vehicle purchase interface. vehiclebuy.free: Grants players the ability to acquire vehicles for free, bypassing the payment requirements. vehiclebuy.pickup: Permits players to use the /pickup command to re-package their vehicles. vehiclebuy.recall: Allows players to use the /callback command to retrieve their vehicles.  
📨  Video Overview
 
 
old overview:
 
 
 
🧪  Test Server
Join our test server to experience all our unique features firsthand!
Copy the IP address below to start playing!
connect 194.147.90.239:28015  
📚  FAQ
Q: Where can I see an example of a config?
A:    Config
Q: How do I add VehicleBuy to the ServerPanel menu?
A: Follow these simple steps:
1. Open ServerPanel menu in-game and click "+ADD CATEGORY" button
2. Set these exact parameters:
Type: Plugin Plugin Name: VehicleBuy Plugin Hook: API_OpenPlugin 3. Click "SAVE" button to create the category
Note: If VehicleBuy doesn't appear in ServerPanel menu, make sure both plugins are loaded and you typed the parameters exactly as shown above.
Q: I'm using the KazuraVehicles plugin and VehicleBuy doesn't work / throws errors. What should I do?
A: IMPORTANT: if you're using KazuraVehicles, you MUST enable a special dependency inside VehicleBuy, otherwise it simply will NOT work.
1) Open the plugin file Plugins/VehicleBuy/VehicleBuy.cs (or oxide/plugins/VehicleBuy.cs on your server).
2) At the very top of the file, find this line:
// #Requires: KaruzaVehiclesCommon 3) Change it EXACTLY to this (just remove the # after //😞
// Requires: KaruzaVehiclesCommon 4) Save the file and reload the plugin with o.reload VehicleBuy (Oxide) or c.reload VehicleBuy (Carbon).
If you skip ANY of these 4 steps, VehicleBuy + KazuraVehicles will NOT work correctly. Do all 4.