Khan
-
Posts
284 -
Joined
Recent Profile Visitors
7,444 profile views
Khan's Achievements
-
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.
-
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. -
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 ?
-
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.- 52 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 15 more)
-
version 2.3.9 works without any such issues in all tests on my machines.
-
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 )
-
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
-
Fixed in 1.0.4
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed
-
Changed Status from Pending to Closed
-
Can you pls try this update and let me know if that issue goes away?
