Khan
-
Posts
1,117 -
Joined
-
Days Won
8
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by Khan
-
Oxide already prevents duplicate command registrations internally. Commands are stored in a dictionary, and attempting to register the same command again simply results in a warning rather than creating another entry. Because of this, duplicate command registration cannot cause the error you referenced. The error Symbol table grew beyond unsigned short indicates that tens of thousands of unique strings are being inserted into Rust’s internal symbol table. This typically occurs when something repeatedly generates dynamic strings (for example entity names, or other identifiers) until the 16-bit symbol limit is exceeded. Stack Modifier does not generate dynamic commands, permissions, or entity names, and therefore cannot produce this error. In other words, Stack Modifier does not and cannot cause the issue you are experiencing. I would recommend checking other plugins or reviewing your server logs to identify what is generating excessive unique symbols.
-
First, Oxide already handles all command and permission registrations for plugins internally. Adding a manual guard like the one suggested would not resolve the error you mentioned. Second, there are no server logs provided in your report. Without the actual crash log or stack trace from the server, there’s no way to determine what is occurring on your end. Third, command duplication would not cause a server crash. Even if a command were registered more than once, Oxide handles that safely and it would not produce the error you referenced. If you're encountering a crash, please provide the full server logs around the time of the crash so the issue can actually be investigated.
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Yes that error very clearly states it's occurring in a method that I don't touch ( OnMaxstackable ) and it's a harmony patch created by Epic Loot there's nothing I can do to fix that. Please reach out to imthenewguy with a support ticket report. EpicLoot+Item_MaxStackable_Patch
-
@AlaEddineYahia Added that and a few other things. -
Changed Status from Pending to Fixed Changed Fixed In to 1.1.3
-
I honestly didn't think anyone was still using this thing. One sec /
-
Changed Status from Pending to Fixed Changed Fixed In to 1.1.6
-
Changed Status from Not a Bug to Fixed Changed Fixed In to 2.9.7
-
Changed Status from Pending to Not a Bug
-
Turns out that was DLC items.
-
stacks don't revert back to vanilla unless something happened to the config file, please send the current config file you have and the server log from when it wiped the config file.
-
If you happen to use a plugin on umod called Corpse Location please make sure you remove it as it is bricking player save data and causing server crashes. Regarding recyclers, they are working just fine for me, are you by chance using a mod for them? Additionally if you use a plugin on umod called Backpacks by whitethunder please make sure you are on the latest update since that also causes bugs with stacking if you are not on version 3.17.2
-
@FreezerGaming This plugin does not have that functionality built into it, the best you could do is edit these settings here "Currency Settings": { "Sets default currency, 0 = disabled, 1 = Economics, 2 = ServerRewards": 0, "Sets price": 15.0, "Sets Increment penalty to apply only when they purchase a revive instead of adding for each death.": false, "Sets Increment penalty for quick repeated use, 0 = disabled": 5.0, "Resets Cost Increment after x seconds, 0 = disabled": 1800 }, You could set the base price from 15 to 0. This would make it so that the first use is free. You could then set the increment penalty to true & set the penalty price. Then simply set the reset cost timer. That's about as close as you can get to doing what you want. At the moment, I would have todo a feature update to better support what your wanting todo with it. So basically at the moment, no it cannot do what you are asking. -
Changed Status from Pending to Closed
-
This issue is from a umod plugin called Corpse Location on umod. https://umod.org/plugins/corpse-location You need to update to latest 2.4.0 and wipe your server.
-
@Rust Admin 2.9.6 It's no longer in beta and is the latest release for live server use.- 202 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Changed Status from Pending to Not a Bug
-
That is occurring because the developer has not yet been made aware that new item creations don't have null parents anymore since last months updates and doing this results in items never being moved. the fix is to simply do this right before trying to move the item. if (item.parent != null) item.SetParent((ItemContainer)null); Even without stack modifier loaded you'd still have that problem with those plugins.
-
@Paul H. Teams only get deleted like that if the server crashes or if you are using some kind of plugin like clans that override teams. Vanilla teams don't get messed up normally. -
@Paul H. Thanks for the report. Stack Modifier doesn’t officially support or maintain compatibility with third-party plugins like Furnace Upgrades. With the amount of mods out there, it’s not realistic to guarantee compatibility with all of them. If this is the only reported conflict out of thousands of servers/mod combinations, that’s honestly a pretty good outcome. I’m continuing to add new features and fixes, and with the game itself updating multiple times a month, plugin developers also need to keep their projects maintained and compatible. I do my best to keep Stack Modifier stable and optimized, but cross-plugin compatibility ultimately requires effort on both sides.
- 202 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Are you currently using Custom Item Definitions? From the behavior you’re describing, this appears consistent with how that plugin modifies item data. It dynamically creates custom item instances, which can cause stacking logic to behave differently or produce unexpected results. If you are running Custom Item Definitions, that is very likely the source of the issue. For clarity: I do not officially support integrations with Custom Item Definitions or other plugins that fundamentally alter item definitions. Because those plugins modify core item behavior, they can conflict with stack logic in ways that are outside the intended scope of this plugin. If an issue is confirmed to originate from Custom Item Definitions (or similar plugins), I won’t be implementing compatibility patches specifically for it. If you'd like, you can temporarily disable it and test again that will confirm whether it’s the root cause.
