Khan
-
Posts
1,062 -
Joined
-
Days Won
7
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Khan
-
Version 1.0.3
66 downloads
Allows weapons to have modified magazine sizes, conditions, custom names, infinity ammo/condition, and control if the weapon should drop or not on death. Features 5 permission levels ( will default to lowest number if assigned multiple permissions to a player. ) infinity ammo toggle " Without needing to reload gun" infinity condition toggle Drop Weapon on Death toggle Custom Weapon Name options for each permission on each gun Condition Level Options on item crafted Skin Id Support on item crafted Ammo Type Support on item crafted Preloaded Magazine Size support on item crafted Each weapon has the ability to rename permission at the end. Example: weaponmodifier.1 to weaponmodifier.police Item Short-Names can be found here at this link. Chat Commands /switchperm 3 1 //permission 3 is removed & 1 is granted for everyone on the server /switchperm police cop //permission police is removed & cop is granted for everyone on the server /modify <shortname> <permission> max <true/false> /modify <shortname> <permission> maxammo <true/false> /modify <shortname> <permission> drop <true/false> /modify <shortname> <permission> magazinesize <100> // These below are only for when you craft a weapon. /modify <shortname> <permission> preloadsize <100> /modify <shortname> <permission> skin <skinID> /modify <shortname> <permission> condition <100> /modify <shortname> <permission> name <NewName> /modify <shortname> <permission> ammotype <ammoshortname> Localization The default messages are in the WeaponModifier 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. { "NoPerm": "Unknown Command: modify", "Syntax": "Invalid Params please do /modify shortname permission setting value", "InvalidSelection": "You've selected an invalid weapon to modify please type a valid weapon shortname", "InvalidWeaponOption": "Weapon {0} is not an available option in the config file.", "InvalidPermission": "Invalid Permission Selected please check config for current permission names", "Success": "You've successfully set {0} {1} to {2}", "InvalidSwitch": "Invalid, Example: /switchperm 3 1\n permission 3 is removed & 1 is granted" } Config$9.99- 2 reviews
-
- 1
-
-
- #weapon modifier
- #weapon
- (and 3 more)
-
Version 1.0.1
183 downloads
Easily identify the owner and ID of taken photographs, also logs all images taken to discord using a simple webhook. Permissions photographsowner.use -- Allows players to use the /photo chat command photographsowner.admin -- Allows players to toggle true/false config settings Chat Commands /photo -- Shows the photographs owner ID/Name Admin Commands /setphoto displayname true -- Enables/Shows the photographs owner Display Name /setphoto id true -- Enables/Shows the photographs owner Steam 64 ID Configuration { "Display Name": true, "Display SteamID": false, "Set Who's Photo Command": "photo", "Set Admin Command": "setphoto", "Set Discord Webhook Logging": "" } Localization The default messages are in the PhotographsOwner 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. { "NoPermPhoto": "Unkown Command: {0}", "NoneFound": "No Photos Found", "Syntax": "Invalid syntax. Please use {0} option true or false.", "CmdResponse": "Successfully set {0}, to {1}", "Photographers": "Photographers:\n{0}", "DisplayName": "Display Name", "SteamID": "Steam ID", "Title": "Photographer: {0}", "Description": "Photographed In Zone: {0}", }Free -
Version 1.0.0
64 downloads
Prevents players from being double handcuffed, which can cause them to become permanently stuck in a handcuffed state due to a glitch. Also includes a chat command that allows affected players to restore their normal status—only usable if the player is bugged but not currently handcuffed. /restorecuffs /restorecuffs userID ( you can also manually specify a player or NPC to restore )Free -
@Rust Admin There are not any performance issues with stack-modifier and stack modifier supports and fixes a significant amount more of bugs with stacks then any other stack plugin. But plugins can cause performance issues that literally spam call the can-stack hook. Plugins such as ( sorting plugins, auto-splitting plugins, and plugins that move a large amount items really fast like kits or loadout plugins ). If you experience performance issues and your running one of those kinds of plugins ^ then it's most likely the poor code quality spamming the hook call needlessly. Without running any kind of coroutines or preventing the players from rapidly spam clicking sort to cause server spike issues. Etc. -
@ocnod Due to some rust changes awhile back, you cannot fully hide the dome you can make it mostly transparent by setting the value to 1. I don't use timers, and mine is extremely performant. Anyone who enters the raid bubble all share the same raid clock with an option to add combat block when they leave the raid bubble. -
That is a tuff question. Lower move frequency = faster moving, higher move frequency = slower moving. This entirely depends on your servers specs, the map size, industrial limits set, and how many players are actively on your server. You'll just have to play with the settings and adjust as needed in regards to performance concerns. -
@db01739 It will automatically refresh the loot when no players are nearby. Every 600f, so basically every 10min it will check & refresh the loot if no players are within x radius. ( to deter loot campers ) -
Certainly, I’ll be preparing an update for this. Next Update will have multi-language support.
-
Version 1.1.0
914 downloads
StackModifier: Industrial is an expansion designed to address all industrial-related stacking, splitting bugs, exploits, and issues. It patches the Industrial Conveyor and Industrial Crafter, providing much-needed fixes and improvements. Additionally, it introduces customizable limits that you can set and control to enhance the industrial gameplay experience. It also has blacklist support for the industrial crafter. This plugin will not affect plugins that auto-generate Industrial piping or placing. This plugin only targets players. NOTE: IF a plugin auto generates a farm past 5 daisy chained boxes it will start affecting server performance and cause hook time warnings. Server Defaults: Recommend sticking below vanilla defaults due to performance issues. # Industrial Component | Default | Custom | |-----------------------------|---------|---------| | Industrial Crafter | 6 | 6 | | Industrial Storage Adaptor | 34 | 20 | | Industrial Hopper | 6 | 6 | | Industrial Combiner | 17 | 9 | | Industrial Splitter | 17 | 9 | | Industrial Conveyor | 28 | 14 | |-----------------------------|---------|---------| Configuration File: { "Allow Industrial Crafter to craft random armor slots like normal crafting.": false, "Industrial Conveyor Max Stack Size Per Move Default: 128": 128, "Industrial Conveyor Move Frequency Default: 5, Lower = faster moving": 5, "Maximum difference in seconds that two items with Spoil Timers can have and still be stackable: 3600f < Default = 1-Hour difference": 3600.0, "Limit Industrial linking to improve server performance, adjust as needed.": { "Industrial Crafter": 6, "Industrial Storage Adaptor": 20, "Industrial Hopper": 6, "Industrial Conveyor": 14 }, "Industrial Crafter Black List: Item-Shortnames": [ "spear.wooden", ] } Why Limits Are Needed: Due to heavy server performance issues caused by the Industrial Conveyors being daisy-chained, I've introduced limits to help reduce the strain on server resources. When large industrial systems are built, especially with Auto-Crafters and Auto Bases, the sheer number of items and operations involved can cause significant performance degradation. Here’s an example of how an industrial system affects server performance: Industrial Crafter > Industrial Crafter > Industrial Crafter > Lg Furnace > Elec Furnace > DropBox > DropBox > DropBox > Combiner > Combiner > Combiner > - Combiner > - Splitter > - x3 Splitter > x3 Splitter > x3 Splitter > x3 Splitter > 27x Conveyor > Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box Box 3x Combiner > 3x Combiner > 3x Combiner > - 3x Combiner > - Combiner > - Splitter > - 3x Splitter > Auto Crafter > Ore to Lg Furnace > Ore to Elec Furnace > Build Summary: 4x Industrial Crafters 34x Storage Adaptors 17x Combiners 17x Splitters 27x Conveyors Each box has 48 slots, and the CanStackItem hook is called for each slot that is used. With 27 boxes, that’s 1,296 calls before the process stops, assuming all boxes are full. This leads to high hook times, warnings, and server lag. The Solution: Limits To mitigate this issue, I’ve implemented a system of limits for these large industrial builds. The new default limit for Conveyors is now 14 (down from the vanilla limit of 28), drastically reducing the number of CanStackItem calls to 672. This helps to reduce the server load and improve performance. These limits are adjustable and can be configured inside the plugin’s settings, allowing you to fine-tune the system to best suit your server's needs. Lang File: { "Title": "<size=14><color=#00CED1>Connection Limits</color></size>\n", "Message": "<color=#FFD700>0</color>\n<color=#FF6347>Max Limit:</color> <color=#FFA07A>1x</color> | <color=#ADFF2F>Detected:</color> <color=#7CFC00>2x</color>", "Blocked": "Connection Blocked: View Chat or F1-Console-Menu for Details.", "Crafter": "Industrial Crafters", "Adaptor": "Industrial Storage Adaptors", "Hopper": "Industrial Hoppers", "Conveyor": "Industrial Conveyors", "Blacklist": "Blacklisted Item 0" }$9.99- 5 comments
- 2 reviews
-
- 2
-
-
-
- #stack modifier
- #industrial
- (and 5 more)
-
@RickySpanish343 Sure, when I get the chance. -
@Sephisticate Features like that will be added directly to stack-modifier with an addon, sometime next month. It requires me to build a whole other plugin to work with stack modifier to handle the logic correctly.
- 202 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
@mainloot This won't work because if players keep attacking, the MonoBehaviours will keep resetting the timer. Your implementation doesn’t account for this or provide a way to track when the timer resets, leading to inaccurate and unreliable updates. I understand wanting to help, but please don’t post plugins or code patches for paid works without first contacting the developer or at least opening a support ticket to discuss it.
-
@Wizz NoEscape uses a custom UI system inside a MonoBehaviour class, meaning it doesn't rely on standard hook calls for updates. Supporting external API requests for status updates would introduce performance issues due to frequent polling or callback overhead. So, unfortunately, that’s not something I plan to add. That said, if you have specific UI display needs or alternative ways you'd like to see status information presented, feel free to share! I'm always open to improving the system.
-
. -
Version 1.0.1
468 downloads
The No Drop plugin prevents players from dropping items when they are wounded or die. This ensures that all items remain in their inventory system instead of falling to the ground. Features: Prevents active items from dropping on wounded state. Prevents items from dropping on death, including backpacks. Lightweight and optimized for performance. Configuration: This version does not include a config file since item dropping is always disabled. If needed, future updates could add a toggleable setting. Permissions: No permissions are required—this plugin works globally for all players.Free- 1 comment
- 1 review
-
- 1
-
-
- #no drop
- #drop blocker
- (and 8 more)
-
We have verifications for frameworks but not for plugins? Seems like a wasted opportunity.
-
At the moment the main issue is that customers sometimes buy a plugin expecting the works with section to actually work. But even if you added a yellow notification to indicate that this may not be guaranteed at least then the customer wouldn't be miss-lead in case in that moment support was broken for that listed plugin. Currently the site having a works with section in general is miss-leading for plugins that haven't maintained support.
-
I would argue, that it would give peace of mind to customers & would justify the slight inconvenience to the dev. There could also be auto reject options ( on by default ), etc. But again, just an idea & requires more feedback. A simple poll on discord would provide you with an idea if it'd be something devs would even want at the moment.
-
You should do a poll in Discord and get developer feedback. Poll: Plugin Compatibility System on Codefling Description: Should Codefling introduce a "Works With" verification system that allows plugin developers to opt-in for compatibility with other plugins? Green Verified — Both developers agree to maintain compatibility. Yellow Unverified — One developer has added support, but the other hasn't opted in. Renewable Commitment — Developers can choose 6-month or 1-year support periods. Would you support this system? Yes — Helps users find compatible plugins easily! No — Too much overhead for developers. Maybe — Needs refinement before implementation. Vote below!
-
You could also further push this to be solely up to the devs to support / handle by updating the codefling policy to reflect that. So that at the time a purchase is made if both devs have opted in with a green verified works with then both devs will be required to support it. But if only a yellow check box is next to a works with plugin listed then support is not guaranteed upon purchase. This will keep your 6month warranty in-tact & push the responsibility to devs who have opted in. Also, you can make this a 6-month renew option for devs. So there only obligated to support it for 6-months at a time ( or more ) if you include 1 year option.
-
@Death Then don't make it a moderation issue for codefling. Make it so that a dev can list works with x plugin. Then when that occurs that plugins dev can receive a notification indicating that a dev has marked his as works with & can manually decide to opt in to agree to also maintain 3rd party plugin support with that plugin. ( Basically what we already have now on codefling ) But with the addition / addon--being where the dev is notified of it & can manually choose to opt in for mutual agreed 3rd party support between the 2 plugins. ( And if both have it listed, then a green verified check box will appear next to it on the plugins product page as "verified" to work with each other ) ( And a yellow to indicate that support was added but may not be guaranteed--for those who don't both opt in/one sided )
-
@Willie00 The DLL version has been retired, too many compatibility issues with a site called BattleMetrics, etc. I only support / maintain the Plugin version. Which does work with BattleMetrics. -
@mainloot @Elloco This plugin will never work right on carbon fully, there are still currently multiple bugs with it on carbon that do not occur on oxide & that are not fixable due to how they handle oxide plugins / carbon. Yes the carbon team has made a fair bit of improvements to actually supporting oxide plugins but they still have a long ways to go.
