StackSizeController dosen't existNot An Issue

Im pretty sure the plugin is loaded, when I use /stack all it reports I do not have that permission, when I try to use oxide.grant group default StackSizeController it reports it dosen't exist. 

When I use the oxide.load and oxide.reload, same thing. 

Every other plugin is loaded and working. Not sure why this one is not. 

"StackSizeController" is not a permission, stacksizecontroller.canchangestacksize is. Either way, check your oxide/logs for errors.

Awesome thank you that comand worked. For some reason that did not populate when I used oxide.perms.

Thanks again, this solved it all

oxide.perms doesn't list permissions that exist, it lists permissions that are assigned.
The command Oxide.load stacksizecontroller reports 

Could not load plugin 'stacksizecontroller' (no plugin found with that file name)

Also the server does not seem to load the cfg file upon server restarts, no stack sizes that I had changed in the config takes place

Yet if I use /stackall 6000 it works without an issue in game. I had to also manually use oxide.grant group default stacksizecontroller.canchangestacksize to get it to work in game. This is the only aspect of the mod that is working currently. 


Merged post

So, ok this is weird. I do not get this..

Its fixed now, the issue is now 100% Solved.

I fixed it by installing ImageLoader to fix an issue with another mod. 

Seriously, after the first restart of imageloader now everything on this mod and issue is working. Oxide is reporting it, the config is being loaded, everything... Well, I wont complain Ill take the win haha

Could not load plugin 'stacksizecontroller' (no plugin found with that file name)

That command reply means that there is no filename named "stacksizecontroller", the plugin's filename is StackSizeController.

The permission is a requirement if not admin, so there's no surprise there that it was necessary.

Assuming you mean ImageLibrary, not ImageLoader, but that plugin doesn't get used or touched at all, so extremely unlikely to have resolved the issue.
Locked automatically