uMod - Stack sizes not working except with command - Stack Size Controller

Posted 6 years ago

Last updated 6 years ago

So Ive again, read my eyes our of my head trying to figure this out. I legit havent even touched my oxide/data/StackSizeController.json at all, as Im fine with it. However, under the oxide/config/StackSizeController.json I have this as bellow:
{
"Settings": {
"CategoryDefaultStack": {
"Ammunition": 300,
"Attire": 1,
"Common": 1,
"Component": 1,
"Construction": 1,
"Food": 40,
"Items": 1,
"Medical": 4,
"Misc": 1,
"Resources": 2000,
"Tools": 1,
"Traps": 10,
"Weapon": 1
},
"DefaultStack": 0,
"StackHealthItems": false
}
}

Now from what Ive read and been told. When editing the specific items within the oxide/data/PLUGINNAME.json, the server has to not be running, or plug in unloaded. But, I never changed anything in this file. As the specific items are fine as is. What I mainly care about is the resources. Som, going back to the oxide/config/PLIGINNAME.json, as you can see above. Should work fine right? Ive tried through rcon, oxide.unload PLUGINNAME, then oxide.load PLUGINNAME. Tried oxide.reload PLUGINNAME, even restarted the entire server... Nothing seems to get it to stack over 1000. However. When I type in chat /stack wood 2000, its works.... Which defintely signifies that the plugin is installed and working. Just simply isnt hitting my configuation levels? Any help is greatly appreciated, thanks.

Posted 6 years ago

Last updated 6 years ago

The server can be running, the plugin just needs to be reloaded after editing it. Configuration files just require a plugin reload, data file editing requires the plugin to be unloaded or server shut down.

Posted 6 years ago

Last updated 6 years ago

Thanks for stopping in wolf, but with all do respect, Im well aware of that. The issue isn't reloading or unloading or restarting the server.. I was simply clerifying that I have done EVERYTHING. The issue is why isnt the plugin working for the desired amounts that I have under the default oxide/config/StackSizeManager.json? REGARDLESS of reloading, unloading, restarting server.

Posted 6 years ago

Last updated 6 years ago

I have same issue. stack just wont go any higher than 1k.

{
"Settings": {
"CategoryDefaultStack": {
"Ammunition": 500,
"Attire": 50,
"Common": 0,
"Component": 100,
"Construction": 0,
"Food": 100,
"Items": 50,
"Medical": 100,
"Misc": 0,
"Resources": 5000,
"Tools": 10,
"Traps": 10,
"Weapon": 1
},
"DefaultStack": 0,
"StackHealthItems": false
}
}

Posted 6 years ago

Last updated 6 years ago

Have either of you considered editing your Data file items to the size you want ? , My default resources size is 200000 but my data size is 600000 , I have no problems with this plugin after i finished editing my data file a while ago.

Posted 6 years ago

Last updated 6 years ago

where do I look for this data file items?

Posted 6 years ago

Last updated 6 years ago

In your Data folder called StackSizeController.json , dont forget to unload the plugin before you edit and save the Data file, save it and then reload plugin.

Posted 6 years ago

Last updated 6 years ago

it works with file in \data folder. thank you

Posted 6 years ago

Last updated 6 years ago

In response to pookins ():
Have either of you considered editing your Data file items to the size you want ? , My default resou...

No because I had no desire to change any specific items. I only wanted to change the resources. I was told that this can be done easily through the oxide/config/StackSizeManager.json. Everyone else has done this from what ive read, and seems to work fine. I guess the main thing to edit is the oxide/data/StackSizeManager.json. I figured this was only neccessary for specific items. But now its clear that this is THE ONLY way to edit your stack size. So the description of who created this plugin is VERY misleading...

I just honestly didn't want to have to sift through all that crap, just to change the stack size of 5 resources, when it should easily be done through the Oxide/config/StackSizeManager.json. But, Apparently the Oxide/config/StackSizeManager.json is complete garbage and does absolutely nothing...

I will edit the data file and get back to you guys.

Yup so editing the Data file, works. Just sucks I have to literally sift through HUNDREDS of items just to change 5 resources.... I still am curious why the oxide/config/StackSizeManager.json Doesnt work?

Posted 6 years ago

Last updated 6 years ago

#10

In response to EsCL337 ():
No because I had no desire to change any specific items. I only wanted to change the resources. I wa...

IF you had read ALL the posts regarding this plugin you would have saved yourself some time by adjusting those resources by using (in chat)
/stack metal.refined 2000 and do the same for other resources. with your experience you would already have the link to Rust item names but just in case you lost it i will give it to you again.
https://www.corrosionhour.com/rust-item-list/

Posted 6 years ago

Last updated 6 years ago

#11

As of this wipe my stack sizes also won't go above 1,000 and they are edited in the .json file.

Furthermore, attempting to use the /stack command generates a NRE on the server.

Posted 6 years ago

Last updated 6 years ago

#12

My max stack size is 600000 and no problem with using.

/stack <item name> <amount>

Which .json file ? Config or DATA ? I just used command in chat to increase medical syringe stack to 50 with no problem.

Posted 6 years ago

Last updated 6 years ago

#13

Hi

We have been using the plugin for months now and after the last wipe we have to manualy type the stack size after every server restart.

We udated the both the file on the config and data folders but they do not load the required stack sizes.

Files

/oxide/config/StackSizeController.json
/oxide/data/StackSizeController.json

Resources that we been changing.

Wood 3000
Sulfur Ore 3000
Stones 3000
Metal Ore 3000

Server Details

Server Type: Community
Name: Voodoo SA | Noob Freindly

Posted 6 years ago

Last updated 6 years ago

#14

EsCL337
No because I had no desire to change any specific items. I only wanted to change the resources. I was told that this can be done easily through the oxide/config/StackSizeManager.json. Everyone else has done this from what ive read, and seems to work fine. I guess the main thing to edit is the oxide/data/StackSizeManager.json. I figured this was only neccessary for specific items. But now its clear that this is THE ONLY way to edit your stack size. So the description of who created this plugin is VERY misleading...

I just honestly didn't want to have to sift through all that crap, just to change the stack size of 5 resources, when it should easily be done through the Oxide/config/StackSizeManager.json. But, Apparently the Oxide/config/StackSizeManager.json is complete garbage and does absolutely nothing...

I will edit the data file and get back to you guys.

Yup so editing the Data file, works. Just sucks I have to literally sift through HUNDREDS of items just to change 5 resources.... I still am curious why the oxide/config/StackSizeManager.json Doesnt work?

The config file is meant to add a sort of automation to the plugin. As in, if a new item gets added to the game, server owners have the option to change the stack size of the new item immediately, and not have to do so manually. For every new item.

WOLFN
Hi

We have been using the plugin for months now and after the last wipe we have to manualy type the stack size after every server restart.

We udated the both the file on the config and data folders but they do not load the required stack sizes.

Files

/oxide/config/StackSizeController.json
/oxide/data/StackSizeController.json

Resources that we been changing.

Wood 3000
Sulfur Ore 3000
Stones 3000
Metal Ore 3000

Server Details

Server Type: Community
Name: Voodoo SA | Noob Freindly

Both of those files are the same, and are the data file. The config file is completely different, see the plugin page for the default config.

Posted 6 years ago

Last updated 6 years ago

#15

And only change the DATA file with the plugin unloaded or the server off, Save and then reload the plugin