• Content Count

  • Joined

  • Last visited

Recent Profile Visitors

76 profile views
  1. If you can't trust your staff with Auth Level 1, then why should they be allowed to spectate at all? I understand if you want to keep your server locked down from admin abuse, but there are much more effective ways of allowing admins Auth 1 and preventing them from doing what you don't want them doing. I just don't see why anyone would put the time into a plugin that is a built-in command.
  2. Version 1.0.0

    1 download

    This is a script that can be used to automatically wipe your servers on a set schedule, changing either your seeds or level URL. You may need Administrator privileges on the system to setup & run this script depending on your server's setup. Files Batch script which turns on/off your server and deletes your chosen data/map/bp files Executable which will handle changing the seed/levelurl seeds.txt file which stores all your seeds/levelurls which will be randomly chosen every wipe (the name can be changed later) Requirements Rust Server(s) setup in a standard way on a Windows dedicated server. Administrator privileges on said Dedicated server. File editing software (Notepad++ works) Rust server(s) running as a service (you can use NSSM to set this up) Microsoft Visual C++ Redistributable Package (64 Bit, 32 Bit) How to Setup Open auto-wipe.bat Enter your server's service name Replace the example paths with the plugin and map file paths you want to be deleted on wipe Note: Using *.db will delete all .db files in the folder Open config.json in Notepad++ Replace the example server config path with your own server.cfg location Replace the example seed / txt file with the path of your own seeds.txt or levels.txt file (the name of the file does not matter) Note: Make sure to use double \\ just like in the example provided or it will not work! Optional: Change the value of replacement from server.seed to server.levelurl if you wish to change the server levelurl each wipe. Choosing your "Replacement" value This can be anything that you wish for the code to look for, but it is necessary that the seed or levelurl is the last thing on the line and it is separated by a space. For example, if you wanted to change something where the line started with +server.seed you can change the replacement property to match this. For most standard setups and usages, the default of server.seed will be sufficient. Open Task Scheduler in Windows Click Create Task Select "Run whether user is logged on or not" Select "Run with highest privileges" In the drop-down box select "Configure for Windows Server 2016" (may be different depending on server version) In the "Triggers" tab click "New..." and select your schedule In the "Actions" tab click "New..." and select the auto-wipe.bat file In the "Conditions" tab deselect any power options Populate your seeds.txt file If you're using levelurls, the same will apply just with different values Open seeds.txt (you may have called it something else) in Notepad++ Go to and search for some seeds using your map size. Put each seed or levelurl on a new line Save the file Perform a Dry-Run Whilst your server is online with no pop, manually run the auto-wipe.bat to ensure that it is working as expected. If not, please go through all of the steps again and make sure you read everything! It is very common to forget double backslashes in the config file, or to have a typo in one of your file paths. This is a general method to setup your auto wipes, each setup will be different so you must ensure you adapt and change ALL file paths to match your setup and desires. I cannot aid you in making your server into a service, though it is highly recommended for all servers to do so as it will make your setup safer and more relaible. There are numerous tutorials available on YouTube if you desire to do so. If you have time, and would like to help better this product, please fill out this form: you.


  3. Version 1.0.0


    Receive your Rust server's chat messages into your Discord server - no plugin installation needed! Tired of a Discord extension crashing your server? All it does is listen for chat messages over RCON and then post them to a specified Webhook. With a little bit of knowledge and trial-and-error, you could even have this working as an embed or change how it looks entirely. Whilst this product won't rid your server(s) fully of it, it'll make sure it gets used just that little bit less, and hopefully make it cause less crashes. This is a simple, free to use, free to modify script using my own WebRcon Package licensed under BSD 3-Clause. Usage Install Python3.8 Download & extract the ZIP file Using your favourite text editor open up and edit the following variables: ○ WEBHOOK_URL - This should be the webhook the code will post to ○ RCONHOST - The IP of your server ○ RCONPORT - The port that your server is listening to RCON on ○ RCONPASSWORD - The RCON password you specify in your .bat, .sh or .cfg file. Open some form of console and type python Fair Warnings This script has not been setup to dynamically adapt to Discord's ratelimits. If you feel like your chat goes at about 10 messages a second for more than 5 minutes at a time, do not use this. You will need basic programming know-how if you wish to edit this script effiiciently. Support is not guaranteed for this product, and is available solely at the discretion of the author. If you have multiple servers, you will have to run multiple instances of this script. If you are on Linux, you might want to learn how to use Tmux You must include the copyright notice and license (see the LICENSE file) in any and all redistributions of this code. Usage instructions do not account for the various nuances of different Operating Systems, and you must adapt the steps accordingly. See some of my other products for more detailed Python installation instructions. This has not been designed to be user friendly. It has been created and made available for those who feel like a small challenge.


  4. Version 1.0.3


    This is a script capable of controlling multiple bots from one program and with a single config file without ever connecting to your server over RCON. You may need Administrator privileges on the system to setup & run this script depending on your server's setup. Feature List Run multiple bots from the one script Change your config using the included "Config Editor & Generator" - no JSON knowledge needed! Lowest possible performance impact - there are no new RCON connections ever made to your server. Show players, max players, queued players, AND joining players! Threshold message - when your pop falls below XX%, show a different message such as your wipe schedule. Special variables that are replaced in your strings, allowing you to have any variable in any part of your pop bot's message. Global pop bots - add up the total players across your servers and show it on a dedicated bot! Detailed logging - always know what went on whilst you were gone. How does it work? This script works by querying the BattleMetrics API - even if you don't have a purchased RCON subscription! If you do, you'll be able to display the amount of players joining. Install (Windows) Your server will need to have Microsoft Visual C++ Redistributable Package installed, simply click the link to download the 64 bit variant. Method 1 - Installer, Windows Dedicated Server Download the Multi Pop Bot Installer ZIP file. Extract the ZIP file anywhere on your system Run the included .MSI, which is a Windows Installer File. You'll be able to choose where to install the script when you run this. Method 2 - No Installer, Windows Dedicated Server Download the Multi Pop Bot Raw Files ZIP file. Extract the ZIP file anywhere on your system Run the file run.bat Method 3 - No Installer, Alternative System Install Python 3.8, using the Recommended Installation and ticking Add Python to PATH. Download the Multi Pop Bot Raw Files ZIP file. Extract the ZIP file anywhere on your system Install necessary modules with pip install -U aiohttp websockets in console (cmd) Run python in console (cmd) Install (Linux) You will always require the raw files for Linux installs. Since Linux is a very broad term for OSes, it is possible that there is not yet any compiled code ready for your architecture. If the following instructions do not work for your architecture, please get in touch so I can compile them for your system & add them to the download. Method 1 - Generic Linux System Install Python3.8 on your system (you will have to search how to do this, as it is different for Ubuntu, Debian, Installs, Gentoo, etc) Install necessary packages using one of the following commands. If you are unsure which is the right command, you may have to try all of them or do a little read up on your installation. pip install -U aiohttp websockets pip3 install -U aiohttp websockets python3 -m pip install -U aiohttp websockets python3.8 -m pip install -U aiohttp websockets Run one of the following commands, depending on your system python python3 python3.8 Now that you have figured out which command runs the code, make yourself a new file called Using your favourite text editor (nano of course), you want to edit this file and setup an infinite loop to run the command you previously used to run the script. How to setup an infinite loop in a .sh file Run your .sh file Method 2 - Hosting Platforms All hosting platforms do things differently. You will need to use and make sure that it automatically restarts the script when it closes! This is needed because Discord occasionally kills the connection between themselves and your server, which causes the bot to no longer function. When this happens, the script will detect it and close itself automatically, allowing whatever is handling the execution of the code to start the script again. If you are asked which packages are required you need, aiohttp, websockets For Pterodactyl users, you will need to use a Discord bot egg which you can find with a quick search. The startup command will typically be python For Pebble users, you can simply use with Python3.8 and the appropriate packages. The Config Once you've installed the code, you should now be able to see in your selected directory that there is a "Config Editor & Generator" file. Run this and it will walk you through editing the configuration file. I strongly recommend you select "Create a New Config" when installing for the first time, so that you can select whether or not you want logging enabled, and add your own bots from scratch. When you are specifying the messages that will be displayed, you will be told that {{players}}, {{maxplayers}}, {{queue}}, {{joining}} will all be replaced on the bot. What this means is that if you want your bot's message to look like >150/150 (71 Queued)< you would need to enter >{{players}}/{{maxplayers}} ({{queue}} Queued)<. You can use this feature to customise your pop bots however you like. If you feel you are a bit more tech savvy than others, there is a folder examples that contains sample configs for you to read over, one even including a full description of each JSON key + value. Update Intervals During the creation of your pop bots, you may be asked what "Update Interval" you would like. If you are running more than 4 bots, it is recommended you increase your update interval appropriately so that you do not spam Discord's API - a quick way to get your server banned that a lot of Discord-related Rust scripts do not account for. Additionally, Discord will attempt to kill the connection a few times before banning you, which could result in crashes! Not to worry though, this script has been built to be as reliable as possible and will automatically restart itself if you follow the steps under "Running the Script". Thresholds The threshold feature will wait for your pop to fall under a set percentage (referred to as threshold in the config), and display an alternative message so that you do not have to display potentially embarassingly low pop to your Discord members. If this is something you are not worried by, simply set the threshold to 0 and it will never trigger. It is important to remember that the threshold is a percentage not a set value! A threshold of 10 and a max player count of 100 will only show the threshold when there are less than 10 players online. The message shown can be changed by altering threshold_msg in the config, or you will be asked to enter the text you wish to display when using the config editor. Joining Players If you would like to show the amount of players joining, it is absolutely necessary that you have a BattleMetrics RCON subscription purchased. You will be asked by the config generator if you would to create a Pop Bot with BM Token or Pop Bot without a BM Token - if you wish to display the players currently joining your server, choose the former. If you do not wish to show this or do not have a BM subscription, use the latter. Obtaining a Discord Bot Token First, head over to and create yourself an application. It'll most likely need your server logo, the name of the server, and any other information you wish for people to see appear. Once that's done, select the "Bots" tab and press create a bot. You'll be presented with "Click to reveal a token" and a button that reads "Copy". You can just press Copy and it's on your clipboard ready to insert into your config file. Obtaining a BattleMetrics API Token If you have purchased a BM RCON subscription, this is for you. Head over to You want to select "New Token". Fill in the identifier with something such as "Pop Bots" and ensure it has the "Execute any RCON command" permission. The rest aren't used at all, so whether or not you grant them or not are completely your choice. You'll have only one chance to copy this token somewhere safe (such as the config.json file), so make sure you do. Luckily for you, this one token will work with all of your pop bots, so don't worry about generating a new one for each bot (unless you really want to keep things nice and tidy). Running the Script At last, your configuration file is complete! You have probably noticed that there are 2 .bat files included. If you have NSSM installed you can use nssm.bat and run the pop bots as a service, then simply forget about them. If not, you can just double click run.bat and the bot will always restart itself no matter what issues it encounters. If the above does not apply to you, please see the installation section as it includes steps for running the script in more complicated environments.