Bubbafett

Place a map marker. Teleport straight to it. Teleport Marker is a free Rust plugin for Oxide and Carbon that lets players with permission teleport to newly placed map markers. Handy for server administration, exploring the map, and setting up events. Features Map-based teleporting — open your map and place a marker to travel to that location. Continuous or one-time use — toggle teleporting with /tpm, or use /tpm once for a single jump. Permission-based access — choose which players or staff members can use it. Automatic marker cleanup — the marker is removed after teleporting. Customisable messages — translate or personalise all chat responses through the language files. No configuration required — grant permission and you're ready to go. How to Use Grant the player or group the teleportmarker.use permission. Type /tpm for continuous use, or /tpm once for one teleport. Open the map and place a new marker to teleport to its location. One-time mode automatically disables after teleporting. Use /tpm to disable continuous mode or cancel a pending one-time teleport. Commands Command Description /tpm Toggles marker teleporting. Also cancels a pending one-time teleport. /tpm once Enables teleporting for your next map marker, then automatically disables it. Permissions Permission Description teleportmarker.use Allows the player to toggle and use marker teleporting. Language Support All chat messages can be customised or translated through the plugin's language files. Keep placeholders such as {0} and {1} intact when editing messages. Good to Know Teleporting starts disabled for each player. Reloading the plugin or restarting the server resets all toggles. Destinations use terrain height; the plugin does not check for buildings or other obstacles. Dead or spectating players cannot teleport. These attempts do not remove the marker or consume a pending one-time teleport. Looking for more server tools? Browse more plugins by Bubbafett

Your server. Your guest list. Simple Whitelist is a free Rust plugin for Oxide and Carbon that lets you control who can join your server. Approve players by Steam ID or permission, manage the whitelist through console commands, and customise the message shown to anyone denied access. Ideal for private communities, testing servers, and invite-only events. Features Steam ID access — maintain a list of approved players. Permission-based access — optionally allow players to join through a permission. Separate management permission — let trusted staff manage the whitelist without giving ordinary whitelisted players administrative control. Console commands — add or remove players, view the list, check status, and toggle restrictions. Custom rejection message — explain why access was denied or tell players how to request entry. Saved changes — command-based changes are saved automatically. How It Works When the whitelist is enabled, a connecting player can join if: Their SteamID64 is in Whitelisted Steam IDs; or Use Permission is enabled and they have SimpleWhitelist.Allow. Both access methods can work together. Enabling permission-based access does not disable the Steam ID list. When the whitelist is disabled, Simple Whitelist does not restrict connections. Commands Run these commands from the server console, RCON, or an authorised player's F1 console. Do not add a / prefix. Replace <SteamID> with the player's SteamID64, without the brackets. Command Description whitelist.add <SteamID> Add a player to the Steam ID whitelist. whitelist.remove <SteamID> Remove a player from the Steam ID whitelist. whitelist.list Display the configured Steam ID whitelist. whitelist.toggle Enable or disable whitelist restrictions. whitelist.status Check whether the whitelist is enabled. Adding or removing players and toggling the whitelist automatically saves the changes. Permissions Permission Description SimpleWhitelist.Allow Allows the player to join when Use Permission is enabled. Does not grant management access. SimpleWhitelist.Admin Allows the player to use all whitelist management commands. Works independently of Use Permission. Server administrators and the server console can use management commands without the management permission. Management access does not bypass the connection whitelist. Administrators and players with SimpleWhitelist.Admin must still be approved through their Steam ID or the join permission. Configuration Setting Description Whitelist Enabled Enables or disables connection restrictions. Use Permission Enables SimpleWhitelist.Allow as an additional way to join. Kick Message Message shown to players whose connection is rejected. Whitelisted Steam IDs List of SteamID64 values approved to join. Version (DO NOT CHANGE) Plugin-managed configuration version. Leave this unchanged. Example Configuration This example leaves restrictions disabled while you set up your player list: { "Whitelist Enabled": false, "Use Permission": false, "Kick Message": "This is a private server. Please contact an administrator for access.", "Whitelisted Steam IDs": [], "Version (DO NOT CHANGE)": { "Major": 1, "Minor": 1, "Patch": 0 } } Reload the plugin after manually editing the configuration. Changes made through whitelist commands take effect immediately. Getting Started Install SimpleWhitelist.cs in your server's plugin folder. Review the generated configuration. From the server console or RCON, add your own SteamID64 using whitelist.add <SteamID>. Add the other players you want to allow. Run whitelist.status to check the current setting. If restrictions are disabled, run whitelist.toggle to enable them. Using Permissions To approve players through permissions: Set Use Permission to true and reload the plugin. Grant SimpleWhitelist.Allow to the players or permission groups you want to admit. Grant SimpleWhitelist.Admin separately to trusted staff who need whitelist management commands. You can continue using the Steam ID list alongside permissions. Good to Know Access is checked when players connect. Enabling the whitelist does not kick players already online. Removing a Steam ID affects future connections. It does not disconnect the player. Either access method can approve a player. Removing their Steam ID will not block them if they still have the join permission and permission-based access is enabled. The list command shows Steam IDs only. It does not list players approved through permissions. Looking for more server tools? Browse plugins by Bubbafett.