codeboy

TeleportTerminal - Paid Teleport Terminals on Monuments TeleportTerminal turns ordinary monuments into a network of paid teleportation points. Players pay to travel right at the terminal. The price scales with distance and destination popularity, and admins place terminals and destinations through an in-game editor, so nobody has to touch a config file by hand. Terminals right on monuments. Place teleport points on any monument, including train tunnels and lab modules. The plugin finds the correct spots on the map automatically. Three terminal types. An NPC terminal (a full guard character with configurable name, kit, clothing and belt), a decorative prop, or an invisible interaction point with no model at all. Pick whichever fits the location. Ready-made setup included. Preset teleport destinations and NPC terminals are already spawned on monuments, so there's content on day one instead of an empty shell. Flexible monetization. Teleport price is calculated from distance to the destination and rises automatically for popular destinations through a dynamic surcharge, while permission-based discounts let admins reward VIPs or donators. Four payment options built in. ServerRewards, Economics, IQEconomic or Scrap: switch providers with one config line. If the chosen economy plugin is missing, the terminal falls back to Scrap automatically. A map built into the interface. Every terminal opens a map view with markers for all destinations, prices and zoom, so players see exactly where they can teleport and for how much, without leaving the panel. A full editor, no config files. Admins add and remove terminals, move them with pinpoint precision, manage destinations, adjust marker appearance on the map, and edit NPC profiles, all from an in-game menu. A visual prefab catalog. Terminal models are picked from a searchable catalog with previews, instead of typed in from memory. A player approaches a terminal and opens it (E key): A list of available destinations with the price for each, already including discounts and the current popularity surcharge. An interactive map of the monument or server with destination markers. Clicking a marker or a list row confirms the trip and teleports the player. An admin with editing rights opens the same interface in edit mode: Create and move terminals: snap to the nearest monument, fine-tune position and rotation, and use grid snapping. Manage destinations: add them, edit them, and require a specific permission for any given destination. Adjust style options: marker color, size, and icon, matching your server's theme. Edit the NPC profile: name, kit, clothing and gear for NPC-type terminals. All changes save immediately. There's no need to reload the plugin. An admin stands near a monument and creates a terminal from the editor, choosing the type (NPC, prop, or invisible), setting its look, and fine-tuning its position. Destinations are added, either open to everyone or restricted to players with a specific permission. A player with usage rights approaches the terminal, sees the map and destination list with prices, and teleports after paying through the configured economy. Pricing adjusts automatically. The more a destination gets picked, the higher its temporary surcharge climbs, and it decays gradually over time, while permission-based discounts reduce the final price. Supported out of the box: ServerRewards Economics IQEconomic Scrap (no extra plugin required, used as the default fallback) The provider is chosen with a single config line. If the selected economy plugin isn't loaded, the terminal falls back to Scrap automatically, so it keeps working without errors. TeleportTerminal needs the following plugins to function and will not work without them: HumanNPC: required for NPC-type terminals. MonumentFinder: required to detect monument locations, including train tunnels and lab modules. ServerRewards, Economics or IQEconomic: only needed if you want payment through one of these instead of Scrap. English and Russian are included out of the box. Every message lives in the language files, so translating or rewording anything for your community takes just a few minutes. Questions or suggestions? Reach out to us on Discord. Thank you for choosing TeleportTerminal!

PowerfulWhitelist is a whitelist for Rust. It works on its own through chat andconsole commands with login enforcement, and if you also run PowerfulAdmin itadds an in-game management panel. >>> No dependencies required. Install PowerfulAdmin only if you want the UI. Works on its own. Commands, enforcement and storage run with no other plugin installed. PowerfulAdmin is optional and only adds the in-game panel. Three storage backends. Keep the list in a JSON file, a local SQLite database, or MySQL/MariaDB to share it across several servers. Instant rejection at the connect screen. Players who are not whitelisted are rejected during login (`CanUserLogin`), so they never spawn in. The list is held in memory, so the check is instant and there is no "join then kick" flash. Shared list across servers. Point every server at the same MySQL database and additions and removals show up on all of them. Two independent on/off switches. Right on the Whitelist page: a This server switch (local) and an In database switch (shared across every server on the same database). The whitelist enforces if either one is on. Auto-reconnect. If the database is briefly unreachable at boot, the plugin keeps retrying and starts enforcing as soon as it connects. In-game panel. Search, add and remove from a UI that follows your PowerfulAdmin theme (requires PowerfulAdmin). Admin options. Server owners and moderators can be let through automatically, there is a bypass permission, and you can optionally kick non-listed players the moment the whitelist starts enforcing. A dedicated Whitelist section in the Tools category: A status banner with two switches, This server (local on/off) and In database (shared on/off, shown when a database backend is used), plus an Enforce button to kick everyone not on the list. The whitelist is active if either switch is on. The whitelist with search (by name or SteamID) and pagination. Each entry shows the player avatar, name, SteamID, who added it and when. One-click Remove with a confirmation step. An + Add dialog with: 1. a SteamID input with live validation (green when valid, red when not); 2. a searchable, paged player picker that shows online status and hides players who are already whitelisted; 3. an avatar and name preview before you confirm. A whitelist status row in the player popup card (Listed / Allowed / Not listed). Colors, fonts and switches follow your active theme. Every action is written to PowerfulAdmin's Logs. JSON (default): a plain data file, nothing to configure. Good for a single server. SQLite: a local database file, created automatically. MySQL / MariaDB: share one whitelist across many servers. Switch backends and migrate your data from the Settings page (your current list is copied into the new backend), or check your MySQL connection first with the built-in Test connection button. With MySQL, each server refreshes the list on a short interval, so an addition or removal made on one server shows up on the others. The Whitelist page has two separate switches: This server (local, per-server) and In database (shared). Flip the database switch on one server and the whole network starts enforcing. The whitelist is active whenever either switch is on. /whitelist add <name|steamid> - add a player /whitelist remove <name|steamid> - remove a player /whitelist list [page] - list whitelisted players /whitelist on | off - enable / disable the whitelist (this server) /whitelist enforce - kick everyone not on the list /whitelist status - show state and count /whitelist help - show all commands >>> /wl ... - short alias for /whitelist pwl add <name|steamid> pwl remove <name|steamid> pwl list [page] pwl on | pwl off pwl enforce pwl status pwl help powerfulwhitelist.view - Open the Whitelist section and read the list powerfulwhitelist.manage - Add, remove, toggle on/off and enforce powerfulwhitelist.bypass - Always allowed to connect, even when not listed A default config is generated on first load (PowerfulWhitelist.json { "Enabled": false, "AllowAdmins": true, "KickOnEnable": true, "ServerName": "", "InfoUrl": "", "Storage": "Json", "SyncInterval": 60, "MySql": { "Host": "127.0.0.1", "Port": 3306, "Database": "powerfulwhitelist", "User": "root", "Password": "" } } The shared database on/off state (the In database switch on the panel) is stored in the database, not in this config. Storage, MySQL credentials and these options can also be changed live from the Settings page when PowerfulAdmin is installed. Drop PowerfulWhitelist.cs into your plugins folder (Carbon: carbon/plugins/, Oxide: oxide/plugins/). The plugin loads and uses a JSON data file by default. No setup is required to start whitelisting. Grant the permissions above to your staff groups. Add yourself and your players (/whitelist add <name|steamid>), then turn it on (/whitelist on). (Optional) For a shared/network whitelist, open the config (or the Settings page), set Storage to MySql, fill in your credentials, and apply. (Optional) Install PowerfulAdmin to get the in-game whitelist panel. For MySQL storage: MySQL 8.0+ or MariaDB 10.2+ (recommended). PowerfulAdmin is optional, needed only for the in-game panel. English and Russian are included out of the box. Every message lives in the language files, so you can translate or reword anything for your community.

PowerfulFreeze lets your staff freeze a player on the spot in one of three styles, with per-freeze modifiers and an optional Freeze Gun. It works on its own through chat and console commands, and if you also run PowerfulAdmin it adds an in-game panel for managing freezes. >>> No dependency required. Install PowerfulAdmin only if you want the UI. Why PowerfulFreeze? Works on its own. Commands and enforcement need no other plugin. PowerfulAdmin is optional and only adds the panel. Three freeze modes. A frozen loading screen, an in-world position lock, or an invisible chair. Pick whichever fits the situation. Per-freeze modifiers. Invulnerability, no-deal-damage, vanish, keep-alive, mute, hide-from-map and item lock, each toggled on its own. A Freeze Gun. Give moderators a weapon that freezes whoever they hit, with an in-hand menu to change duration and mode while holding it. Timed or permanent. Any duration like 30m, 2h, 1d12h, or leave it permanent. Frozen players see a countdown. An in-game panel. Search, page, freeze, extend and unfreeze from a UI that matches your PowerfulAdmin theme (needs PowerfulAdmin). Survives reconnects and restarts. Freezes are saved and re-applied when the player returns or the server reboots. Freeze modes Screen. The target gets a full-screen frozen overlay showing the reason and the time left. There is nothing to play through. Position Lock. The player stays in the world and can look around, but is snapped back the moment they try to move. Useful when you want to talk to someone and keep them in place. Mount. The target is seated on an invisible chair and cannot get off. Modifiers Each freeze can carry any combination of these, set from the panel or applied by default from the config: No take damage - the frozen player cannot be hurt. No deal damage - the frozen player cannot hurt anyone. Vanish - the player is hidden from everyone except staff with the see-vanish permission. No death - keeps the player alive by stopping bleeding, cold and radiation from killing them. Mute - blocks the player's chat and voice. Hide from map - removes the player from their team for the duration, so they drop off the team map. Lock items - the player cannot move or drop items. The Freeze Gun Give moderators a weapon that freezes on hit Configurable item, skin and name (default: a marked revolver called "Freeze Gun"). Freezes any player it hits for the gun's current duration and mode. Press reload while holding it to open an in-hand menu and change the duration or mode. Optional infinite ammo and no condition loss, so it does not run dry or break. Optional auto-removal from players who do not have the permission. Hand it out with /freezegun (or pf.gun.give). The in-game panel (requires PowerfulAdmin) A Freeze section in the Tools category: A freeze list with search by name or SteamID, and pagination. Each entry shows the name, SteamID, mode and the time left (or "permanent"). A detail view with the reason, who set it, the mode, the date, a live countdown, quick +/- time buttons and modifier toggles. One-click Unfreeze with a confirmation step. Freeze composer: a searchable, paged player picker, reason templates and a free-text reason, duration presets or a custom value, mode selection and modifier toggles. A Freeze action in the player popup, anywhere in the panel. It follows your active theme. Every action is written to PowerfulAdmin's Logs. Commands Chat: /freeze <name|steamid> [duration] [mode] [reason] /unfreeze <name|steamid> /freezeinfo <name|steamid> /freezegun - give yourself the freeze gun /freeze help - show all commands Console / RCON: pf.freeze <name|steamid> [duration] [mode] [reason] pf.unfreeze <name|steamid> pf.info <name|steamid> pf.list [page] - paged active freeze list pf.ui - open the in-game panel (in-game player only) pf.gun.give - give yourself the freeze gun Duration examples: 30m, 2h, 7d, 1d12h. Empty or 0 means permanent. Mode keywords: screen, world / pos / lock (position lock), mount / chair (invisible chair). Leave it out to use the default mode. Permissions powerfulfreeze.freeze - Freeze, extend, and edit modifiers powerfulfreeze.unfreeze - Unfreeze powerfulfreeze.view - Open the Freeze section and view freeze info powerfulfreeze.gun - Receive and use the Freeze Gun powerfulfreeze.seevanishforfreezed - See players frozen with the Vanish modifier Configuration { "DefaultMode": "LoadingScreen", "BroadcastFreezes": true, "NotifyFrozen": true, "ServerName": "", "DefaultFlags": "NoDeath", "GunEnabled": true, "GunItem": "pistol.revolver", "GunDefaultDuration": "5m", "GunBlockDamage": true, "GunSkin": 0, "GunName": "Freeze Gun", "GunInfiniteAmmo": true, "GunRemoveUnpermitted": true } DefaultMode - mode used when none is given: `LoadingScreen`, `PositionLock` or `Mount`. DefaultFlags - modifiers put on a new freeze by default (combine with commas, e.g. `NoDeath, Mute`). BroadcastFreezes / NotifyFrozen - announce freezes to everyone / notify the frozen player. GunEnabled / GunItem / GunSkin / GunName - the Freeze Gun's behavior and appearance. GunDefaultDuration / GunBlockDamage - the gun's starting duration, and whether its shots deal no real damage. GunInfiniteAmmo - never run out of ammo or lose condition. GunRemoveUnpermitted - take the gun away from players without the gun permission. When PowerfulAdmin is installed, most of these can also be changed from the Settings page without editing the file. Installation Drop PowerfulFreeze.cs into your plugins folder (Carbon: carbon/plugins/, Oxide: oxide/plugins/). The plugin loads and generates its config. There is nothing else to set up before you can freeze someone. Grant the permissions above to your staff groups. (Optional) Install PowerfulAdmin to get the in-game freeze panel. Use the commands above, or open the Freeze section in the panel (Tools category) if PowerfulAdmin is installed. Localization English and Russian ship with the plugin. Every message lives in the language files, so you can translate or reword anything for your community. Questions or bug reports? Reach out on our Discord.

PowerfulBans is a complete, database-backed ban system for Rust. It runs perfectly on its own (chat and console commands, login enforcement, and its own SQLite or MySQL database), and when you also run PowerfulAdmin it adds a full in-game ban management panel. >>> No dependency required. Install PowerfulAdmin only if you want the UI. Why PowerfulBans? Works on its own. Commands, enforcement and storage all work with no other plugin installed. PowerfulAdmin is optional and only adds the in-game panel. Your own database. Bans live in SQLite (zero setup) or MySQL/MariaDB, ready to share across your whole server network. One banlist for your network. Point every server at the same MySQL database and a ban on one server applies on all of them, instantly. A real in-game panel. Search, page, ban, extend and unban from a polished UI that follows your PowerfulAdmin theme (requires PowerfulAdmin). Steam-aware. Optional VAC/Game ban checks and auto-kick using your own Steam Web API key. Safe by design. If the database is unreachable, bans are blocked with a clear message instead of silently failing, and a broken connection is reported on startup. The in-game panel (requires PowerfulAdmin) A dedicated Bans section in the Tools category: Live ban list with search (by name or SteamID) and pagination. Each entry shows the name, SteamID, reason, who issued it, and a clean live remaining-time countdown (e.g. "9d 1h 10m" or "permanent"). One-click Extend and Unban (with a confirmation step). A Ban dialog with: - a searchable, paged player picker showing online status, VAC/Game ban flags and Rust hours; - reason templates plus a free-text reason and a staff-only comment; - duration presets (1h, 6h, 1d, 7d, 30d, permanent) or a custom duration like `1d12h`. A Ban action right in the player popup, anywhere in the panel. Theme-aware: colors, fonts and switches follow your active theme. Every action is written to PowerfulAdmin's Logs. Database and multi-server SQLite (default): nothing to configure, the database file is created automatically. Perfect for a single server. MySQL / MariaDB: share one banlist across many servers. Each server can carry its own name in the shared data. Switch storage and migrate your data right from the Settings page, with row-count verification that reports a clear error if anything goes wrong. Prefer the console? Migrate without the UI from the server console: pb.migrate <sqlite|mysql> Bans are checked directly against the database on every login (no stale cache), so cross-server bans take effect immediately. Steam integration (optional) Set your Steam Web API key in the PowerfulBans config (or from the Settings page)and PowerfulBans can: show VAC / Game ban status on the player picker; automatically kick players who have a recent VAC/Game ban, with a configurable threshold in days. This works with or without PowerfulAdmin. Rust playtime on the picker is shownwhen PowerfulAdmin is present. Steam results are cached in the plugin's own database and refreshed automatically, respecting Steam's rate limits. Commands Chat: /ban <name|steamid> [duration] [reason] /unban <name|steamid> /baninfo <name|steamid> /ban help - show all commands Console / RCON: pb.ban <name|steamid> [duration] [reason] pb.unban <name|steamid> pb.info <name|steamid> pb.list [page] - paged active ban list pb.migrate <sqlite|mysql> - migrate storage to another backend (server console only) Duration examples: "30m", "2h", "7d", "1d12h". Empty or "0" = permanent. Permissions powerfulbans.ban - Ban and extend bans powerfulbans.unban - Unban powerfulbans.view - Open the Bans section and use /baninfo --- Configuration { "Storage": "Sqlite", "MySql": { "Host": "127.0.0.1", "Port": 3306, "Database": "powerfulbans", "User": "root", "Password": "" }, "ServerName": "Main #1", "BroadcastBans": true, "AppealUrl": "https://discord.gg/...", "KickRecentSteamBan": false, "RecentSteamBanDays": 30, "SteamApiKey": "" } You can also change storage, credentials, the Steam API key and these options live from the Settings page when PowerfulAdmin is installed. Installation Drop PowerfulBans.cs into your plugins folder (Carbon: carbon/plugins/, Oxide: oxide/plugins/). The plugin loads and creates its SQLite database automatically. No setup is required to start banning. Grant the permissions above to your staff groups. (Optional) For a shared/network banlist, open the config, set Storage to MySql, fill in your credentials, and reload the plugin. (Optional) For Steam VAC/Game checks, put your Steam Web API key into SteamApiKey in the config (or the Settings page). (Optional) Install PowerfulAdmin to get the in-game ban panel and Rust playtime. Done. Use the commands above, or open the Bans section in the panel (Tools category) if PowerfulAdmin is installed. Requirements For MySQL storage: MySQL 8.0+ (recommended) or MariaDB 10.2+. Localization Fully localizable. English and Russian are included out of the box, and every message lives in the language files so you can translate or reword anything for your community. API