Jump to content

Khan

Creator
  • Posts

    836
  • Joined

Everything posted by Khan

  1. 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.
  2. Khan

    Stack Modifier

    Gee if only like their was a way to know that sort of thing? hmm weird, but incase you missed it here.
  3. 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 )
  4. Khan

    Stack Modifier

    @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.
  5. Khan

    TC

    Changed Status from Pending to Can't Reproduce
  6. Khan

    TC

    Okie so after an hour of messing around with the latest oxide update being bugged for download I finally managed to get my test server up. Please double check and make sure your oxide version in console reads 2.0.6164 ( do o.version in console for output ) this is the latest oxide update but the website download link from umod is old and gives people the wrong update. This is a new bug with the site today, theirs multiple reports of it in various discords. For me I had to manually change the link/url still because i was still getting the wrong oxide version from the umod url. https://github.com/OxideMod/Oxide.Rust/releases/download/2.0.6164/Oxide.Rust.zip << windows release. https://github.com/OxideMod/Oxide.Rust/releases/download/2.0.6164/Oxide.Rust-linux.zip << linux. Also if you where using the old link like me the file name changed from OxideMod.zip to Oxide.Rust.zip I do not have any issues with the tc accepting the set stack sizes provided in your config. I booted my server unloaded the plugin replaced the config with your config loaded the plugin and then proceeded to test in game stacks and all is normal for me. Even if i change the stacks in the UI with your config it still goes to a higher setting for me. ( Example 2m ) If you are certain you are on the latest oxide version and still have this issue, then please unload all other plugins and reload stack modifier. If the bug goes away then It is most likely a plugin conflict of some kind.
  7. Khan

    TC

    Aye, just waking up. It seems rust / oxide updated about 7 hours ago? in the wee hours of night. I will update my server an stuff an see whats up.
  8. Khan

    Auto CCTV Stations

    That is because the UI system for the cctv station is not coded the same as anything else in the game rust. Facepunch used a whole other system for it and it is not possible to properly fix the UI scaling problem. https://umod.org/community/auto-cctv-stations/40222-page-buttons-placement-bug Here is a 1 year old report on the issue. The best I could do is either code out every different monitor type and then make the players select which resolution they have, even if i did that their is no guaranty it would be in the right place since i only have a shitty 1080p 24in monitor and even then that wouldn't really work for wide-screen monitors because it would be so stretched and since i do not own a wide screen monitor i cannot even code support for it.
  9. I don't have davids shop or botrespawn so i cannot test those plugins. However guishop and serverwards are working just fine. Are you able to sort out if its specific items causing it ?
  10. Khan

    Stack Modifier

    The oxide permission system that would handle such a feature addition is simply too heavy to use and sometimes accessing the permission handler is null. Which to this day has still not yet been resolved. The permission handler system is so heavy that I actually code my own work arounds for it in simpler plugins. If i was to add a permission based stack system it would prove to be really heavy. + How would i handle automation item movements? Example: after 6 boxes daisy changed up to the output of a conveyor become full and start moving to box 7/8, etc already cause performance problems. I would have to add additional oxide hooks to even do perms & then sort out all kinds of other problems, its simply not worth it because in the end I fear the performance would be so horrendous that I'd have to pull the whole update. I hate to say this but honestly people need to stop trying to 'vip'-monetize every tiny thing. When it comes to core gameplay such as something so minor as stack sizes.. You shouldn't be limiting it anyways.
  11. version 2.3.9 works without any such issues in all tests on my machines.
  12. version 2.3.7 has other issues such as F1 spawns & crafting bugs. ( Example crafting multiple lanterns results in loss of fuel inside them when they go to auto stack )
  13. I've tested it and honestly I am not experiencing any stacking issues with GUIShop items or other 3rd party stack items given via commands. Or from killing npcs and looting. Even F1 and crafting items seems fine and to be working accordingly
  14. Khan

    unlock glitch

    Fixed in 1.0.4
  15. Khan

    unlock glitch

    Changed Status from Pending to Closed Changed Fixed In to Next Version
  16. Khan

    Error compiling

    Changed Status from Pending to Closed
  17. Changed Status from Pending to Closed
  18. Khan

    NRE error

    Changed Status from Pending to Closed
  19. Can you pls try this update and let me know if that issue goes away?
  20. Khan

    NRE error

    Ya, i've been trying to track this down as well lol
  21. Khan

    Error compiling

    add me on discord i have a feature update prepared for you to try out. @ khan8615
  22. Khan

    bug with lantern

    Changed Status from Pending to Not a Bug
  23. Khan

    bug with lantern

    That's only an F1 spawn bug from facepunch. F1 spawn items are not supported. Only shop items and native spawn loot or loot created by 3rd party plugins.
  24. Khan

    ui doesn't open for me

    Changed Status from Pending to Not a Bug
  25. Khan

    Console errors latest build

    Try the latest version 2.3.7
1.8m

Downloads

Total number of downloads.

8.5k

Customers

Total customers served.

128.3k

Files Sold

Total number of files sold.

2.7m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.