-
Posts
26 -
Joined
-
Last visited
RustV's Achievements
-
Understood, perhaps try on their Discord also if they are a little inactive. Unfortunately in this case it's something that needs editing within the HeavyCargoShipEvent .cs -
@SlayersRust DM the owner of HeavyCargoShipEvent, their plugin should be returning 'true', also. Should be a minor fix.
-
@Dave This is odd - shows the correct version when downloading on this side. Have just re-uploaded on the back end to be sure - can you re-check and let me know if your issue is now resolved or still persisting?
-
@TTK None have been identified to date.
-
@Dave Good idea. Added it to the suggestion list - if we get more requests for the same/similar thing i'll add it to dev roadmap.
-
@corndiggitydog Interesting, i have added it to the suggestion list - if we get more requests for the same/similar thing i'll add it to roadmap.
-
Changed Status from Work in Progress to Closed Changed Fixed In to 2.1.0
-
The latest update has a large number of bigfixes from the rust update and optimisations broadly. Several of which should prevent issues raised above. I will close this thread out as it has drifted from its initial query and another can be opened for additional support.
-
We've just released an update with a broad number of Rust update optimizations & bugfixes. One of which addresses an infinite ammo exploit. Download the latest update (and enjoy!)
-
It doesn't make sense that turret range would affect any other functions, unless there is something else modded in your custom server. First, try verify your server oxide version / steam update. Otherwise need to github share your files and I can have a look at it. You can share the link privalety in the support request you opened.
-
Hi, Lets finish troubleshooting this in the Discussion area seeing as all the chats are there already. I'll leave this support request open for the moment but unless you want to migrate comms back in here I may close it out in future, purely to avoid comms loss because I have so many parallel dev chats open in discord/codefling/lone/steam etc that double ups can sometimes get buried in notifications.
-
Changed Status from Pending to Work in Progress
-
Hmm, it shouldn’t need it unless another plugin/script is has caused a temporary Boolean error (a persistent one won’t disappear from rcon) but oxide.reload should fix. The other thing I would recommend is check the entity that owns (/places) the turret has the correct permission (TurretFury.use). I’ve just tested it in a fresh server with no other plugins and the infinite ammo function works with other config setting as default.
-
On a typical PVE type server with npcs, a turret range of approx 100 is a generally accepted range (to avoid excessive turret range harassing distant players etc). Regarding your issue with SAMs not targeting Heli: this plugin does not affect this one way or the other, aside from the standard SAM settings. I recommend ‘Heli SAMs’ on umod to achieve this.
-
Hi @Bubles Buternuts We can't replicate the issue you have mentioned. Can you confirm if you are using any other plugins that affect Turret settings?
