Sigilo

What is DiscordLink? DiscordLink is a Discord bot designed for Rust gaming communities. It securely links Discord users to their Steam accounts, automates in-game reward distribution, and manages special perks for linked players and server boosters. The bot integrates with Rust servers via RCON and supports multiple servers. Key Features - Steam Account Linking: Users can link their Discord and Steam accounts for in-game rewards. - Booster Perks: Automatically grants and removes special in-game perks for Discord server boosters. - Role Management: Assigns a custom Discord role to users who link their Steam account. - Multi-Server Support: Works with multiple Rust servers at once. - Automated Reminders: Notifies boosters who haven't linked their Steam account. - Admin Tools: Commands for checking, resetting, and auditing links and perks. - Secure & Auditable: All actions are logged for transparency and troubleshooting. How It Works 1. User Links Account: - Users type /link <steam_id> in the designated Discord channel. - The bot validates the Steam ID and links it to the user's Discord account. - The user receives in-game rewards on all connected Rust servers. 2. Booster Perks: - If a user is a Discord server booster, the bot automatically grants them special in-game perks (e.g., Nitro group) on all servers. - If a booster stops boosting, perks are removed automatically. 3. Reminders: - Boosters who haven't linked their Steam account receive periodic reminders (can be disabled). 4. Admin Controls: - Admins can check, reset, or audit user links and booster perks with slash commands. Main Commands - /link <steam_id> – Link your Discord and Steam accounts for rewards. - /checklink – See your current link and booster status. - /reminders <on|off> – Enable or disable booster reminders. - /status – (Admin) Show server and user stats. - /reset <user> – (Admin) Reset a user's links, perks and cooldowns for changing the SteamID associated with the discord user. - /checklinks <user> – (Admin) Check a user's linked Steam IDs and booster status. Configuration For Server Admins - Set up the bot using the .env file and follow the install guide. - Make sure the bot has the right permissions and intents in your Discord server. - Use admin commands to manage and audit user links and perks. Environment Variables The bot uses a .env file for configuration. This file contains sensitive information like API keys and server credentials, so it should never be committed to version control. Why .env files? - Security: Keeps sensitive data separate from code - Flexibility: Easy to configure different settings for development and production - Standard Practice: Widely used in Python applications and deployment platforms Configuration Options: - RCON Timeouts: Configure WebSocket timeouts via `RCON_CONNECTION_TIMEOUT`, `RCON_OPERATION_TIMEOUT`, and `RCON_USERGROUP_TIMEOUT` - Server Settings: Add multiple Rust servers with `SERVER1_NAME`, `SERVER1_HOST`, etc. - Discord Settings: Configure roles, channels, and permissions - Steam Integration: Steam API key for SteamID validation For Users - Use /link <steam_id> in the correct channel to get in-game rewards. - If you boost the server, your perks are managed automatically. - Use /checklink to see your status or /reminders off to stop reminders. Support - For help, check `bot.log` or contact me.

Features Automatic Privilege Management: Detects when users start/stop boosting and adjusts permissions accordingly Steam ID Linking: Allows boosters to link their Steam ID to receive Rust server privileges Multi-Server Support: Manages multiple Rust servers via RCON Regular Auditing: Checks every 12 hours to ensure only active boosters have server privileges Reminder System: Sends daily reminders to boosters who haven't linked their Steam ID yet Security Measures: Limits on Steam ID changes to prevent abuse Pterodactyl Optimized: Designed to run seamlessly in a Pterodactyl panel environment (with a python egg) How It Works When a user boosts your Discord server, they receive a welcome message with instructions Boosters use the /link command to connect their Steam ID The bot automatically adds them to the configured Oxide group on all your Rust servers If a user stops boosting, their privileges are automatically removed User Commands /link Link your Steam ID to receive Rust server privileges. Steam ID must be a 17-digit number starting with 7656. Users can only change their Steam ID once every 30 days and a maximum of 2 times. Admins can link their Steam ID without boosting for testing purposes (it will be removed on the next audit). /checkboost Check your current boost status and Steam ID link. Shows your boost status, linked Steam ID, and available servers. Displays when you can next change your Steam ID. /reminders Enable or disable daily reminders about linking your Steam ID. Admin Commands /status Shows bot status, number of players boosting, linked Steam IDs, recent actions, and server connections. /reset Resets the Steam ID change count for players. This allows users to change their Steam ID again if they have reached their limit of 2 changes. Scheduled Tasks This bot runs the following automated tasks: Booster Status Check Every 1 hour. Verifies if users are still boosting the server and removes former boosters from the Nitro group. Nitro Group Audit Every 12 hours. Ensures only active boosters have Nitro privileges and removes unauthorized users from all servers. Reminder System Every 24 hours. Sends reminders to boosters who haven't linked their Steam ID. Only sends to users who have reminders enabled (enabled by default). Config: # Discord Bot Configuration DISCORD_TOKEN=YOUR_DISCORD_BOT_TOKEN_HERE GUILD_ID=YOUR_DISCORD_SERVER_ID_HERE ADMIN_ROLE_ID=YOUR_ADMIN_ROLE_ID_HERE WELCOME_CHANNEL_ID=YOUR_WELCOME_CHANNEL_ID_HERE COMMANDS_CHANNEL_ID=YOUR_COMMANDS_CHANNEL_ID_HERE TICKET_CHANNEL_ID=YOUR_TICKET_CHANNEL_ID_HERE STEAM_API_KEY=YOUR_STEAM_API_KEY OXIDE_GROUP_NAME=nitro # Server 1 Configuration SERVER1_NAME=Your Server Name SERVER1_HOST=server1.example.com SERVER1_PORT=28016 SERVER1_RCON_PASSWORD=your_rcon_password_here # Server 2 Configuration (optional - remove if not needed) SERVER2_NAME=Your Second Server Name SERVER2_HOST=server2.example.com SERVER2_PORT=28016 SERVER2_RCON_PASSWORD=your_rcon_password_here # Server 3 Configuration (optional - remove if not needed) SERVER3_NAME=Your Third Server Name SERVER3_HOST=server3.example.com SERVER3_PORT=28016 SERVER3_RCON_PASSWORD=your_rcon_password_here Requirements Python 3.8 or higher Discord Bot Token Rcon access to your Rust server

A powerful and visually stunning comet system that allows players to call down devastating meteors using supply signals. The plugin creates dramatic visual effects with chain explosions and temporary impact effects, adding an exciting new gameplay element to your Rust server. FEATURES: Unique signal for calling down comets Configurable cooldown timers for meteor summoning Customizable comet trajectory with diagonal fall paths Spectacular visual effects and explosions Dynamic chain explosions and secondary blast effects Configurable building and player damage Temporary effects at impact sites Admin commands for spawning comets and distributing signals PERMISSIONS: comet.admin -Allows use of admin commands and spawning comets comet.use -Allows players to use comet signals COMMANDS: /comet -Summon a comet at your location (admin) /comet here -Summon a comet at your crosshair location (admin) /givecometcaller [player] [amount] -Give comet signals to a player /givecometcaller [amount] -Give yourself comet signals /givecometcaller reset [player] -Reset cooldown for a player comet.summon x y z -Console command to summon a comet at coordinates comet.give [player] [amount] -Console command to give comet signals to a player comet.giveall [amount] -Console command to give comet signals to all connected players CONFIGURATION: Comet Appearance: Control how comets fall using the Speed Scale, height and horizontal offset (higher values create more diagonal fall paths). Damage Settings: Configure impact radius, base damage, and separate multipliers for building and player damage. Higher values create more devastation. Visual Effects: Adjust the number and timing of chain explosions, secondary blasts, and post-impact effects to create spectacular visual displays. Signal System: Customize the signal name, time before impact, and cooldown periods for players. CONFIG: { "Comet Configuration": { "Falling Speed Scale (lower = slower fall)": 0.5, "Minimum Height for Comet Spawn": 900.0, "Maximum Height for Comet Spawn": 950.0, "Horizontal Offset for Comet Spawn (0 = above target, higher = more diagonal fall)": 800.0, "Impact Radius": 7.0, "Base Explosion Damage": 500.0, "Building Damage Multiplier": 1.0, "Secondary Explosion Damage Scale": 0.75, "Maximum Chain Explosion Length": 5, "Delay Between Chain Explosions": 0.3, "Fall Speed of Chain Explosions": 5.0, "Number of Secondary Explosions": 20, "Initial Explosion Count": 10, "Post Impact Effect Interval": 3.0, "Post Impact Effect Count": 5, "Time Until Impact Site Cleanup (0 = never)": 10, "Player Damage Radius": 30.0, "Player Damage Amount": 20.0 }, "Signal Configuration": { "Signal Name": "Comet Signal", "Time Before Comet Falls (seconds)": 30.0, "Cooldown Time (seconds)": 300.0 } }

A powerful and configurable voting system that allows players to democratically ban disruptive players from your Rust server. Features Democratic Banning System: Players can initiate votes to ban other players Configurable Parameters: Customize voting duration, required percentage, and cooldown periods Temporary or Permanent Bans: Set ban durations or make them permanent Discord Integration: Automatic notifications for ban votes and results Localization Support: Easily translate messages to any language Anti-Abuse Measures: Cooldown between votes Minimum player requirement Optional admin protection Self-vote prevention Commands /voteban playername/steamid - Start a vote to ban a player /y - Vote yes on the current ban vote /n - Vote no on the current ban vote Permissions voteban.start - Allows starting ban votes voteban.vote - Allows participating in ban votes Configuration { "Required percentage (0-100)": 90.0, "Vote duration (seconds)": 120, "Cooldown between votes (minutes)": 10, "Ban duration (minutes, 0 for permanent)": 60, "Discord Webhook URL": "", "Log to console": false, "Minimum players required for voting": 9, "Allow voting to ban self": false, "Allow voting to ban admins": false, "Reminder interval (seconds)": 30 "Count only voters (if false, non-voters count as No)": true } Messages All messages are customizable and support color formatting: Vote initiation notifications Vote success/failure messages Error messages and warnings Permission denied notifications Instructions for voting Installation Place the plugin in your server's oxide/plugins folder Configure the settings to match your server's needs Set up permissions for your players (Optional) Configure Discord webhook for notifications Notes The plugin automatically manages temporary bans Integrates with Discord for ban notifications (if webhook URL is provided) Saves ban data between server restarts

A player voting system for temporary chat mutes. Supports both default chat and BetterChat, with persistent mute storage and Discord webhook integration. It will mute players from chat and voice channels. Permissions votemute.startvote - Allows initiating vote mutes votemute.vote - Allows participating in votes votemute.unmute - Allows manual unmuting (admin) Configuration { "Required percentage (0-100)": 60.0, // Percentage of yes votes needed "Vote duration (seconds)": 120, // How long voting period lasts "Cooldown between votes (minutes)": 10, // Time between vote initiations "Mute duration (minutes)": 60, // How long mutes last "Discord Webhook URL": "", // Optional Discord logging "Log to console": false, // Enable console logging "Minimum players required for voting": 4, // Server population requirement "Allow voting to mute self": false, // Self-mute prevention "Allow voting to mute admins": false, // Admin mute prevention "Reminder interval (seconds)": 30 // Interval of vote reminder message "Count only voters (if false, non-voters count as No)": true } Commands /votemute playername/steamid - Start vote to mute /yes - Vote in favor /no - Vote against /unmute playername/steamid - Admin unmute command Notes Mute data persists through server restarts via data file Integrates with BetterChat if present Supports team chat muting Automatic mute expiration system Vote session management with concurrent vote prevention Discord webhook sends detailed embeds with vote results Supports localization through language files Thread-safe mute operations Handles player disconnections during votes

This plugin automatically manages boomboxes in your Rust server by: Setting a default radio stream URL Automatically turning on radios when deployed/spawned Restarting radios periodically Turning on all radios after server restarts Separate control for deployed and static (monument) boomboxes Configuration { "Radio Stream URL": "http://s-00.wefunkradio.com:81/wefunk64.mp3", "Enable for deployed boomboxes": false, "Enable for static/monument boomboxes": true, "Auto-restart interval (minutes)": 60, "Enable auto-restart": true, "Turn on radios after server restart": true } Configuration Options - Radio Stream URL - The URL of the radio stream (must be a direct MP3 stream URL) - Enable for deployed boomboxes - Whether to activate player-placed boomboxes - Enable for static/monument boomboxes - Whether to activate static boomboxes found in monuments - Auto-restart interval (minutes) - How often to check and restart radios - Enable auto-restart - Whether to periodically restart radios - Turn on radios after server restart - Whether to activate all radios when server starts Installation 1. Download the plugin 2. Place the `RadioOn.cs` file in your server's `oxide/plugins` folder 3. Configure the plugin settings in the generated config file 4. Reload the plugin or restart your server Notes - Make sure your radio stream URL is a direct MP3 stream - The URL must be accessible from your server - Some radio streams might not work due to Rust's audio limitations Permissions This plugin doesn't require any special permissions to function.