Search the Community

Description The UpgradeRestrictor plugin prevents players in Rust from skipping upgrade levels for building structures. Inspired by the new game Duckside, which showcases this upgrade progression and is loved by players, this plugin enforces Rust's upgrade sequence: Twig → Wood → Stone → Metal → HQ. It ensures that players follow this order and blocks attempts to skip material tiers. If players try to bypass a step, the upgrade is blocked, and a color-coded message appears in the chat, indicating the next required tier. Features - Blocks players from skipping upgrade tiers for building structures. - Displays a color-coded chat message with the plugin name and the next required upgrade level. - Requires specific permission to apply restrictions. - Supports the following upgrade path: Twig → Wood → Stone → Metal → HQ. Commands No specific commands available. Permissions upgraderestrictor.use For these players, the upgrade restrictions must be used. Players without this permission can upgrade structures without restrictions. Configuration No specific configuration settings required. load, run, enjoy

Features: The plugin allows you to control the number of foundations per player (or per clan). You can also customize the number of foundations per player using permissions. Plugin works with Clans (from UMod or Clans REBORN). Also it can be used without the Clans plugin. How it works with the Clans plugin: If a player is in a clan, then he can use the entire clan limit (the clan limit counts the limit of each player), and a certain amount of an additional limit for each player is added to this limit (this percentage can be configured in the config or set to 0, which will disable this function) Commands: playerflimit steamid - show player limit (RCON command) Config: { "SteamID for icon in chat messages": 0, "Command for check limit": "flimit", "Additional foundations for each player (Percentage)": 0.05, "Permission - Limit for foundations(Should go from standard to best)": { "foundationlimits.default": 50, "foundationlimits.vip": 100, "foundationlimits.premium": 200 } } Lang: { "CM_LIMIT": "You have exceeded the limit for building foundations (type /{0})", "CM_LIMITFULL": "Your limit for foundations: <color=red>{0}/{1}</color>", "CM_NOTFULLLIMIT": "Your limit for foundations: <color=green>{0}/{1}</color>" }

IMRG plugins are currently not for sale. Additionally the "IMR Tools Package" are (or soon to be) unlisted. Those who've already bought our plugins are welcome to still submit support request if necessary. Once we've more time to allocate to Codefling plugins will be relisted again as well as more added. Entity Control is a powerful all-in-one entity-controlling plugin offering virtually complete admin control over which entities players on the server can place, where they can place them, and how many they can place, with many advanced features. Because mass entities like bases with huge block counts or other unregulated entities like Large Furnaces, Wind Turbines, Disco items, Xmas Lights, and more, can greatly reduce both server frames and client frames (two different forms of FPS), it is especially critical to limit how many can be used in order to troubleshoot or optimize performance for your server and players. This plugin can also be used to allow or disallow specific groups of players access to or from specific entities or specific quantities of those entities, or used for special occasions like events and more; the sky is the limit, and this plugin gives admins the control they need. List of entity names for the config can be found here: https://www.corrosionhour.com/rust-prefab-list/ Features • Gives server owners precise control over which entities can be deployed, where they can be deployed, and how many can be deployed • Saves admins having to beg players to limit their entity counts when admins can now dynamically enforce this themselves • Can target specific groups of players or everyone at once • Controlling entities can be critical for server and client frames and therefore all around performance for your server • VIP Ready to allow specific players or groups to bypass the blocks or have different quantity amounts • Zone Manager integration (optional) to allow or disallow specific entities in specific areas or specific amounts in or out of those areas • Optional warning message when players are nearing their limit • Great performance • Highly customizable with advanced features Depends On IMR Tools Package: https://codefling.com/tools/imr-tools-package Always make sure you have the IMR Tools Package installed first when running any plugins by IMR Games. Works With Zone Manager: https://umod.org/plugins/zone-manager Compatibility with Zone Manager If you want to use the zones feature of the plugin. Installation - Make sure you have the IMR Tools Package installed, as explained above. - If you want to use the zones feature of this plugin, make sure you also install the Zone Manager plugin, found above. - Put this plugin in your oxide plugins folder. - It will generate a config file. - Customize and enjoy! Console Commands imrgentitycontrol.cache - Goes through all entities on server and reloads amounts for accuracy. Suggested for use before using the logcounts command. imrgentitycontrol.logcounts steamid - Shows how many relevant entities as per the config a particular player has. imrgentitycontrol.logexcess - Highlights any excess deployables that players may have outside of the configured limits. imrgentitycontrol.deleteexcess - Deletes any excess deployables that players have outside of the configured limits. Good for making sure limits are enforced or if you like, enforcing limits on a wipe that is already active but you changed the config settings and want to enforce the new limits, and so on. Permissions All permissions in this plugin are completely customizable in the config file. There can be as little or as many group as you like depending on what you want to do. The only requirement is that the beginning of the permission use the plugin name which is imrgentitycontrol. This makes the potential use cases nearly endless! Included in the default config are the following permission group examples just to demonstrate a few things you can do: - Example 1: Players can place 500 foundations, and VIP players can place 5000 foundations (With an example of the warning message feature) - Example 2: Small Oil Refineries are blocked for everyone - Example 3: Only VIP players can place Christmas lights - Example 4: Players can place 2 Large Furnaces, and VIP players can place 6 - Example 5: Players with this specific permission cannot place Wind Turbines at all, without even a VIP option (this could be useful if just simply trying to improve performance period) - Example 6: Disco deployables cannot be placed where the user is trying to place them, with a permission to bypass the block - Example 7: Auto Turrets can only be placed in a special Auto Turret Zone These are just examples, the plugin can be used in countless ways by inputting whichever prefabs you want to block/limit in whichever ways you want to block/limit them in the config below. Config { "Prefab Groups": [ { "Limits (By Zone)": [], //Optional list of Zone Manager Zones where players can or can't place entities, or controls how many they can place there. "Default Limits": { "Limit (By Permission)": { "imrgentitycontrol.vip": 5000 //Permission to allow any players with the permission to override the default limit below. Setting this to -1 would mean unlimited amount. Setting this to 0 means anyone with this permission can't place any. }, "Default Limit": 500 //The amount that all players can place of the configured entities below. Setting this to -1 would mean an unlimited amount. Setting this to 0 means they can't place any unless they have a permission bypass. }, "Shared Prefab Count": true, //If set to true, the count of prefabs below is shared. For example, if the default limit is set to 4, you can place 2 of each or 3 of one and 1 of another (using the sample prefab list below). If set to false, players can place 4 of each of those since the prefab count is NOT shared. "Warning Percentage": 0.75, // Percentage for when the warning message starts. So in this example players will start reciving warnings when they have placed 375 foundations (3750 for vips) "Limited Prefabs": [ //List of prefabs that all the above configs work with. "assets/prefabs/building core/foundation/foundation.prefab", "assets/prefabs/building core/foundation.triangle/foundation.triangle.prefab" ], "Block Chat Message": "Players can only place 500 foundations. VIP players can place 5000.", //Message players receive if trying to place an entity that is above their personal or global limit. "Warning Chat Message": "You are nearing your foundation limit. ({0} out of {1})" //Message players recive when being warning for nearing their limit. Or null to disable the warning }, { "Limits (By Zone)": [], "Default Limits": { "Limit (By Permission)": {}, "Default Limit": 0 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/deployable/oil refinery/refinery_small_deployed.prefab" ], "Block Chat Message": "Small Oil Refineries are blocked on this server", "Warning Chat Message": null }, { "Limits (By Zone)": [], "Default Limits": { "Limit (By Permission)": { "imrgentitycontrol.vip": -1 }, "Default Limit": 0 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/misc/xmas/poweredlights/xmas.advanced.lights.deployed.prefab", "assets/prefabs/misc/xmas/christmas_lights/xmas.lightstring.deployed.prefab" ], "Block Chat Message": "You must be a VIP player to place Christmas Lights", "Warning Chat Message": null }, { "Limits (By Zone)": [], "Default Limits": { "Limit (By Permission)": { "imrgentitycontrol.vip": 6 }, "Default Limit": 2 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/deployable/furnace.large/furnace.large.prefab" ], "Block Chat Message": "You can only place {1} Large Furnaces (you have already placed {0})\nVIP players can place up to 6", "Warning Chat Message": null }, { "Limits (By Zone)": [], "Default Limits": { "Limit (By Permission)": { "imrgentitycontrol.windmillblocked": 0 }, "Default Limit": -1 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/deployable/windmill/windmillsmall/electric.windmill.small.prefab" ], "Block Chat Message": "You are not allowed to place Wind Turbines", "Warning Chat Message": null }, { "Limits (By Zone)": [ { "Limit (By Permission)": { "imrgentitycontrol.discoallowed": -1 }, "Default Limit": 0, "Zone": [ "No Disco Zone" ] } ], "Default Limits": { "Limit (By Permission)": {}, "Default Limit": -1 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/voiceaudio/discofloor/discofloor.deployed.prefab", "assets/prefabs/voiceaudio/discoball/discoball.deployed.prefab", "assets/prefabs/voiceaudio/discofloor/skins/discofloor.largetiles.deployed.prefab" ], "Block Chat Message": "Disco Deployables may not be used in this Zone unless you have a special permission", "Warning Chat Message": null }, { "Limits (By Zone)": [ { "Limit (By Permission)": {}, "Default Limit": -1, "Zone": [ "Auto Turret Zone" ] } ], "Default Limits": { "Limit (By Permission)": {}, "Default Limit": 0 }, "Shared Prefab Count": false, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/npc/autoturret/autoturret_deployed.prefab" ], "Block Chat Message": "Auto Turrets may only be placed in the Auto Turret Zone", "Warning Chat Message": null }, { "Limits (By Zone)": [], "Default Limits": { "Limit (By Permission)": {}, "Default Limit": 3 }, "Shared Prefab Count": true, "Warning Percentage": 0.75, "Limited Prefabs": [ "assets/prefabs/deployable/tier 1 workbench/workbench1.deployed.prefab", "assets/prefabs/deployable/tier 2 workbench/workbench2.deployed.prefab", "assets/prefabs/deployable/tier 3 workbench/workbench3.deployed.prefab" ], "Block Chat Message": "You can only have {1} Workbenches in total", "Warning Chat Message": null } ] } Lang All messages players receive related to prefab blocks or allowances are in the config file per group. They can be customized for the exact purpose you need them. Notes - If a prefab is not covered in the config, it is simply not limited/controlled/affected by permissions in any way. It is simply untouched and unaffected by this plugin and works like normal.