Khan
-
Posts
932 -
Joined
-
Days Won
6
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Khan
-
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.
-
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.
-
That's just the auto updater doing its job repairing your config. For whatever reason stack sizes on specific items got set to 0 or negative - digits which will break the items. So its also self repairing the server. -
@SlayersRust It has a built in auto updater function so yes it should just auto update without issues.
-
Changed Status from Pending to Closed Changed Fixed In to 2.5.7
-
Update 2.5.7 Fixes any issues with this wipes changes. If you have not yet done so, pls update.
- 196 comments
-
- 2
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Changed Status from Pending to Closed Changed Fixed In to 2.5.7
-
@ZEODE You have been out of town / away on vacation so I've been waiting for you to come back before trying to reach out to you. & frankly it's been so long that I've forgotten. "But unless people are putting incorrect vanilla names" ?? That field is natively null on vanilla items. If it is supposed to be a vanilla item that field should never be set. Ever. Also for the record umod release is abandoned / not maintained. I only support codefling release. I haven't logged into umod in over a year. If you really wanted to reach out to me about a plugin you could simply do so in discord or here on codefling but umod is not a platform I even look at.
-
Changed Status from Pending to Gremlins
-
It's okie, no worries. I was just running out of ideas of what it could have been. I'm glad you got it sorted, I'll be closing this ticket now, have a good day /
-
No the Config file.. not the cs file
-
And you have the config set to true for enable ui ?
-
There should be an error or something in console then if nothing happens. Did you try removing the lang api plugin like suggested above ^^??
-
What happens in game specifically when you try to run the command /stackmodifier Can you make a video or screens shot it? Or screen share it on discord in dms?
-
Are you on the latest oxide release? I don't support beta branches or staging builds. Also, Lang API is not needed it's only a translation tool for none english folk / Perhaps that is preventing it from working properly for you? I don't think i've updated the files in awhile for it. Pls try removing Lang API & reloading stack modifier to see if it works.
-
Any items created by copy paste its self will not stack since item creation is bugged / not handled properly. Any items made from raidable bases should continue to work fine / stack without issues. I do not know which skins plugin you are referring to but i would suggest using the F1 menu and getting a few default items try stacking them and see if they stack normally & then try skinning them with that skins plugin & if they stop stacking then that means the skins plugin is breaking item creations. Sorry for the late reply codefling has been doing site modifications and notifications got broke for awhile I just noticed you had responded.
-
It should work out of the box without any plugins required. It does not use or need image library. All you have to do is load the plugin and in the game do /stackmodifier while having the oxide permission stackmodifier.admin It would help if you told me what framework you are running ( oxide or carbon )
