It's quite possible I'm just doing something wrong:

used stacksizecontroller.setallstacks 999999
that resulted in CategoryStackMultipliers all being set to 999999
so far so good
however values in the "IndividualItemStackSize" section are not overriding the category multiplier

for example, note is set to 1, but i can still stack them.

1. am I doing this wrong?  if this is the correct way to do it, can I remove items I don't want to override, or will it put them back?  It seems like the "IndividualItemStackSize" should be a rather short list of items that don't use the category values.

3. can you explain the difference between multiplier and stack limit? is multiplier simply so you can scale stacks up, rather than just setting a max? (having trouble understanding a use case for this, but probably depends on the type of server one is running)

edit:

In case it helps, we run a PVE server.  My end goal is to set all items to max (we used to use 999999, but I guess 2,147,483,647 is valid now).  However, there are a few items we do NOT want to stack (notes for example)

Currently you would need to set a 1x multiplier for the item, like notes in the field IndividualItemStackMultipliers. As that will take the IndividualItemStackSize value and multiply it by the value instead of returning IndividualItemStackSize multiplied by category or global.

So basically for anything that you don't want stacked, copy the entry from IndividualItemStackSize which has the item shotname and stack limit, and add it to IndividualItemStackMultipliers and set the number to 1 which essentially forces a default stack size. 

I'll try to get an update soon with the ignore list in the configuration, which should make this a little easier and more understandable.

thanks, that helps.  I ended up using your converter to pull our old v3 config in, then went through and updated the ones that we must not have added (new items), and set the multipliers back to 1.  Not the most efficient, but it works.

Also, I don't think this is a fault of your plugin, but it might be something to warn people about:
Apparently the Furnace Splitter plugin has issues if the stack size for some items (ores and their outputs I assume) is too high.  I don't know where the limit is, and I have too many players on to play with it right now, but when I had it set to whatever the defaults times 999999 is[-4031221 metal.ore Resources 1,000 999,998,976], you couldn't add things to small furnaces.  Again, I don't think this is something being done wrong by your plugin, but it might be something to warn ppl about.

I'll see if I can find the max value and the items in the next few days.

mughi

thanks, that helps.  I ended up using your converter to pull our old v3 config in, then went through and updated the ones that we must not have added (new items), and set the multipliers back to 1.  Not the most efficient, but it works.

Also, I don't think this is a fault of your plugin, but it might be something to warn people about:
Apparently the Furnace Splitter plugin has issues if the stack size for some items (ores and their outputs I assume) is too high.  I don't know where the limit is, and I have too many players on to play with it right now, but when I had it set to whatever the defaults times 999999 is[-4031221 metal.ore Resources 1,000 999,998,976], you couldn't add things to small furnaces.  Again, I don't think this is something being done wrong by your plugin, but it might be something to warn ppl about.

I'll see if I can find the max value and the items in the next few days.

AnExiledDev

Yeah just checked FurnaceSplitters code and yeah, it wasn't built to support stack sizes over roughly 715,827,882. FurnaceSplitter should be throwing an exception for that.

facepalm  I don't know if it's new, but there is a warning right near the top of the Furnace Splitter page

WARNING STACK SIZES CANNOT & SHOULD NOT EXCEED 700 MILLION!!! Anything over 700 million, the small furnace, small oil refinery, and BBQ Grill tend not to split them at that point and has to be done manually.

Hmm, not sure why he wouldn't just fix it, it's a very minor issue lol