Khan

Jet event is a known problem that plugin requires updating to fix it. Jet event creates the items incorrectly. & radiable bases is fine but if you used the copy paste plugin to create items it cannot create them correctly and wont stack with anything else. You can test this on a vanilla install with just copy paste installed and see that they don't stack as well.

You have a lot of plugins, it could be a couple different ones causing issues, I've narrowed the list down a bit for you to test. You'll need to boot up a vanilla test server with just stack modifier installed. Then add these one at a time. And test each plugin with stack modifier 1 at a time to test stacking to see if it bugs out. Even if you find 1 that is causing stack issues it could still be multiple causing issues. So make sure you fully test the list. aQuarry NoDurability ItemSort SkinController AutoFarm BoxLooters DropInventory JunkyardEvent

In server console if you type plugins it will output a list of installed ones can you post that here in the support thread? It's most likely a plugin or two creating the items wrong thus preventing the stack.

It'll work, they just won't stack. These are just plugins that never got caught that had been causing stack issues. Its not our job to ensure 3rd party plugin support but I do my best. In cases with stack issues its almost always due to other plugins with improper code.

@Kapco411 Yes, he is setting the vanilla name when he should not be doing so.

Changed Status from Pending to Closed

If you cloned your live server over to the test server you should have no issues re-creating your bug. & then doing the diagnostic steps, so honestly I don't see how you couldn't sort out what plugin is causing it.

Again, its not stack modifier but most likely a plugin conflict since it literally works flawlessly for everybody else including myself. + it was working flawless for you until you either added a new plugin or updated one so more then likely a plugin conflict. if you use any of imthenewguys works it's more then likely one of his plugins causing issues with it since he directly harmony patches into the default hook methods & over-rides logic which can cause errors in stack modifier due to how he's handling the logic in his. In-fact if you remove all your other mods/harmony patches and rebooted with just stack modifier I would bet it boots without issue like mine does. So perhaps rex if you did that and found out which one is causing the bug for you then maybe just maybe we'd get somewhere..

Changed Status from Pending to Can't Reproduce

Or do you have another harmony patch installed already for industrial ?

Are you on carbon or something ?

No idea, perhaps you have a plugin conflict with something? Never seen an error like that before. I would recommend trying a vanilla server with no other plugins installed & then reboot with a fresh install of stack modifier & see if it boots. I currently have no issues with reboots on the latest update.

@r0gi Where you about to get it sorted?

It should work just fine, but if you are free today sometime i will need help testing it on my test server since this is a player vs player issue & i'm alone, lol. My discord id is khan8615

Changed Status from Pending to Closed

At the moment technically no, not without a feature update. But doing so would change the vanilla game behavior that facepunch had intended to be. Perhaps you could simply set the repair time to the same time as the raid-block time? This won't be perfect but would increase the repair time by a fair bit.

Just so you understand how the default game logic works. Facepunch natively doesn't allow repairing of a recently damaged block. They make you wait 30 seconds before allowing repair of it. So what i do is allow you to change that time to whatever value you want it to be.

You can change the default repair time allowed inside the config, facepunch default is 30sec.

If you have either of these plugins installed you'll need to remove them & then reload console spam cleaner.

Changed Status from Pending to Not a Bug

Alright so it looks like this plugin handles item creation wrong like i've been seeing with a bunch of others lately. The item.name field is reserved for custom item names only & this plugin is setting the vanilla names on the item.name field when natively their supposed to be null thus preventing stacks with other vanilla items from the game.

This is the first i am hearing of it. Things won't get fixed if you don't report issues you find ya know. What xp system are you referring to? Can you link the plugin page for me, pls.

Changed Status from Pending to Not a Bug

Items should not be having the item.name field set unless its a custom name is the thing. If skinner is setting the item.name field for vanilla items then that is the problem. The item.name field should not be set for none-custom items & i do not recommend you removing this check either since it will break other stack support for other plugins that rely on only the item.name field being set to identify a custom item creation to do x y or z in their plugin/code logic. Overall it sounds like user-error.