-
Posts
753 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Martian
-
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.7.7
-
@Vergbergler I’ve just updated it with support for EpicLoot again.
-
Changed Status from Pending to Work in Progress
-
Hi, I had already added support for that. It might be due to an update from EpicLoot—I’ll test it again and see what might be going on.
-
Changed Status from Work in Progress to Can't Reproduce
-
Changed Status from Work in Progress to Fixed Changed Fixed In to 2.2.3
-
I’ve just released an update—please test it and see if it fixed the issue.
-
@Takeshi I’ve just released an update—please test it and see if the issues have been resolved. If not, please open a ticket and I’ll keep looking into it. -
Hi, of course! I’ll check that today. I had already made an adjustment to prevent sealed rooms, but I’ll look into this issue again. If possible, please open a support ticket for cases like this instead of posting here—it makes it much easier for me to track and manage the issues.
-
Hi, sorry for the delay.. I’ve been busy with other projects... I’ll take care of that this week for sure!
-
That behavior doesn’t seem to come from my plugin — I don’t have any GUI or setting that automatically adds Dungeon Lord NPCs. It’s likely coming from another plugin or configuration.
-
Upgrades taking all of a stack instead of the required amount
Martian replied to AltoSaxZeroCubicMetersBruh's Support Request in Support
Changed Status from Work in Progress to Fixed Changed Fixed In to 1.6.4 -
Could you please confirm this issue? There’s no such patch in the plugin, and I’ve been trying to track down the problem but haven’t been able to reproduce it. Is it possible that this error is coming from another plugin?
-
Upgrades taking all of a stack instead of the required amount
Martian replied to AltoSaxZeroCubicMetersBruh's Support Request in Support
Hello, I’ve just uploaded a new version — please check if it solves the issue -
Changed Status from Pending to Work in Progress
-
Hi, are you using carbon or oxide?
-
I’ve pushed a new update, check if is fixed now, here the problem dont ocurr.
-
Upgrades taking all of a stack instead of the required amount
Martian replied to AltoSaxZeroCubicMetersBruh's Support Request in Support
I’m unable to reproduce this on a clean setup, everything works correctly here. Could you help me narrow down what might be going on? Have you added or swapped in any “stack” plugin recently that changes how item stacks behave? Please run the "plugins" command and post the full list of installed plugins so I can see what else is running on your server. Do you have any other ideas about what might be conflicting (custom configs, other mods, server proxies, etc.)? Thanks for your help -
Upgrades taking all of a stack instead of the required amount
Martian replied to AltoSaxZeroCubicMetersBruh's Support Request in Support
Changed Status from Pending to Work in Progress -
Upgrades taking all of a stack instead of the required amount
Martian replied to AltoSaxZeroCubicMetersBruh's Support Request in Support
Thanks for the report. I’ll check it out and get it fixed. -
The first time the plugin runs after an update, it stores all the recyclers. If this was the first time you ran it, it should work fine on the next restart without needing to reload manually.
-
Thanks for the report. I’ve just released v3.4.1, which adds a null check for dungeon.InsidePortal.transform in the OnPlayerDeath hook to prevent that NullReferenceException. Please update to v3.4.1 and let me know if you still encounter any issues.
-
Changed Status from Pending to Fixed Changed Fixed In to 1.7.4
-
I’ve pushed an update that now saves each industrial recycler’s state to a data file and automatically restores them on server startup, preventing the rare issue where they’d reset to standard after a restart.
-
I’ve pushed an update that now saves each industrial recycler’s state to a data file and automatically restores them on server startup, preventing the rare issue where they’d reset to standard after a restart.
