Search the Community

AI Translation plugin is the best powered-AI translation solution for Rust Servers. Enjoy the power of AI by automatically translating all your language files, or the messages exchanged by players in the chat! ALL languages, without exception, are accepted. !! Important: The plugin requires the use of OpenAI's API, which includes fees for each request (see the dedicated section for more details) !! Free Version : A free version (but limited) is available. Easy to Use with Minimal Configuration There is almost no setup required; everything is straightforward to handle. Open AI & Request Costs You need to register for the OpenAI API to retrieve a token. Signing up and getting the token is very simple and takes just a few seconds. Translating language files will only cost a few cents for about a hundred files. It's difficult to quantify the cost of translating chat; expect around $1 for thousands of translated messages (this is a purely theoretical value). Something to consider if your language files are long: It is possible that some files may arrive incomplete. To solve this issue, you need to increase the token limit of your model (in the configuration). The limit depends on the OpenAI model used, but generally, you can go up to 4096. More information on tokens can be found here. Support Available I am available for all your questions, whether it's support here or on Discord (d.0ne_) More information at the bottom of the page. Commands ait.translateplugin <plugin> <lang1> <lang2>: Requires the plugin to have a default language file (in English). Specify all desired languages in ISO639-1 format. Example: "ait.translateplugin MyPlugin fr ru" ait.translateallplugins <lang1> <lang2>: Operates the same way but will do so for all plugins. Permission aitranslationpro.chat.use: permission that allows users to see the translation in the chat OPEN AI API Registration (2mn): 1 - Visit the OpenAI Website: Go to OpenAI's official website. Click on the "API" section in the navigation menu. 2 - Create an Account: If you don’t already have an OpenAI account, you will need to create one. Click on the "Sign Up" button. Fill in your details such as email, name, and password. Follow any additional prompts to complete the registration process. 3 - Verify Your Email: Check your email for a verification link from OpenAI. Click on the link to verify your email address. 4 - Log in to Your OpenAI Account: Once your email is verified, log in to your OpenAI account. Navigate back to the API section. 5 - Apply for API Access: Depending on OpenAI's current policies, you might need to apply for API access. Fill out any required forms or surveys. Submit your application. 6 - Access the API Dashboard: Once approved, you can access the API dashboard. This dashboard is where you can manage your API usage. 7 - Generate an API Token: In the API dashboard, look for an option to create a new API token. Click on "Create Token" or a similar button. Follow the prompts to generate a new token. 8 - Secure Your Token: Once your token is generated, make sure to copy it and store it securely. Never share your API token publicly as it gives access to your OpenAI account.

Everlight allows infinite light from configured objects without consuming or using any fuel resources. You can also enable no resource usage on furnaces and/or refineries by enabling them in the configuration file. "Barbeque","Camp Fire","Cursed Cauldron","Chinese Lantern","Stone Fireplace","Furnace","Large Furnace","Jack O Lantern Angry","Jack O Lantern Happy","Lantern","Skull Fire Pit","Small Oil Refinery","Tuna Can Lamp", "Hobo Barrel" Configuration The settings and options can be configured in the Everlight file under the config directory. The use of an editor and validator is recommended to avoid formatting issues and syntax errors. Credits Wulf, for the original version of this plugin **Arainrr **: Previous maintainer lukespragg: Previous maintainer

SAVE 13% WHEN BUYING THE BUNDLE This is a server management plugin. It allows you to have consistency and visibility over all the information related with your server, including it's basic configuration. You may find this valuable no matter if you manage ONE or TEN servers, it works great with automation tools, docker and alike. It has four main features: Wipe schedule calculator (support weekly, biweekly and monthly) Manages server information (Title, description, tags, logo, banner, etc) Manages the basic server configuration (cvars) Manages Oxide's groups, permissions and user membership. Loading messages when a player is joining and/or waiting in queue. Timed messages (adverts) Public chat command "!wipe" that will inform: Last wipe date Next wipe date The current time in UTC Support the new Nuclear Missile Silo computer countdown Support dynamic slots (increase total slots according to connected players) 1. Wipe schedule calculator The plugin provides four "tokens" that you can use within the server's title or description to inform your users when was the last wipe and when it will be the next wipe. You can customize the date format and wipe schedule on the config file and the wipe schedule calculator will have into account the Thursday forced wipe. // You can format the date as you'd like "Date": { "Short": "dd/MM", "Long": "dd/MM/yyyy" }, "Wipe": { "DoW": 4, "Hour": 19, "Timezone": "Europe/London", "Frequency": "BiWeekly" }, 2. Manages server information This one is pretty self-explanatory, it allows you to define all the metadata about your server. "Server": { "Name": "DEVELOPMENT SERVER | %LASTWIPE%", "Description": [ "Map size is %WORLDSIZE% using seed %WORLDSEED%.", "Last wipe was at %LASTWIPE_LONG%, Next wipe is at %NEXTWIPE_LONG%", "Server has %UPTIME% seconds uptime, running at %FPS% fps with %ONLINE%/%MAXSLOTS% players online." ], "Banner image": "https://assets.example.com/banner.jpg", "Logo image": "https://assets.example.com/logo.png", "Tags": [ "weekly", "vanilla" ], "Website": "https://example.com/", "Custom map name": "kasvoton was here", "Wipe schedule": 7 }, Notice the special feature "Custom map name" which allows you to customize the map name that is displayed on the server list (Procedural Map). This shows in not only at Rust's in-game server browser, but also all on all the other sites that show off your server, i.e. Battlemetrics. WE DO NOT REQUIRE OXIDE'S SANDBOX MODE TO BE TURNED OFF AS OTHER PLUGINS DO. 3. Manages the basic server configuration (cvars) It allows you to have a clear view of what cvars are applied, very helpful if you run automation tools such as docker or github to manage server configurations. "CVars": { "fps.limit": "32", "server.tickrate": "10", "server.censorplayerlist": "true", "server.maxplayers": "8", "env.time": "12", "env.progresstime": "false" }, 4. Manages Oxide's groups, permissions and user membership. When you define a group inside the plugin's config file it means that the plugin will make sure that the group is created, that the permissions are assigned and that the listed members are part of the group. You can (and should) assign users to your groups using the oxide's tools or any other third party plugin as usual, the only difference is that the members listed on this config file will always be added back to the groups even when manually removed. "Permissions": { "Delay": 60.0, "Groups": [ { "Name": "admin", "Title": "Administrators", "Parent": "developer", "Rank": 0, "Default": false, "Permissions": [], "Members": [] }, { "Name": "default", "Title": "Default", "Parent": null, "Rank": 0, "Default": true, "Permissions": [], "Members": [ "*" ] }, { "Name": "developer", "Title": "Developer", "Parent": "administrator", "Rank": 800, "Default": false, "Permissions": [ "plugin.e", "plugin.f" ], "Members": [ "123456789123456789" ] }, { "Name": "administrator", "Title": "Administrator", "Parent": "moderator", "Rank": 80, "Default": false, "Permissions": [ "plugin.b", "plugin.c", "plugin.d" ], "Members": [ "123456789123456789", "123456789123456789" ] }, { "Name": "moderator", "Title": "Moderator", "Parent": "default", "Rank": 60, "Default": false, "Permissions": [ "plugin.a" ], "Members": [ "123456789123456789", "123456789123456789", "123456789123456789" ] } ] } Note the important config parameter "Delay", when the server starts we have no way to tell in which order the plugins will get loaded by Oxide, which means that when OxidationMetadata loads it's probable that we will not be the last one getting loaded. If we try to assign a permission to a group but the third party plugin has not yet loaded then the permission is not found and we'll get an error. The "Delay" creates a waiting period for OxidationMetadata to wait for all other plugins to load and only then it tries to assign the permissions, the value of the delay is really dependent of your own server. List of supported string format "tokens": %FPS% Average FPS value on the server %MAXSLOTS% Max number of players on the server %ONLINE% Total number of online players %UPTIME% Server uptime in seconds %WORLDSEED% Seed used to generate the world %WORLDSIZE% World size i.e. 3500 %LASTWIPE% Last wipe date formatted in short form %LASTWIPE_LONG% Last wipe date formatted in long form %NEXTWIPE% Next wipe date formatted in short form %NEXTWIPE_LONG% Next wipe date formatted in long form

Say goodbye to configuration and data files. This plugin lets yo edit the loot of (almost) every lootable object directly over a custom UI. It also includes a graphical stack size editor thus making it ideal for anyone who is not familiar with editing config files. Do not use in combination with any other stack size controller or loot plugin. Features: User friendly GUI - no need to edit config files Loot configuration for every prefab in the game Stack size controller supports individual stack sizes for every prefab Support for custom items Support for third party plugins Fully backwards compatible with version 1.x.x Default config included for every prefab Configuration for Smelting Speed, Recycler Speed and Efficiency Supply Drop configuration Supported prefabs: Crates, Barrels NPCs Trees, Ores, Animal corpses Excavator, Quarries Christmas Presents, Eggs, Loot Bags Collectables like Hemp, Corn, etc. Additional Configuration: Smelting Speed Supply Drop Recycler Speed / Efficiency Commands: loottable - Open the Loottable UI loottable reload - Manually refresh loot Permission: loottable.edit - Required to use the Loottable UI Required Dependencies (Oxide only): Image Library: https://umod.org/plugins/image-library Translations: This plugin fully supports translation. Out of the box only english is included. For item names to be translated, the plugin https://umod.org/plugins/rust-translation-api is required. English translations are located in /oxide/lang/en/Loottable.json For Developers: Loot Api: Developers can use the Loot Api to register loot profiles for custom NPCs or other plugin related loot. It is highly recommended to use one of the provided wrappers to access the api. Both wrappers offer the same functionality. Non-static (with documentation): https://gist.github.com/TheKiiiing/53a37e8bbb48d8a24c8e8b21b9da37ac Static (with documentation): https://gist.github.com/TheKiiiing/77ee60fa5d23934fd138fde58a2b147f Loot Api Example: // This example uses the non-static version of the Loot Api private LoottableApi loottableApi; void OnServerInitialized() { loottableApi = new LoottableApi(this); timer.In(5f, () => { loottableApi.ClearPresets(); loottableApi.CreatePresetCategory("Crates"); loottableApi.CreatePreset("c_locked", "Locked Crate", "crate_hackable"); loottableApi.CreatePreset("c_elite", "Elite Crate", "crate_elite"); loottableApi.CreatePreset("c_military", "Military Crate", "crate_military"); loottableApi.CreatePreset("c_normal", "Normal Crate", "crate_normal"); loottableApi.CreatePresetCategory("NPCs"); loottableApi.CreatePreset(true, "npc_cargo", "Cargo Ship NPC", "npc_militunnel"); loottableApi.CreatePreset(true, "npc_control", "Control Center NPC", "npc_militunnel"); }); } void SpawnNpc() { // Spawn NPC here ScientistNPC npc; // Assign a loot preset to the NPC loottableApi.AssignPreset(scientist, "npc_control"); } void SpawnCrate() { // Spawn crate here LootContainer crate; // Assign a preset to the crate if (loottableApi.AssignPreset(container, "c_locked")) { // The container has been filled with loot return; } else { // The container is not handled by Loottable // Default loot logic goes here } } The resulting configuration page would look like this: Custom Items API: Developers can use the Custom Items Api to add a custom item to the Loottable item list. If an item is marked as persistent it will remain in the custom item list until it is removed by ClearCustomItems. All non-persistent items will be removed after the plugin that registered them has been unloaded. (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, bool persistent) //(v1.0.27 or higher) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName, bool persistent) //(v1.0.27 or higher) (void) ClearCustomItems(Plugin plugin) //(v1.0.27 or higher) Hooks: (object) OnContainerPopulate(LootContainer container) This hook is called every time a loot container is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that crate. (object) OnCorpsePopulate(LootableCorpse corpse) This hook is called every time an npc corpse is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that corpse. (object) OnCustomAirdrop(SupplySignal signal) This hook is called every time a custom supply drop is about to be delivered. Returning a non-null value will cancel the custom supply drop. Outdated documentation for Version 1: New with version 1.0.27: Custom Items can now be created and edited directly in the GUI. They can be created from any existing item and modified in the Item Select menu You can now create and load backups of your configuration. Commands (F1 or Server Console): loottable.backup load <name> - Load backup with the given name from the backups folder (will wipe your current configuration) loottable.backup create <name> - Create backup of everything with the given name Backups will be created in the data/Loottable/backups folder. To load a backup, the backup file needs to be present in that folder. When creating backups in the in-game console, the permission loottable.debug is required. IMPORTANT: DO NOT LOAD BACKUPS FORM SOURCES YOU DO NOT TRUST, they might cause harm to your server New with version 1.0.16: Custom Items: Now you can add custom items used by other plugins directly to your loot table. Other plugins can can register these items using the api (documentation below). Screenshots: Overview of crates and their current loot table Stacksize Editor Commands: loottable - Open the editor loottable refresh - Manually refresh crate loot loottable flags - List available flags (explained below) loottable flags <name> <1|0> - Enable / disable a certain flag loottable reload_vanilla_profiles - Manually re-download vanilla loot profiles (only for debuging) Permission: loottable.edit - Required to use the editor Flags: There are flags to disable some limits in the editor. Only enable these flags if you really need to as they might cause unexpected behavior of the editor. There are currently 3 flags available: Debug If enabled, the Debug flag provides more detailed information about errors and other actions in the editor. Don't enable this flag unless you want your console full of spam. UnlockGatherMultiplier allows you to use gahter multipliers less than one and higher than 1000. Note that multipliers less than one might lead to unexpected results in some cases. DisableItemLimit Probably the safest flag to use is DisableItemLimit as it simply lets you set stack sizes and every other item amount in the editor as high as 2,147,483,647 which is the biggest possible value of a 32-bit integer. UnlockFurnaceMultiplier lets you use any value as the furnace speed multiplier. Don't enable this flag unless you know what you are doing, since the default value range from 0.1 to 100 should cover most use cases and larger values might impact server performance. UnlockItemMultiplier unlocks the multiplier when multiplying a loot table. DisableStackingHooks will disable all stacking related hooks. Enable if you encounter problems when stacking items. RefreshLootOnExit controls if all crates get refreshed after closing the editor or when reloading the plugin. Enable this only for testing, there might be an increase in entities. Refer to the Commands section for more information about enableing flags. Vanilla Configurations: Since version 1.0.7 there are vanilla loot profiles available for most crates and NPCs. These profiles can be loaded using the "Load default loot table" button at the top center of the editor. DISCLAIMER: The vanilla loot profiles in the editor might not exactly match the vanilla loot distribution of the game as it uses a completely different loot distribution system than Rust. These profiles rather serve as a reference point for custom loot profiles. Important for Carbon users: In order for this plugin to work with carbon, Harmony references need to be enabled. This can be done with the following command: c.harmonyreference 1 Required Dependencies (Oxide only): Image Library: https://umod.org/plugins/image-library Custom Items API: Add a custom item to the item list. If an item is marked as persistent it will remain in the custom item list until it is removed by ClearCustomItems. All non-persistent items will be removed after the plugin that registered them has been unloaded. (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, bool persistent) //(v1.0.27 or higher) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName) (void) AddCustomItem(Plugin plugin, int itemId, ulong skinId, string customName, bool persistent) //(v1.0.27 or higher) (void) ClearCustomItems(Plugin plugin) //(v1.0.27 or higher) Example: Its recommended to delay the call a little bit to make sure Loottable is loaded private void Init() { timer.In(1f, () => { Loottable?.Call("AddCustomItem", this, -946369541, 2664651800, "High Quality Fuel"); }); } Hooks: (object) OnContainerPopulate(LootContainer container) This hook is called every time a loot container is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that crate. (object) OnCorpsePopulate(LootableCorpse corpse) This hook is called every time an npc corpse is about to be populated with loot. Returning a non-null value prevents the plugin from spawning loot into that corpse. (object) OnCustomAirdrop(SupplySignal signal) This hook is called every time a custom supply drop is about to be delivered. Returning a non-null value will cancel the custom supply drop.

Vanilla LootTable example for use with BetterLoot includes min and max amount of each item to spawn per container and min and max items to spawn per container.

RUST AUTO WIPER Rust auto wiper is an advanced but simple-to-set-up Discord bot that makes your server wipes 100% automated! Features: 100% automates the server wipe process. Start map votes for the next wipe automatically. Manage wipes of as many servers as you need. Dynamically update server details on the wipe. (ex: server title, description) Deletes a selection of files and folders on the wipe. (ex: plugin data files) Sends wipe announcements. Updates server on the wipe. Set up wipe reminders. Information: This advanced server wipe system covers 100% of the wipe cycles on all your servers. The real power of this tool is that it's running separately from the server, this makes managing server files much easier when the server is offline. with this tool, you don't need batch files or other crap to get your server(s) wiped. This tool also uses cron intervals to determine the exact wipe dates and times. *Note: This tool must be run on a Windows VPS/Server* Configuration: (This example shows 1 server, but you can set up as many servers as you want) module.exports = { token: '', // Your Discord bot token rustMapsApiKey: '', // the rustmaps.io api key guildId: '984577959648174121', // the id of the discord server you want to use the bot in logChannelId: '1102195648683585616', // the id of the channel where the bot should log all actions dbdAccountId: '', // your dbd account id (get this by typing /license display in the support server) debugMode: true, // if true, the bot will log all actions to the console servers: [ // in this list your can add as many servers as you need { server_identifier: 'server1', // the unique identifier of the server. (used for internal purposes) server_name: 'Test Server', // the name of the server server_ip: '', // the ip of the server server_port: 28015, // the port of the server server_queryPort: 28017, // the query port of the server server_rconPort: 28016, // the rcon port of the server server_rconPassword: '', // the rcon password of the server server_modded: true, // if the server is modded or not (if plugins are used) wipe_Interval: '0 20 19 1/1 * ? *', // the interval of the wipe. (generate interval at http://www.cronmaker.com/) wipe_bpWipe: false, // if the wipe is a bp wipe or not files_serverRootPath: 'C:\\Users\\user\\Desktop\\rsmtesting', // the path to the main server folder. (where your start.bat is located) files_savesFolderPath: 'C:\\Users\\user\\Desktop\\rsmtesting\\server\\rsm', // the path to the saves folder. (where your map file is located) files_serverCfgPath: 'C:\\Users\\user\\Desktop\\rsmtesting\\server\\rsm\\cfg\\server.cfg', // the path to the server.cfg file files_startFilePath: 'C:\\Users\\user\\Desktop\\rsmtesting\\start.bat', // the path to the start.bat file files_oxideFolderPath: 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide', // the path to the oxide folder files_excludeSafeFiles: ['logs', 'cfg', 'Log.EAC.txt'], // save files that should not be deleted on wipe. (always exclude cfg) files_deletables: [ // file paths that should be deleted on wipe. (use absolute paths) 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide\\data\\Shop.json', 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide\\data\\Referrals.json', 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide\\data\\StaticLootables_data.json', 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide\\data\\VanishPlayers.json', 'C:\\Users\\user\\Desktop\\rsmtesting\\oxide\\data\\Kits', ], vote_autoStart: true, // if the vote should start automatically vote_channelId: '1098325670687416331', // the id of the channel where the vote should be posted vote_StartAt: '0 0 19 1/1 * ? *', // the interval when the vote should start. (generate interval at http://www.cronmaker.com/) vote_endAt: '0 10 19 1/1 * ? *', // the interval when the vote should end. (generate interval at http://www.cronmaker.com/) vote_maps: ['1000_1', '1000_50000', '1000_1000'], // the maps that should be voted for. (always format the map name like this: 'mapSize_mapSeed') vote_mapCount: 3, // the amount of maps that should be voted for. the maps from the list will be randomly selected vote_multiple: true, // if players can vote for multiple maps update_dynamicTitle: true, // if the title should be updated dynamically update_serverTitle: 'Test Server wiped on {wipeDate} test1', // the title of the server. placeholders: {wipeDate} update_dynamicDescription: true, // if the description should be updated dynamically update_serverDescription: 'Test Server wiped on {wipeDate} test1', // the description of the server. placeholders: {wipeDate} // embed placeholders: {serverName} {mapSeed} {mapSize} {mapImage} {mapUrl} {wipeDate} {nextWipeDate} {nextBpWipeDate} {nextVoteDate} announcement_autoAnnounce: true, // if the announcement should be posted automatically after a wipe announcement_channelId: '1098325694930497607', // the id of the channel where the announcement should be posted announcement_content: '@ ping roles', // the content of the announcement. (can be used to ping roles) announcement_embedTitle: '{serverName} just wiped!', // the title of the embed announcement_embedDescription: '**Join Server:**\nSteam: steam://connect/{serverIp}:{serverPort}\nF1: `client.connect {serverIp}:{serverPort}`\n\n**Planned:**\nNext wipe: {nextWipeDate}\nNext BP wipe: {nextBpWipeDate}\nNext vote: {nextVoteDate}\n\n**Map:** [rustmaps.com]({mapUrl})', // the description of the embed announcement_embedColor: '#038CB5', // the color of the embed. (must be a hex color) announcement_embedImage: '{mapImage}', // the image of the embed announcement_embedFooterText: 'Server just wiped!', // the footer text of the embed announcement_embedFooterIcon: '', // the footer icon of the embed announcement_embedThumbnail: '', // the thumbnail of the embed announcement_embedAuthorName: '', // the author name of the embed announcement_embedAuthorIcon: '', // the author icon of the embed announcement_embedUrl: '', // the url of the embed reminder_autoRemind: true, // if the reminder should be posted automatically before a wipe reminder_Interval: '0 15 19 1/1 * ? *', // the interval when the reminder should be posted. (generate interval at http://www.cronmaker.com/) reminder_channelId: '1098325694930497607', // the id of the channel where the reminder should be posted reminder_content: '@ ping roles', // the content of the reminder. (can be used to ping roles) reminder_embedTitle: '{serverName} is about to wipe!', // the title of the embed reminder_embedDescription: 'Make sure to vote for the next map!', // the description of the embed reminder_embedColor: '#038CB5', // the color of the embed. (must be a hex color) reminder_embedImage: '', // the image of the embed reminder_embedFooterText: 'Server is about to wipe!', // the footer text of the embed reminder_embedFooterIcon: '', // the footer icon of the embed reminder_embedThumbnail: '', // the thumbnail of the embed reminder_embedAuthorName: '', // the author name of the embed reminder_embedAuthorIcon: '', // the author icon of the embed reminder_embedUrl: '', // the url of the embed }, ], }; Support: You can get support at my Discord server by clicking HERE!

x5 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

x100 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

This is a free version of the AITranslation plugin. It enables you to translate all the language files of your plugins into any desired language with a simple command. Limited Features in Free Version In this version, features are limited, and you only have access to file translations. Visit the AITranslation Pro page if you wish to obtain the version without limitations. Commands: ait.translateplugin <plugin name> <lang>: If the plugin has a default language file (in English), a translated version in the desired language will be created. (For lang, use the ISO639-1 format) The PRO version allows translating into multiple languages with a single command and translating ALL your plugins with one command. AITranslation PRO Version:

Hassle free setup. Takes less then 10 minutes to install. Removing countless hours of work instantly. Whats included? + BETTER CHAT - v2.2.78 + TRADE - v1.2.44 + BETTER LOOT - v3.5.8 + AUTO AUTHORIZATION - v1.3.3 + QUICK SMELT - v5.1.5 + GATHER MANAGER - v2.2.78 + NO ESCAPE - v2.1.35 + CLANS - v0.2.6 + STACK SIZE CONTROLLER - v4.1.2 + ALWAYS DAY - v1.0.1 + SPAWN MINI - v2.5.0 + RECYCLER SPEED - v2.0.2 + NTELEPORTATION - v1.7.8 + VANISH - v1.8.0 + REMOVER v4.3.41 + MORE! Server Feautures: - 2X Gather Rates. - All loot tables are perfectly balanced. - Players can teleport with a simple command if they are not combat or raid blocked. - Users with admin permissions will be able to vanish and moderate other players. - Time set to Always Day. Can change to your liking. - Clans, Recycler speed, & Remover tool. - And so many more features..... Not all plugins have to be used. You can modify all plugins to your exact liking if you wish. All of the items above are modified for 2x server.

This file provides instant setup for "ServerRewards" plugin. This configuration is for the free shop plugin on uMod saving yourself time, money, and the hassle of adding every item manually. Requirements: https://umod.org/plugins/server-rewards How to install: 1. Install Server Rewards from umod. 2. Place Server Rewards in plugin folder. 3. Load Server Rewards in your server. "o.reload ServerRewards" 4. Delete current data file. "Rewards_Data" (Oxide>Data>ServerRewards). 5. Unzip and place new file in its place. 6. Reload plugin, "O.reload ServerRewards".

500+ SKINS (INSTANT) This package includes a config file with access to 500+ skins for the free plugin: https://umod.org/plugins/skins Save yourself 10's of hours of compiling rust skins manually. No "SkinBox" needed. How to install: 1. Install free "Skins" plugin from umod. 2. Load plugin on server. "O.reload Skins". 3. Go to Oxide>Config and delete current configuration file for skins. 4. Unzip the 500+ Skins file. Upload the file to config folder. 5. Once again, reload the plugin. "O.reload Skins". 6. All done, Use /Skins to view usable skins.

x15 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

x10 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

x3 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

x2 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

x1 Optimized Loottables! all Loot Tables have been stripped of all junk and useless items to make the looting experience a little more enjoyable. So exactly what every server needs. if you want to have an individual table created or you don't like something don't hesitate to contact me REMOVED/ADDED Changelog: -balanced High tier loot (bradly,heli etc) -added revolver & pistol ammo to low tier crates -removed junk from high tier loot crates/events -balanced low tier loot (radtown,barrels etc) -lowered electrical loot by -1 per container 2.0 UPDATE -removed all electrical loot -removed all clothing -balenced mid tier loot -balanced low tier loot -balanced high tier loot

This plugins allows you to fine tune the settings about the Airdrop event such as frequency, speed, cargo drop mass and speed. To control the frequency, you can define a max and min duration between each airdrop event. If you don't want any randomization, just set the max and min with the same value. "AdditionalEvents": { "Enabled": false, "Min": 300.0, "Max": 600.0 }, The following config controls the "delay" between the start of the airdrop event (either it is server wide or called in by an user) and the drop of the cargo at the spot. In a nutshell it will make your planes fly must faster aka airspeed. "Airplane": { "Speed": { "Enabled": false, "Min": 70.0, "Max": 80.0 } }, You can change the duration of the supply signal smoke. "Signal": { "Duration": 110.0 }, Finally you can also adjust the time it takes for the dropped cargo to reach the ground by changing it's mass and drag values. "Cargo": { "Mass": { "Enabled": false, "Min": 20.0, "Max": 20.0 }, "Drag": { "Enabled": false, "Min": 2.5, "Max": 3.5 } }

StructureUpgrade allows players to upgrade entire structures, regardless of size, quickly, efficiently and securely using as much of Rust's code as possible to maintain stability. StructureUpgrade was built for performance from the ground up, and resolves many issues in free alternatives such as exploits, client & server crashes, and extreme lag. In addition, due to issues a lot of plugins suffer from, I offer a 6 month support guarantee with maximum 7 day turnaround (including for updates to fix the plugin if functionality is lost due to updates) for all support handled through Codeflings support system. If I can't get the plugin into a working condition or provide a reasonable level of support through Codeflings support requests within 7 days, I'll refund what you paid for the plugin if within the 6 month guarantee period. Support is provided in many places other than Codeflings support system, and I encourage everyone to ask on the forums or our discord first for the fastest response times. Click here to join my discord. Features Upgrades entire buildings, regardless of size, without causing lag in batches. Determines upgrade costs, handles taking costs from player inventory, dominating tool cupboard, and soon, storages inside the structure. Several checks ensure payment is taken correctly, and when refunding is added even more checks will be implemented. Resumes upgrading efficiently where it left off after a server crash or plugin reload. Supports a virtually infinite queue with optimized queue storage, jobs are stored and tracked in a data file and worked one at a time. Players are notified when their job starts. Unlike the simpler free alternative this plugin is optimized to prevent crashing on upgrading large structures, optimized to eliminate server lag, only a small frame drop for players looking at the structure. Uses Rusts existing building system rather than a janky, laggy alternative. We don't to build lists of entities because Rust already maintains that for us. We're just manipulating and using that information. Free alternative has an exploit allowing players to unintentionally upgrade nearby structures that aren't theirs, StructureUpgrade resolves that issue. Permissions structureupgrade.admin - Allows the player to upgrade structures without being authenticated on the tool cabinet. structureupgrade.free - Allows the player to bypass the upgrade costs when upgrading. They still must be authenticated on the tool cabinet. structureupgrade.up - Allows the player to use the /tc command. structureupgrade.uptc - Allows the player to use the /uptc command. structureupgrade.ups - Allows the player to use the /ups command. structureupgrade.norefund - Disables refunding cost when using /down for that player. Chat Commands Up Command Adds an upgrade job to queue after verifying and taking payment from the players inventory. Usage: /up {NewGrade} Usage Example: /up 2 (Upgrades structure to Stone Tier) Parameters NewGrade - What grade you'd like to upgrade to. 0 = Twig, 1 = Wood, 2 = Stone, 3 = Sheet Metal, 4 = High Quality Conditions For Use If using NoEscape Plugin - Player is not currently RaidBlocked. Provided NewGrade variable is inside supported range; currently 0 - 4. Command is run by a player. Player is inside building privilege. Player is authenticated on dominating tool cabinet, or has permission structureupgrade.admin. Player has upgrade costs in inventory, or has permission structureupgrade.free. Down Command Adds an downgrade job to queue after verifying and refunding cost to the players inventory. (Disable refund by giving player structureupgrade.norefund permission) Usage: /down {NewGrade} Usage Example: /down 2 (Downgrades structure to Stone Tier) Parameters NewGrade - What grade you'd like to downgrade to. 0 = Twig, 1 = Wood, 2 = Stone, 3 = Sheet Metal, 4 = High Quality Conditions For Use If using NoEscape Plugin - Player is not currently RaidBlocked. Provided NewGrade variable is inside supported range; currently 0 - 4. Command is run by a player. Player is inside building privilege. Player is authenticated on dominating tool cabinet, or has permission structureupgrade.admin. Player has space for refunded resources in main inventory, or has permission structureupgrade.norefund. UpTc Command This command functions like /up except payment is taken out of the dominating tool cupboard. Usage: /uptc {NewGrade} Usage Example: /uptc 2 (Upgrades structure to Stone Tier) Parameters NewGrade - What grade you'd like to upgrade to. 0 = Twig, 1 = Wood, 2 = Stone, 3 = Sheet Metal, 4 = High Quality Conditions For Use If using NoEscape Plugin - Player is not currently RaidBlocked. Provided NewGrade variable is inside supported range; currently 0 - 4. Command is run by a player. Player is inside building privilege. Player is authenticated on dominating tool cabinet, or has permission structureupgrade.admin. Player has upgrade costs in inventory, or has permission structureupgrade.free. UpS Command Upgrades the structure, takes payment from storages attached to the structure. Usage: /ups {NewGrade} Usage Example: /ups 2 (Upgrades structure to Stone Tier) Parameters NewGrade - What grade you'd like to upgrade to. 0 = Twig, 1 = Wood, 2 = Stone, 3 = Sheet Metal, 4 = High Quality Conditions For Use If using NoEscape Plugin - Player is not currently RaidBlocked. Provided NewGrade variable is inside supported range; currently 0 - 4. Command is run by a player. Player is inside building privilege. Player is authenticated on dominating tool cabinet, or has permission structureupgrade.admin. Player has upgrade costs in building storages, or has permission structureupgrade.free. Configuration Default Configuration { "BatchSize": 1, "AllowUpgradeFromTc": true, "AllowUpgradeFromStorages": true, "UpgradeFrequency": 0.025, "HidePrefixWithPluginNameInMessages": false } AllowUpgradeFromTc - If enabled the /uptc command is registered, if disabled /uptc is not registered and will result in an unknown command error. AllowUpgradeFromStorages - If enable the /ups command is registered, if disabled /uptc is not registered and will result in an unknown command error. BatchSize - Determines how many building blocks are upgraded every UpgradeFrequency. WARNING! :: Increasing this value does considerably reduce time to upgrade a structure. However for every 1 (one) increment players in the area will see a reduced 15 fps average. Setting this to 3 may kill fps by up to 30 in addition to the normal 20 or so. It is strongly recommended to modify UpgradeFrequency instead. HidePrefixWithPluginNameInMessages - If enabled the [StructureUpgrade] branding is removed from all player communications, as this is attached programatically rather than through the lang file. UpgradeFrequency - This is the frequency in fractions of a second that upgrades structures (quantity defined by BatchSize). This is optimized by default, lowering it too far will still cause lag. By default 1 block is upgraded every 25ms, or 0.025 seconds. For Developers Currently no API or Hooks exposed. This will be changed in the future, suggestions welcome. Future Features Want a feature not listed? Please suggest it as I'd love to continue expanding and increasing on the already substantial feature sets of StructureUpgrade. Command Aliases (in configuration) Logging all usages with statistics to log file Additional payment and block statistics to aid in future refunding functionality and abuse protection /upundo command to undo an upgrade. GUI in inventory screen detailing cost and duration, with buttons for grade and upgrade. Partial upgrades. Changeable chat icon. FAQ Where can I get support and interact with the community & developer? Codefling provides a support and discussion tab that's perfect for that. Additionally you're welcome to join my discord for faster more direct support: Click here to join! What checks are conducted to prevent abuse when upgrading? There are a few checks in addition to the checks defined for each command in the commands section above. Does the building block still exist? Is the building blocks grade higher than desired value? Skip.

The plugin gives ability to admins to create several configs for other plugins, and update them automatically depending on time passed since last wipe. Examples Example 1 You have loot spawn plugin, and you want that after two days from last wipe, loot spawn rules to be changed (more loot, or less loot). Example 2 You want no NPCs in your server at all in first 10 hours after wipe, and then part of NPC appear, and make after 2 more days, many more NPC should appear. How It Works Main Flow On load the plugin scans it's data directory, and detects last wipe. Checks if any of configs should already be applied (last ones that closer to current time). Once a minute it checks if some configs should be updated. Update Process Target plugin is unloaded. Its config is replaced. Target plugin is loaded again. Localization The default messages are in the DynamicConfig file under the oxide/lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages. The default messages are in the DynamicConfig file under the oxide/lang/en directory. To add support for another language, create a new language folder (e.g. de for German) if not already created, copy the default language file to the new folder and then customize the messages. Plugin uses only console messages to RCON. They could be localized. Out of the box the plugin supports EN localizations. Usage If you want to add any dynamic config, you should do these steps: Copy plugin config to oxide/config/DynamicConfig directory the DynamicConfig must be manually created. Edit the config name to meet naming syntax (below). Edit the config itself to meet your needs. Reload Dynamic Config if you're done. You can edit dynamic configs contents without reloading Dynamic Config (if they are yet to be applied), the plugin only reads the filenames and schedules the update time. Naming [] - optional [<number>d][<number>h][<number>m]<PluginName>.json Examples 2dMagicLoot.json - will be applied after 2 days from last wipe (exactly 48 hours) 10h20mTestConfig.json - after 10 hours and 20 minutes 10d10hBotSpawn.json - guess yourself