Khan
-
Posts
832 -
Joined
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by Khan
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
carbon isn't supported.
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
Changed Status from Pending to Closed Changed Fixed In to 2.0.2
-
Carbon is not supported on this plugin. Even when the compile error is resolved the plugin does not work on carbon.. Plugins that are supported by carbon would have the carbon tag, mine have never had such tag.
-
My discord id is khan8615 if you wish to show / discuss to better explain the problem I'm willing to listen / take feedback for design improvements.
-
Which doors? I just tried a wood door and shot 1 normal 556 bullet using an AK and it took 1hp off and did not trigger a raid. Only explosive bullets trigger raids on doors/walls*
-
That means the auto repair logic I painstakingly coded works. So congrats your good to go /- 186 comments
-
- 2
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Changed Status from Pending to Can't Reproduce
-
Pls try update 2.4.2 Most likely missing or invalid config items
-
Changed Status from Work in Progress to Closed Changed Fixed In to 2.4.2
-
Latest update should finally resolve all config problems with outdated configs. So pay attention to console output pls.
-
Alright listen peeps. The reason you are even getting those issues is because their is things wrong with your config files. This is also the reason why things aren't stacking for you or being edited properly in the UI editor, etc. This next update 2.4.2 should auto-fix them now As well as still output the problems found/fixed in console. If it finds anything it will output all of what it fixes in console. So pay attention. However another easier fix would have been to unload the plugin live on the server delete config and then load it and it would have self regenerated with the same stacks already set on the server except with a valid config this time. But of course nobody does this. So here I am wasting hours of coding to auto check for and patch your config files. So all this extra code is for you guys.
- 186 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Okie so after inspecting the config file i see the problem. The item display name has changed and my code check is in the wrong order to fix it. I'll prepare a new update to fix this automatically or you can manually edit the config to resolve it.
-
Okie, well still waiting on someone to send a config file.. Pretty sure I coded a fix, but I am not going to push an update out until someone sends me their bugged config to confirm.
-
Changed Status from Pending to Work in Progress
-
You'll need to send me your config file.
-
Using GUIShop & F1 spawning NPCs to pickup their loot and buying items from GUIShop results in stacks working just fine. So i have no problems with stacking. Here is my video, for the record i do not own a copy of Davids shop plugin or BotRespawn so i cannot recreate the error your showing me. Also, here. Plugins that give anything to players should be respecting the stack sizes set on the server so that would be a 3rd party plugin bug. I ran and maintained GUIShop on umod for about 5 years roughly and I had implemented special code that respects server stack sizes whenever any items where given to the player. As seen in the above video i made ^^. So that would be something to ask david for to add support that respects server set stack sizes when giving the players items. I took screen shots of the code I made in guishop I made that handles stack size checks accordingly and gives the player the items in stack sizes that respect the server set amounts.
-
Gee if only like their was a way to know that sort of thing? hmm weird, but incase you missed it here.
-
Report: Another bug that I was just told about is this: If a stack of an item is greater than that allowed by this plugin, say for example 500 of an item in a crate in a raidable base, and the stack limit is 100 with this plugin, a player could transfer that whole stack over to their inventory when he really should have made 5 piles of 100. @BetterDeadThanZed Their is an ignore admin check so that would only be a thing for admins ( anyone auth level 2 ) ( this is done due to F1 spawns to prevent issues )
-
@Snaplatack Aye, that feature has been looked into a few times and the problem is, that it would rely a lot on a specific oxide hook that a lot of 3rd party plugins either use or harmony-patch into the method before the hook is called. Which means the rate of 3rd party plugin conflicts would most likely sky-rocket and I don't want to really deal with the blow-back of that, I have a hard enough time keeping 3rd party plugin support as it is. But yes it is possible to do a feature update but honestly if I do it at all. It would have to be as a stack-modifier add-on and it would be a paid plugin + it would most likely have unknown 3rd party plugin conflicts. Other possible issues/problems with this request are: Overall Performance concerns and Possible High-Hook time warnings.
