Khan
-
Posts
1,081 -
Joined
-
Days Won
7
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Khan
-
Version 1.1.0
928 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.- 201 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
480 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.
-
@RickJamesBitch Well, skill tree should let stack modifier handle all stacking & split logic. So technically skill-tree.
-
@Wizz Set the sound effects to a blank empty string in the config to disable them. You can set the sphere color to 0 & set the visibility level to 1 which makes it very transparent and extremely difficult to see which is as close as it gets to "Invisible"
-
@mainloot Carbon support is impossible, it doesn't support invoking in a custom mono-class because they change the set fields from private to public when an oxide plugin is loaded, also the UI system is slightly different enough which breaks the UI system in this plugin. As well as a few other issues like slight hook differences compared to oxides hook locations resulting in different behavior. So no, carbon support would not be possible.
-
@paxx Thank you for the feedback, I will certainly look into adding some of that functionality / Corpse stuff was added as of 1.4.1 & Blacklist items have been updated.
