VinniTV's Wishlist

This customization allows you to change out the icons for Server Hud to these amazing customized ones. Make your server feel refreshed and different from many other servers running Server Hud! I've designed these icons for my server, and they are intended for use with the plugin I've linked above, which is essential for their functionality.
 
Notes before buying:
These are just the png images, you must upload them and replace the link for the icons found in the Server Hud config.
 
Icons Available:
Space Event (X-Wing or Saturn) Harbor Airfield Gas Station Event Junkyard Event Power Plant Event Shipwreck Arctic Research Event (x3  because I couldn't decide) Satellite Dish Event WaterEvent (x3 Different versions) DefendableBases  (x2  Different versions) WaterPatrol Event HeavyCargo Event PlaneCrash Event  (x2  Different versions) Dangerous Treasures Air Event (x2  Different versions) Meteor Event FishingHotspot ArmoredTrain PookEvent Triangulation Supermarket Event   Caravan   Military Airfield Event Watertreatment Event(x2  Different versions) Flying Cargo Ship Event Ferry Terminal Event Paintball Event Survival Event TrainYard Event MissleSilo Event (x2  Different versions)

This plugin allows for your players to receive or purchase personal recyclers that they can place inside of their base.
The primary benefit of this plugin vs other similar plugins, is that this plugin will restrict usage of the recyclers to only a user or their team (configurable), and has commands built in that will allow players to purchase it directly via payment gateways like Tebex etc.

It will also work with the VIP Token plugin, allowing for a token to be purchased and traded in game, providing the consumer with a redeemable recycler.
 
The plugin itself is fairly straight forward - players type the command into chat, which will provide them with a recycler item. This item is a reskinned box, and will be placed using the box prefab, but once deployed, it will spawn a recycler in with the same positioning as the box, then despawn the box. Recyclers can also be picked up using a hammer or toolgun by pressing mouse 3.

Features
Automatically clears data on map wipe. Allows players to keep their unredeemed recyclers between wipes (configurable). Prevents other players from accessing the recycler (configurable). Team mate support (configurable). Configurable starting amount of recyclers. Additional recycler(s) are accrued upon a map wipe, if the player had not redeemed their recycler (configurable). External payment gateway support, allowing for you to sell individual recyclers to your players. VIP Tokens support. Check below for the configuration example. Can pick up own recyclers using your hammer/toolgun and mouse 3. Recyclers will lost max condition each time they are picked up to prevent players from deploying them while grinding the roads (configurable).  
Permissions
personalrecycler.use personalrecycler.admin personalrecycler.place  
personalrecycler.use commands
/recyclers - will print out how many recyclers a player has left to redeem. /redeemrecycler - will spawn a recycler in the players inventory and deduct a recycler from their redeemable count. /crecycler - Will pickup the targeted recycler (requires a hammer to be wielded) if the player has permission. Players with this permission will automatically get the configured number of starting recyclers upon using the commands for the first time, and will have have recyclers added to their redemption pool at the start of each wipe (configurable).
 
personalrecycler.admin commands
/addrecycler <player name> - will increase the amount of redeemable recyclers a player has by 1. /clearrecyclers <player name> - will remove all of the saved recycler IDs from the data file, making all of their recyclers publically accessible. /clearrecyclerdata - removes all of the saved recycler IDs from the data file, making all recyclers publically accessible. (Console command) subtractrecycler <target> <optional: amount> - removes recyclers from the players available recyclers pool.  
API
This plugin allows for you to add a command to a payment gateway such as Tebex, or via   my VIP Tokens plugin.  
The command is structured as below:
addrecycler <Steam ID> <quantity> Most payment gateways required the player to log in with their steam ID. An example command using tebex would be:
addrecycler {id} 1 This would add 1 recycler for the steam ID of the account that logged into Tebex.
You can also add this as a VIP Token. See configuration options below:
"recycler": { "name": "Personal Recycler", "days_to_add": 0, "vip_group": null, "vip_description": "Allows you to place a personal recycler that only you can access.", "remove_tokens_on_wipe": false, "token_item": { "name": "Recycler Token", "skin": 2544601457, "item_shortname": "radiationresisttea.pure" }, "_command": { "command": "addrecycler {id} 1", "message": "You redeemed a recycler token.", "public_message": null, "hook": false } } As you can see, the command follows Tebex's variable style, using {id} to capture the players steam ID.  
 
If you require help setting this up with VIP Tokens, or need any assistance with anythign else, feel free to send me a PM.
 
Enjoy!

Introducing Linking System, the ultimate Discord integration plugin for your Rust server! Seamlessly connect your players Rust accounts with their Discord profiles, automatically assign roles, and reward linked players with exclusive perks. With a beautiful UI, complete Discord bot solution, and powerful automation features, Linking System is the perfect tool to enhance your community engagement and keep your Discord server active.
 

 
⭐️ Features of Linking System
Complete Discord integration system with automatic role assignment for linked players, enhancing community engagement and server security. Beautiful, customizable UI with ServerPanel V1 and V2 template support for seamless integration with your existing server interface. Secure code generation system with configurable cooldown periods to prevent abuse while ensuring smooth linking process. Automatic permission group assignment for linked players with customizable UI elements displaying potential benefits and server perks. Complete Python Discord bot included with comprehensive installation guides for Windows, Linux, and Pterodactyl hosting platforms. Multi-server support allowing one Discord bot to manage linking across multiple Rust servers simultaneously. Automatic group management with configurable group assignment for linked players, perfect for permissions and role-based systems. Real-time synchronization between Discord and Rust server through RCON communication for instant updates and status changes. Data persistence with automatic saving and loading of linking data, ensuring no loss of player connections across server restarts. Plugin integration support with ImageLibrary, ServerPanel, and Notify plugins for enhanced functionality and user experience. Developer-friendly API for custom integrations, allowing other plugins to check linking status and trigger custom actions. Comprehensive notification system with support for multiple notification plugins to keep players informed about linking status. Flexible interface options with configurable UI settings - use "Use UI" set to false for command-only operation without graphical interface.  
🤖 Complete Discord Bot Solution
LinkingSystem includes a complete Python Discord bot with everything you need for seamless integration. No complex setup required - just follow our step-by-step guides!
⚠️ Important: Python 3.12 is required! Python 3.13 is not compatible due to library issues.
🖥️ Windows Installation Complete guide for Windows servers with automatic startup configuration and service management. 🐧 Linux Installation Full Linux support with systemd service configuration for Ubuntu, Debian, CentOS, and RHEL systems. 🦕 Pterodactyl Support Optimized for Pterodactyl game panel with dedicated setup instructions and panel integration. 🔗 Multi-Server One bot can manage multiple Rust servers simultaneously with individual RCON configurations.  
📬 Video Overview 
 
🎮 Commands
/link - Opens the linking interface for players to connect their Discord account /link status - Shows your current linking status with Discord /link code - Generates a new linking code for Discord connection /link remove - Removes the existing link between Discord and Rust accounts  
🛡️ Permissions
linkingsystem.use - Permission to access the linking system and connect Discord account  
⚙️ How It Works
LinkingSystem provides a seamless three-step process for connecting Discord and Rust accounts, with both UI and command-only options:
Generate Code - Players use the /link command to open the UI interface, or /link code for direct command-only code generation with built-in cooldown protection. Discord Verification - Players share their code in the designated Discord channel where the bot automatically processes the connection. Instant Benefits - Once linked, players immediately receive their Discord role and start enjoying exclusive in-game perks and rewards. The system maintains real-time synchronization between Discord and your Rust server, ensuring that role changes and connections are processed instantly!
 
📚 FAQ
Q: Do I need to create my own Discord bot?
A: Yes, but we provide complete step-by-step instructions for creating and configuring your Discord bot, including all necessary permissions and settings.
Q: Can LinkingSystem work with multiple Rust servers?
A: Absolutely! The Discord bot supports multiple servers simultaneously. Simply add your server configurations to the bot's config file.
Q: How do I add LinkingSystem to the ServerPanel menu?
A: Follow these simple steps:
1. Open ServerPanel menu in-game and click "+ADD CATEGORY" button
2. Set these exact parameters:
Type: Plugin Plugin Name: LinkingSystem Plugin Hook: API_OpenPlugin 3. Click "SAVE" button to create the category
Q: How do linked players receive their rewards?
A: Rewards are granted automatically when a player successfully links their Discord account. The system automatically assigns the configured permission group to linked players.
Q: Are the rewards shown in the UI actually given to players?
A: The reward items displayed in the UI are visual representations only. The actual benefit is the automatic assignment to a permission group (default: "discord") which can be configured to provide various server perks through your permission system.
Q: Can I customize the rewards for linked players?
A: Yes! You can customize which permission group linked players receive and configure what benefits that group provides through your server's permission system. The visual reward elements in the UI are also fully customizable.
Q: What happens if a player leaves the Discord server?
A: The bot automatically detects when linked players leave the Discord server and can remove their in-game benefits accordingly.
Q: Is the linking data saved if the server restarts?
A: Yes, all linking data is automatically saved and persisted across server restarts, ensuring no loss of player connections.
Q: Can I use LinkingSystem without the UI interface?
A: Yes! Set "Use UI" to false in the configuration to enable command-only mode. Players can use /link code to generate linking codes, /link status to check their connection, and /link remove to unlink their accounts directly through chat commands.
 
🔄 Migrations
LinkingSystem includes migration tools to help you transition from other linking plugins. Currently supported:
DiscordLink Migration tools preserve all existing player links and Discord information, ensuring a smooth transition to LinkingSystem without data loss.
 
💻 Developer API
Linking System provides a developer-friendly API for integration with other plugins:
CuiElementContainer API_OpenPlugin(BasePlayer player) - Opens the linking interface for ServerPanel integration  
🧪 TEST SERVER
Join our test server to experience Linking System and all our features yourself!
Copy the IP Address below to start playing!
connect 194.147.90.239:28015

Maximum optimized solution without the possibility of duping. One backpack - one container.
This is an important feature because it ensures that each backpack has its own unique container and eliminates the possibility of incorrectly duplicating items. No data files or similar things are used. Backpacks and items are saved in the original way of the game.
This provides efficient management of backpacks and items in the game without the need for complex or additional file systems. Backpacks are physical items and there can be multiple pieces of them.
This is essential for creating a realistic game experience where players can have multiple backpacks in their inventory. Backpacks can be of all capacities, types (item or liquid) and for different purposes.
This enhances the gameplay experience by allowing players to choose backpacks based on their specific needs. Autoloot feature in backpacks is present (customizable for each backpack). Items will go straight into the backpack when picked up.
This feature makes gameplay easier by allowing items to go straight into the backpack you are wearing without additional actions. Backpack cooking feature is present (customizable for each backpack). Melts and roasts items inside the backpack. The function matches the original mechanics of the stove.
This feature adds an additional gameplay element by allowing players to cook food and recycle items directly inside the backpack. The backpack lies in the parachute slot and is displayed on the player.
This feature allows the backpack to be worn on the back without taking up inventory space, as well as being visually displayed to players. The backpack has several ways to open.
The first through a button in the interface when selecting an item, this allows you to effectively move between backpacks and inspect them even in the box.
The second through a command if the player has the appropriate permission. The opening will be done for an equipped backpack.  Each backpack has its own shortname and itemid.
This helps in easy management and customization.  Each backpack has a black sheet and a white sheet, allowing you to create a variety of backpacks for different scenarios as flexibly as possible. There is an option to return backpacks after death. This helps to save players' progress and prevents the loss of backpacks in case of unexpected situations.  It is possible to limit the number of backpacks in the inventory, set the maximum stack in the container, as well as customize the maximum stack for items. These parameters allow you to carefully control the number of backpacks in the inventory and items in them, which is important for the balance of gameplay. Installation:
The plugin necessarily needs the CustomItemDefinitions plugin, so the first thing we do is download and install it by throwing it into the oxide/plugins folder
Link to the plugin:  https://codefling.com/extensions/custom-item-definitions
After purchase, download and install this plugin by dropping it into the oxide/plugins folder
Quick Start:
In the default configuration 7 different backpacks are available, their shortnames and itemid can be viewed in the config.
Quick grant important permissions:
Allow players to use the autoloot and furnace functions if they are present in a particular backpack
o.grant group default betterbackpacks.autoloot.allow o.grant group default betterbackpacks.furnace.allow Allow players to open an equipped backpack on command
o.grant group default betterbackpacks.commands.open.allow Permission to enable Sortify plugin functionality:
betterbackpacks.sortify.use o.grant group default betterbackpacks.sortify.use The full version is available here:  
Permission to return all backpacks after death:
betterbackpacks.always_reclaim o.grant group admin betterbackpacks.always_reclaim
Permissions and their descriptions:
betterbackpacks.commands.open.allow - Allows the use of a command to open an equipped backpack betterbackpacks.sortify.use - Use the functionality of the Sortify plugin, full version here betterbackpacks.backpackslimit.bypass - Bypass the maximum number of backpacks in inventory (for admins). betterbackpacks.autoloot.allow - Allow to use autoloot function if it is present in a particular backpack. betterbackpacks.autoloot.any - Adds autoloot feature for all backpacks. betterbackpacks.furnace.allow - Allow to use the furnace function if it is present in a specific backpack. betterbackpacks.furnace.any - Adds the furnace function to all backpacks. betterbackpacks.always_reclaim - Returns all backpacks on death Commands to open an equipped backpack:
Console command - backpack.open (no delay) Chat command - /backpack (delay 0.2 seconds to wait for chat opening to close)
  More details about the functions and their customization:
Control the number of max amount backpacks in player inventory.
Control the ability to put backpacks in backpacks.
Here you need to specify the shortname for a particular customized backpack, it will be used in the issue or specified in other plugins. Do not be afraid to specify it in other plugins, it will work.
IMPORTANT: do not specify here shortnames of original items, this field is for a new shortname of a new item. Nothing bad will happen, it will report in the console and remove the backpack from the config.
This field is not used for editing, it is an auto-generated field. This field is for copying and specifying in other plugins.
Default name for the item. Further the name for different languages is customized in lang files.
The skin that will be given to the new item, you can specify the same ones, the plugin does not use the SkinID for identification.
The parameter of the capacity of the backpack. You can specify any, but within reasonable limits, do not specify billions or it may kill your server.
Set this to true if you want the backpack to be returned to the player after death.
Specify here true if you want the backpack to be returned only if equipped.
Container type for the backpack, use 1 for general (default), 2 for liquid.
Parameter to limit the maximum stack size for items in the container. This is not a hard limit, the minimum number for this parameter and the default stack is used. If you need to hard limit, add the items you want to "Max stacks by shortname"
Selects a list to restrict items. Types:
Blacklist allows all items except the specified items.
White list allows only the specified items.
A list of items for the specified item list in the "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)" field.
Example and description:
"Item list to exclude (for whitelist/blacklist)." [   {     "Shortname": "stones", // Item Shortname       "SkinID (negative value = any)": -1 // If it is -1, then the item is with any skin, if a specific one is specified, then only with that skin.   },   {     }, { "shortname": "sulfur.ore",     "SkinID (negative value = any)": -1   }, ], Parameter to enable the autoloot feature.  
To work the player must have the permission "betterbackpacks.autoloot.allow" or "betterbackpacks.autoloot.any".
Once enabled, the player must wear the desired backpack and then all items that will fall into the player's inventory will be in the backpack.
This works with mining and picking up items.
Parameter to enable the furnace function.  
The player must have the "betterbackpacks.furnace.allow" or "betterbackpacks.furnace.any" permission present for it to work.
For this to work, the player must have wood in his backpack.
Works similarly to how a furnace works.
It takes combustible material and melts what can melt, there is an opportunity to change the maximum number of simultaneously cooked items in the oven
Max number of simultaneously cooked items in the furnace in the backpack.
List for hard limit of stacks for an item by shortname in the format "shortname": stack size
Example:
{   "shortname1": 1000,   "shortname2": 1 }
Default config:
{ "General": { "Max amount backpacks in player inventory (minimum 1)": 100, "Prohibit putting backpacks in backpacks?": true }, "Backpacks (Add new ones at the bottom)": [ { "Unique new item shortname": "backpack.admin", "ItemId (DO NOT MODIFY THIS FIELD!)": -1878567520, "Backpack Setting": { "Name": "Admin Backpack", "SkinID (you can use the same ones for several backpacks)": 3050740532, "Capacity": 1000, "Reclaim after death": true, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 0, "Item list to exclude (for whitelist/blacklist)": [], "Components": { "Auto-Loot": true, "Furnace": true, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.small", "ItemId (DO NOT MODIFY THIS FIELD!)": -1093698081, "Backpack Setting": { "Name": "Small Backpack", "SkinID (you can use the same ones for several backpacks)": 3032442379, "Capacity": 6, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 0, "Item list to exclude (for whitelist/blacklist)": [], "Components": { "Auto-Loot": true, "Furnace": false, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.large", "ItemId (DO NOT MODIFY THIS FIELD!)": -717465782, "Backpack Setting": { "Name": "Large Backpack", "SkinID (you can use the same ones for several backpacks)": 3032442379, "Capacity": 48, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 0, "Item list to exclude (for whitelist/blacklist)": [], "Components": { "Auto-Loot": true, "Furnace": true, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.liquid", "ItemId (DO NOT MODIFY THIS FIELD!)": -1863402244, "Backpack Setting": { "Name": "Liquid Backpack", "SkinID (you can use the same ones for several backpacks)": 3050741122, "Capacity": 1, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 2, "Container Max Stack Size (0 = default)": 10000, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 0, "Item list to exclude (for whitelist/blacklist)": [], "Components": { "Auto-Loot": false, "Furnace": false, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.comp", "ItemId (DO NOT MODIFY THIS FIELD!)": -1167179500, "Backpack Setting": { "Name": "Component Backpack", "SkinID (you can use the same ones for several backpacks)": 3050740925, "Capacity": 12, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 1, "Item list to exclude (for whitelist/blacklist)": [ { "Shortname": "gears", "SkinID (negative value = any)": -1 }, { "Shortname": "scrap", "SkinID (negative value = any)": -1 }, { "Shortname": "fuse", "SkinID (negative value = any)": -1 }, { "Shortname": "tarp", "SkinID (negative value = any)": -1 }, { "Shortname": "rope", "SkinID (negative value = any)": -1 }, { "Shortname": "sewingkit", "SkinID (negative value = any)": -1 }, { "Shortname": "techparts", "SkinID (negative value = any)": -1 }, { "Shortname": "riflebody", "SkinID (negative value = any)": -1 }, { "Shortname": "smgbody", "SkinID (negative value = any)": -1 }, { "Shortname": "semibody", "SkinID (negative value = any)": -1 }, { "Shortname": "sheetmetal", "SkinID (negative value = any)": -1 }, { "Shortname": "roadsigns", "SkinID (negative value = any)": -1 }, { "Shortname": "metalpipe", "SkinID (negative value = any)": -1 }, { "Shortname": "metalspring", "SkinID (negative value = any)": -1 }, { "Shortname": "metalblade", "SkinID (negative value = any)": -1 }, { "Shortname": "propanetank", "SkinID (negative value = any)": -1 } ], "Components": { "Auto-Loot": true, "Furnace": false, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.wood", "ItemId (DO NOT MODIFY THIS FIELD!)": -16063997, "Backpack Setting": { "Name": "Wood Backpack", "SkinID (you can use the same ones for several backpacks)": 3050741444, "Capacity": 16, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 1, "Item list to exclude (for whitelist/blacklist)": [ { "Shortname": "wood", "SkinID (negative value = any)": -1 } ], "Components": { "Auto-Loot": true, "Furnace": false, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } }, { "Unique new item shortname": "backpack.ore", "ItemId (DO NOT MODIFY THIS FIELD!)": 1211853999, "Backpack Setting": { "Name": "Ore Backpack", "SkinID (you can use the same ones for several backpacks)": 3050741346, "Capacity": 32, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 1, "Item list to exclude (for whitelist/blacklist)": [ { "Shortname": "stones", "SkinID (negative value = any)": -1 }, { "Shortname": "sulfur.ore", "SkinID (negative value = any)": -1 }, { "Shortname": "hq.metal.ore", "SkinID (negative value = any)": -1 }, { "Shortname": "metal.ore", "SkinID (negative value = any)": -1 } ], "Components": { "Auto-Loot": true, "Furnace": true, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": {} } } ], "This is an example from which you can take parts and put them into the backpacks you want.": { "Unique new item shortname": "backpack.example", "ItemId (DO NOT MODIFY THIS FIELD!)": -1265413270, "Backpack Setting": { "Name": "Example backpack to copy-paste parts", "SkinID (you can use the same ones for several backpacks)": 3032442379, "Capacity": 777, "Reclaim after death": false, "Reclaim only if equipped": false, "Contents Type (1 - General | 2 - Liquid)": 1, "Container Max Stack Size (0 = default)": 0, "Use list (0 - None | 1 - Whitelist | 2 - Blacklist)": 1, "Item list to exclude (for whitelist/blacklist)": [ { "Shortname": "flower", "SkinID (negative value = any)": -1 }, { "Shortname": "pokemon", "SkinID (negative value = any)": -1 } ], "Components": { "Auto-Loot": true, "Furnace": false, "Max number of simultaneously cooked items in the furnace": 3 }, "Max stacks by shortname": { "shortname1": 1000, "shortname2": 1 } } } }  
Default lang file:
{ "NO_PERM_TO_USE_COMMAND": "You dont have permission to use this command.", "backpack.small": "Small Backpack", "backpack.large": "Large Backpack", "backpack.liquid": "Liquid Backpack", "backpack.admin": "Admin Backpack", "backpack.comp": "Component Backpack", "NEED_EQUIPED_BACKPACK": "An equipped backpack is required to use the command.", "backpack.wood": "Wood Backpack", "backpack.ore": "Ore Backpack", "AUTOLOOT_BUTTON": "AUTO-LOOT", "COOK_BUTTON": "COOK", "backpack.test": "Test Backpack" }

Upgrades your furnaces, ovens, refinery, mixing table & etc to beyond.

⭐ Key Features
Upgrade each attribute of your furnace; Supports different oven types; It is possible to define default attributes for all ovens on the server; You can set a default value for all base ovens (replacing quicksmelt); You can enable/disable any features you want; Option to keep attributes when removing the furnace; Option to auto split ores; Automatic fuel calc based on the upraded oven attributes; Now BBQ and Campfire can also be improved; Option so that only the furnace owner can upgrade it; Option so that only owner's teammates can upgrade it; A new completely redesigned UI; NEW Supports Mixing Table 🎬 Video Showcase
 
📜 Permissions
furnaceupgrades.use - This is the unique permission. required for all players to upgrade furnaces ⚙️ Configuration
💬 Support