The_Kiiiing

Is it possible that you are in a group that has this permission?

Did you modify the plugin? The error you sent me does not exist in the code. Please re-download the plugin and tell me if the error persists

did you enable the permission in the config file?

You can get rid of the button by enabling the crafting permission in the config file. Then just make sure your players don't have the permission

This is really weird. I've gotten similar reports from users on carbon, but I was unable to find the exact cause. I'm gonna have a look if I can find a workaround.

I'm gonna fix it with the next update

This looks like a framework problem to me, the code is correct. Please report it to the carbon team

Thanks for reporting. Are you on carbon or oxide?

This usually happens when there is a plugin error during server boot. Please check your logs for errors.

I'm gonna have a look at it. Apologies for the delay.

Changed Status from Pending to Not a Bug

Changed Status from Pending to Closed

Changed Status from Pending to Closed

Changed Status from Pending to Can't Reproduce

I just confirmed that this problem has nothing to do with the Loottable plugin. It must be caused by another plugin on your server.

Changed Status from Pending to Fixed Changed Fixed In to 1.2.4

Hi, such a feature is a ton of work to implement and I don't have much time at the moment - I added it to my to do list, but don't expect it in the near future. What I am currently working on is a way to let AI edit loot configs, which is also perfect for bulk edits.

This a namespace conflict with the Space plugin and I'm gonna fix it with the next update. This is a fairly simple fix and you can also do it yourself if you don't want to wait for the update: Just replace "Space" in line 756 with "UnityEngine.Space"

Hi, I understand the frustration, but I want to clarify that I work on this plugin alongside a full-time job, so I’m not able to provide instant support or 24/7 responses. That said, I’m glad to hear you were able to resolve the issue on your own.

Hey — I think the AI explanation you were given is missing a key part of how this plugin actually works. Yes, SetEnabled(false) only flips the in-memory flag — that part is correct. But the conclusion that stack sizes aren’t reverted is wrong. In this plugin, RevertStackSize() is called from Save(), and Save() is triggered whenever the UI is closed. So the real flow is: Disable in UI Close UI Save() runs RevertStackSize() executes Stack sizes go back to vanilla Because of that, the stack values are not left modified after disabling — they’re reverted as part of the normal lifecycle. The scenario described (values staying overridden indefinitely) doesn’t line up with how the code actually executes. If you’re seeing stacks not reverting, it’s almost certainly something else — leftover data in /oxide/data, another plugin touching item definitions, or the UI not completing its save cycle — not RevertStackSize() being skipped. I’d recommend testing from a clean state before assuming the core logic is broken. If you can reproduce it step-by-step on a fresh setup, I’m happy to take a look — but right now this looks like a misdiagnosis, not a bug.

Changed Status from Pending to Fixed Changed Fixed In to 1.2.23

Changed Status from Pending to Fixed Changed Fixed In to 1.2.23