When tested on oxide version 2.0.4636 (latest version) using StackSizeController v2.0.4 as the only plugin loaded, StackSizeController seems to effect the Recycler's item rate/item consumption.

If modification is made to a stack size, it will recycle differently & accordingly to the multiplier of the stack made

ex: 10 explosives recycle per tick by Vanilla default.
If you raise stack size from 100 explosives to 200 explosives, it will recycle 20 explosives per tick.
If you raise stack size from 100 explosives to 2000 explosives, it will recycle 100 explosives per tick.

This is when modifying specific item numbers, and not adjusting categories (For example, this still persists on v1.9.9 of StackSizeController, if you test editing the Explosives max stack number in the config).

If this is intended feature can or may there be a config variable to disable this feature?

Thank you for your time & help =] <3

I have found that if you have a stack of most Rifle weapons it is best to split them to single units if you dont want to lose recycled components. This is probably true of most multi component items, i can be tedious but rewarding.

pookins

I have found that if you have a stack of most Rifle weapons it is best to split them to single units if you dont want to lose recycled components. This is probably true of most multi component items, i can be tedious but rewarding.

Unfortunately, @pookins, your response doesn't address my concern and current issue; however, I do very much appreciate the effort and time, of course! Thank you for your response. This plugin is currently having an unintended conflict with vanilla recycling item consumption rates, and its creating a source of problems for Recycler modifications I'm trying to make elsewhere. 

I'm simply looking to make the recycling item consumption rates vanilla at its source (more specifically, unmodified) by the StackSizeController functions, instead of having the recycling item consumption scale with higher stack size.

I am assuming this function by StackSizeController is not intended since there is no mention of recycling modifications on the plugin homepage (nor are any edits possible to the recycler within the config). Ideally (as to not cause conflict for other users), I suggest and propose that "feature" should able to be enabled or disabled in the config.

If this is not doable or logical to perform, I'm simply looking for direction on how to fix this outcome within its code, or if the 2x+ recycler item consumption rates are even possible to be fixed. Even if there's some sort of code or reference that can be written or edited, I'd be privileged to be pointed in the right direction.

I appreciate any time anybody spends on this, of course. Thank you!