TOOLCUB's Wishlist

Welcome to the Smurf Detection Plugin by Bnucket! This powerful tool helps you maintain a level playing field on your Rust server by detecting potential smurf accounts.


- 🚨 Keep Your Rust Server Fair and Fun! 🚨
 
⭐️ Features
Automatic Smurf Detection: Identifies potential smurf accounts as soon as players join. Discord Integration: Sends alerts to your Discord server. Customizable Configurations: Tailor the plugin to meet your server’s specific needs. Whitelist Management: Exclude trusted players from smurf detection checks. Detailed Reports: Provides comprehensive player data and smurf probability. 🔧 How It Works
Player Connection: When a player connects to your server, the plugin fetches their Steam data. Data Analysis: The plugin analyzes various metrics like playtime, Steam level, friends count, game count, account age, achievements, and ban history. Probability Calculation: Using customizable thresholds, the plugin calculates the likelihood that the player is a smurf. Automated Actions: If the smurf probability exceeds your set threshold, the plugin can execute predefined commands (e.g., kick the player). Discord Alerts: Alerts are sent to a specified Discord channel, providing detailed player data and detection results. 🛠️ Easy Configuration
Modify the plugin configuration to suit your needs:
{ "SteamApiKey": "YOUR_STEAM_API_KEY", "DiscordWebhookUrl": "YOUR_DISCORD_WEBHOOK_URL", "MinPlayTime": 2000, "SmurfProbabilityThreshold": 85.0, "SmurfCommand": "kick {SteamID} Suspicious_account", "Whitelist": [] } { "PlayTime": {"MinValue": 0, "MaxValue": 2000, "MinProbability": 35, "MaxProbability": 0}, "SteamLevel": {"MinValue": 0, "MaxValue": 30, "MinProbability": 25, "MaxProbability": 0}, "FriendsCount": {"MinValue": 0, "MaxValue": 50, "MinProbability": 5, "MaxProbability": 0}, "GamesCount": {"MinValue": 0, "MaxValue": 40, "MinProbability": 20, "MaxProbability": 0}, "AccountAge": {"MinValue": 0, "MaxValue": 1095, "MinProbability": 5, "MaxProbability": 0}, "Achievements": {"MinValue": 0, "MaxValue": 92, "MinProbability": 4, "MaxProbability": 0}, "VACBan": {"MinValue": 0, "MaxValue": 1, "MinProbability": 0, "MaxProbability": 3}, "GameBan": {"MinValue": 0, "MaxValue": 1, "MinProbability": 0, "MaxProbability": 3} } 🔍 Detailed Player Data
For each player, the plugin collects and analyzes:
Playtime in Rust Steam Level Friends Count Games Count Account Age Achievements VAC and Game Bans 📲 Discord Notifications
Stay informed with instant notifications on Discord:
Player Name and Steam ID Smurf Probability Detailed Player Stats Detection Method (automatic/manual)
✅ Commands
Console Commands:
smurfcheck <playerName or steamId>: Manually check if a player is a smurf. whitelist <add/remove> <steamId>: Manage the whitelist. Chat Commands:
/smurfcheck <playerName or steamId>: Manually check via chat. /whitelist <add/remove> <steamId>: Manage the whitelist via chat.

Offline Raid Limiter
Stop Unfair Offline Raids in Their Tracks
Tired of seeing your Rust server overrun by offline raid abuse? Offline Raid Limiter steps in to restore balance and fair play. With powerful tracking and immediate damage blocking, your players can enjoy a more authentic Rust experience—and you can enjoy worry-free server management.
Key Benefits
Prevent Offline Raid Abuse
Daily Raid Limit: Automatically restrict how many offline raids each player (or team) can perform per day. Proximity-Based Tracking: Only counts raids when attackers are within range of a Tool Cupboard (TC), ensuring offline raid limits don’t trigger prematurely. Smart Raid Session Management
Team & Additional Raider Tracking: Keeps tabs on individual players as well as entire teams—even if they leave and rejoin. Plus, if additional players jump into the same raid, their involvement is recorded. Edge Case Handling: No more confusion or gaps in coverage if a defender goes offline mid-raid or when multiple attackers are involved. Offline Raid Limiter’s robust logic sorts out these scenarios seamlessly. Instant Damage Blocking
Enforce Fair Play: Once a team or individual hits their daily offline raid quota, further damage is blocked automatically. That means no more sneaky workarounds or unstoppable raids. Modded Server UI
In-Game Control: For modded servers, gain access to a simple in-game UI that displays raid history, player statistics, and real-time session data. Player-Friendly Features: Grant permissions so your players can check their offline raid counts with the /myraids command—helping everyone stay within the rules. Detailed Alerts & Reporting
Discord Integration: Offline Raid Limiter sends comprehensive alerts to Discord, making admin oversight a breeze. Export & Clear Sessions: Use /exportraidsessions to log and share your entire raid history for deeper analysis, then wipe all sessions with a simple console command if you need a fresh start. Designed for Vanilla & Modded Servers
Flexible Configuration: If you set your server to “Vanilla,” the plugin automatically disables UI and direct damage blocks, limiting itself to Discord notifications so admins can monitor raiding behind the scenes. Seamless Integration: Works hand-in-hand with Rust’s existing frameworks and requires only the Simple Status & Image Library for certain UI elements. Why Choose Offline Raid Limiter?
Enhanced Fairness: Players can’t take shortcuts with offline raids for easy loot. Clear Oversight: Admins see exactly who’s raiding and how often, helping you enforce balanced gameplay. Configurable & User-Friendly: Tailor the plugin to your server’s needs in just a few clicks, with plenty of documentation to guide you. If you’re ready to level the playing field and protect your community from unfair offline raids, Offline Raid Limiter has you covered. Bring your Rust server to new heights of balance, transparency, and peace of mind!
 
OfflineRaidLimiter_FullDocumentation_Updated.zip

 
Commands & Usage
Damage Blocking & Clearing Sessions
clearraidsessions
Console command: clearraidsessions Usage: Immediately removes all saved offline raid sessions. Purpose: Useful for resetting the entire raid history if you’ve made big changes or just need a fresh start. clearraidsforplayer <SteamID64>
Console command: clearraidsforplayer <SteamID64> Usage: Removes every offline raid session associated with a specific player (and their team). Notes: Handy for admins who need to give a particular player or group a second chance. simulatecleanup
Console command: simulatecleanup Usage: Triggers the plugin’s internal cleanup routine on demand to remove expired sessions. Notes: Essentially forces the “scheduled” cleanup to run right away for testing or maintenance. Temporary Disable & Enable
/orl.disable <hours> temporarily turns off offline raid tracking for a chosen duration. /orl.enable instantly re-enables protections if you wish to end the downtime early. /myraids Command
Players can quickly check their personal offline raid count, helping them stay aware of daily limits. Exporting Raid Data
exportraidsessions
Console command: exportraidsessions Usage: Exports a JSON file of all existing raid sessions and sends it to the Discord debug webhook for easy admin review. Notes: Great for deeper analysis or archiving raid history. Damage / Raid Logic
OfflineRaidLimiter checks incoming damage to building blocks, doors, external walls, and more. If a team or player has exceeded the daily offline raid limit, all further damage to offline bases is blocked—and you can optionally broadcast an alert to Discord. Key Points to Note About Commands
Some commands differ depending on your permissions and server setup. For instance, if a player types /exportraidsessions in chat, it won’t work unless they have OfflineRaidLimiter.admin. For “Vanilla” servers (as set in the config), UI, damage blocking, and certain other features may be disabled—so commands like clearraidsessions and clearraidsforplayer will still work, but may only be visible to server admins via console. When Commands Might Defer
Cleanup Commands: If the plugin detects that some raid sessions are still “cooling down” (meaning the raid window hasn’t fully expired), the system may defer clearing them until the next pass. This prevents conflicts with currently active raids. Blocking Logic: After the daily limit is reached, the blocking triggers immediately and remains in place until the next server reset or cleanup routine (depending on how you configure it).  

Features
Automatically detects when offline players are being raided
Notifies online players about raids in progress
Tracks and stores raid statistics for each player
Provides map markers at raid locations
Optional Discord webhook integration for raid notifications
Customizable notification cooldowns
Notifies players of raids that occurred while they were offline
Team-based notification system
 
Commands
| Command | Description | Permission |
|---------|-------------|------------|
| /raidinfo | View your own raid statistics | offlineraidannouncer.stats |
| /raidinfo [player] | View raid statistics for another player | offlineraidannouncer.admin |
| /raidstats | Alias for /raidinfo | Same as raidinfo |
| /ofra.clear | Clear all stored raid data | offlineraidannouncer.admin |
 
Permissions
| Permission | Description |
|------------|-------------|
| offlineraidannouncer.receive | Allows a player to receive raid notifications |
| offlineraidannouncer.bypasscooldown | Allows a player to bypass the notification cooldown |
| offlineraidannouncer.admin | Grants administrative access to commands and features |
| offlineraidannouncer.stats | Allows a player to view raid statistics |
 
Configuration Options
| Option | Description | Default |
|--------|-------------|---------|
| NotificationCooldown | Time in seconds before sending another notification to the same player | 600 |
| IncludeOwnerName | Whether to include the name of the base owner in raid alerts | true |
| IncludeRaiderName | Whether to include the name of the raider in raid alerts | true |
| WipeDataOnWipe | Whether to clear all stored data when the server wipes | false |
| NotifyRaidersTeam | Whether to notify the raider's team members about the raid | true |
| SaveRaidStatistics | Whether to save and track raid statistics for each player | true |
| NotifyOfflineOnReconnect | Whether to notify players about raids that happened while they were offline | true |
| RecentlyOfflineTime | Time in seconds to consider a player 'recently offline' after disconnecting | 300 |
| UseDiscordWebhook | Whether to send raid alerts to a Discord webhook | false |
| DiscordWebhookUrl | The URL of your Discord webhook for raid notifications | https://discord.com/api/webhooks/your/webhook/url |
| ExcludedZones | List of zone names where raid notifications won't be triggered (requires ZoneManager) | [] |
| RaidThreshold | The minimum number of raid events before triggering notifications | 3 |
| ShowMapMarker | Whether to show a map marker at the location of a raid | true |
| MapMarkerDuration | Duration in seconds that a raid map marker will remain visible | 300 |
| AdminOnlyNotifications | Whether to only send raid notifications to admins | false |
| MonitoredEntities | Entity types to monitor for raid detection | [BuildingBlock, Door, StorageContainer, ExternalWall, Lock, Trap, Barricade, SleepingBag, Turret, Furnace, Workbench] |
 
Dependencies
Optional: ZoneManager - Required for zone exclusion functionality
 
Discord Integration
To enable Discord notifications:
Create a webhook in your Discord server settings
Set UseDiscordWebhook to true in the plugin config
Add your webhook URL to the DiscordWebhookUrl setting
The plugin will now send raid notifications to your Discord server whenever an offline raid is detected.

 

Player Reporting Plugin,

Command Usage: /report (Player Name) (reason)
                               /adminreports - Gui for seeing players with reports and how many requires "playerreports.admin" permssion

Gui Preview in video below

Permissions:
o.grant group default playerreport.use o.grant group admin playerreport.admin Example Of Messages Sent To Discord Webhook Attached.

When a player is reported, In-Game admins will receive a notification of that person being reported, if they have the permission "playerreport.admin"


Default Config:
{   "Discord Webhook URL": "https://discord.com/api/webhooks/yourwebhookhere",   "Ban Notification Webhook URL": "https://discord.com/api/webhooks/yourwebhookhere",   "Server Shortname": "5x Duo Max Rustico",   "Admin Notification": true,   "Ban Appeal Link": "https://discord.gg/JKmGzRf7",   "Maximum Reports Before Auto Ban": 10 } Localisation Support:
{ "Usage": "Usage: /report <player name> <reason>", "PlayerNotFound": "Player '{0}' not found. Check the spelling or try a different name.", "DidYouMean": "Did you mean: {0}?", "ReportSubmitted": "Your report against {0} has been submitted.", "ReporterField": "Reporter", "ReportedPlayerField": "Reported Player", "ReasonField": "Reason", "ReportedOn": "Reported on", "DiscordError": "Failed to send report to Discord: {0}", "CooldownMessage": "Please wait {0} seconds before submitting another report.", "AdminNotification": "Player {0} reported {1} for: {2}", "AutoBanMessage": "You have been automatically banned due to multiple reports. Appeal: {0}" }

Easily give access to Rusts F1 Spawn Menu!  That's permission based with blacklisting support and customizable F1 Spawn button amounts!
 
Features:
* Ban whole categories or Items using their ShortName or ItemID's * Allow Admins or Developers to bypass F1 spawn * Control the amounts it gives on the 1k button & 100 buttons! * ItemID, Amount, SkinID, Conditions. * Shops & other 3rd party plugins. * TODO: Genetics & BPs.  
Perms:
f1spawn.use | needed to use F1 Menu. f1spawn.bypass | needed to bypass blocked Items.  
Chat & Console Commands:
/give itemID amount skin condition | everything past itemID are optional args /givearm itemID amount skin condition | everything past itemID are optional args give steamID-or-Name itemID amount skin condition | everything past itemID are optional args givearm steamID-or-Name itemID amount skin condition | everything past itemID are optional args  
Configuration File:
{ "Ignore: Disabled 0, Admin 2, Developer 3": 0, "Set F1 1000 button spawn amount": 1000, "Set F1 100 button spawn amount": 100, "Ban Categories: Weapon 0, Construction 1, Items 2, Resources 3, Attire 4, Tool 5, Medical 6, Food 7, Ammunition 8, Traps 9, Misc 10, Component 11, Electrical 12, Fun 13": [ 10 ], "Ban Items using: ShortNames (Easy to Read)": [ "explosive.timed", ], "Ban Items using: ItemIDs (Slightly Faster)": [ 143803535, ] }