I recently updated and it seems to have been a bad move. I had to go through thousands of lines to readjust each value. But now I've found out there is a vanilla config file that overwrites the actions of the other config file I edited. For instance I set the stack size of Tech Trash to 500. Doesn't matter, the server only recognizes the value of Tech Trash in the vanilla file for some reason. So I edited that to 500, saved, reloaded the plugin. But it redownloaded the vanilla config file from github and overwrote the changes I just made.

How can I get around this?

I'm not using any of the multipliers. Just editing the value of each stack size individually.

Updating without READING ANYTHING, is indeed a bad move.

If only there were a way to tell, like a plugin description, or update notes



Darn.

In case you aren't going to read that, here comes the airplane.
- Datafiles are not used, period. Ignore them, pretend they don't exist.
- Again, basic visual search would have found this https://umod.org/community/stack-size-controller/39589-stacksizecontroller-datafile-configuration-conversion-tool which does everything for the lazy people.
- Editing stack sizes only works in the CONFIGURATION. Editing vanilla stack sizes does absolutely nothing except screw up your stack sizes when you UNLOAD the plugin. It does NOTHING to stack sizes otherwise.
- If CONFIGURATION (in oxide/config) changes aren't sticking, even after a plugin reload, there's probably going to be an error in console, otherwise it's improperly configured.

So why two configs?

If I can't edit the vanilla file, what's the point of this plugin? I've been using this plugin for 3-4 years, and you seem to be a new dev that took over this project and completely overhauled it with less features?

theshadow

So why two configs?

If I can't edit the vanilla file, what's the point of this plugin? I've been using this plugin for 3-4 years, and you seem to be a new dev that took over this project and completely overhauled it with less features?

You're dense huh? This'll be the last time I repeat myself.

1. There isn't and never has been 2 configurations. Configuration files are stored under oxide/config. You will see there is only 1 configuration file.
2. Under oxide/data is the DATAFILE not configuration, a datafile is not intended to be modified, and never has been since oxide was first created. Moving stack sizes to the configuration was correcting my mistake, and the mistake of other maintainers to provide a less confusing experience. Datafiles are like databases, the user should never ever touch them, that's why there are configuration files.
3. Again, you edit stack sizes in the configuration under the value IndividualItemStackSizes, which is populated when the plugin is first created. It functions EXACTLY like the datafile, it's just in the configuration where it should have always been. 
4. I'm the original developer of this plugin, which initially released on the old Oxide site roughly 7 years ago, and has since gone through at least 1 different maintainer, I honestly didn't keep track of it. I initially stopped updating it because my life was crazy, so other maintainers kept the lights on, thankfully. Then I reaquired the plugin, which largely hadn't been changed much, granted it's a rather simple process to change stack sizes. If anyone is new here, it's you. I believe back then my username was Waizujin.
5. Pretty much the same features it's always had are still present, although I did regress quite a bit in v4, as the hooks I was using were causing more issues than they were solving, and causing quite a few plugin conflicts, so I brought it back to the basics, primarily to build a strong foundation, considering this is one of the main plugins used by servers for 7 years. I'd rather maintain a solid plugin, than a buggy featured plugin. 

So once again, there isn't 2 configurations, and hasn't been since I created it 7 years ago. You're using it incorrectly which is why it's display unintended behaviour, user error. Modify the configuration values under InvidualItemStackSizes in oxide/config/StackSizeController.json and solve all your problems, or continue to repeat "why two configs" until you're blue in the face. Regardless I can not make this any clearer without literally doing it for you. I will not provider further support or continue this discussion. If you still haven't figured out how the plugin works, I strongly encourage you locate one of the other plugins providing similar functionality. 

Jesus christ man.

EDIT: Last ditch effort to identify where the disconnect here is; I want to state the reason there is still a datafile, which isn't a configuration file as it's name clearly indicates, is because Rust doesn't store vanilla stack sizes, so when you unload the plugin stack sizes stay the same. The datafile is there solely to ensure when the plugin is unloaded, that vanilla stack sizes are configured correctly without a server restart. The plugin does rely on this file some, and in a way that REQUIRES the file to be unmodifiable to prevent bug reports due to user error.

To avoid all of this confusion, when you moved the individual stack sizes from the data file to the config file (where it should've been in the first place) you should have also made your plugin automatically populate the individual stack sizes in the config file from the previous version's values in the data file. I recently opened a thread about your plugin regarding the confusing individual stack size modifications, turns out I was modifying the data file from the older versions that is no longer used. Server owners updating StackSizeController from older versions where the individual stack sizes were still stored in the data file will get confused.

runescape

To avoid all of this confusion, when you moved the individual stack sizes from the data file to the config file (where it should've been in the first place) you should have also made your plugin automatically populate the individual stack sizes in the config file from the previous version's values in the data file. I recently opened a thread about your plugin regarding the confusing individual stack size modifications, turns out I was modifying the data file from the older versions that is no longer used. Server owners updating StackSizeController from older versions where the individual stack sizes were still stored in the data file will get confused.

theshadow

So why two configs?

If I can't edit the vanilla file, what's the point of this plugin? I've been using this plugin for 3-4 years, and you seem to be a new dev that took over this project and completely overhauled it with less features?

Its obvious that regardless of your inability to read documentation you also are ignorant of the fact that the format has reverted back to the original concept where changes are made in the config and not the data file,
I have been using this since it launched in 2015 . I dont need a converter  i only need one hour to go through the Config and set the values i want, If i need to adjust any setting i can do it with the plugin running and reload it through RustAdmin consol with no difficulties at all,
As to why it has a data file , Nearly all plugins have data files and only a few of them allow you to make changes to the plugin using them , the majority allow you to make changes using the config file or a gui (such as kits plugin), all the time you have used complaining about the changes could have been used just editing the config,

And there will always be confused people, mainly because they dont read the documentation , If you want verification of that just read through the help topics from when this plugin was implemented or any other plugin,
https://oxidemod.org/threads/stack-size-controller-moved.9848/

Sorry i meant two data files

theshadow

Sorry i meant two data files

Because you didn't delete the old v3 datafile. That's no longer used. I don't have a way to remove it, it's not used in v4 at all, only vanilla defaults. You're safe to delete it if you've already converted stack sizes and don't need it for reference anymore.