ZEODE
-
Posts
1,615 -
Joined
-
Last visited
Content Type
Profiles
Downloads
Forums
Store
Support
DOWNLOADS EXTRA
Services
Everything posted by ZEODE
-
Thank you, work has been crazy busy and also busy with the kids. But I will try and get on the test server this weekend and see if I can reproduce this and find the issue.
-
Thanks, in future though, please don't copy and paste the config like this, simply just upload the config file in the thread. I'll look into this when I have time and update. Can you explain more who gets the wrong amount and when?
-
please post your config file
-
Would you be willing to send me a list of the plugins you use on here or in DM ?
-
If you are using the latest of both then there shouldn't be any conflict because nivex accepted my patch to make both plugins compatible. Do you have any other plugins which control heli in any way?
-
Hi, are you using Loot Defender? Are you using the most recent versions of my plugin and Loot Defender if using it?
-
Changed Status from Pending to Closed
-
I haven't had any other reports like this, its also running on our servers just fine with no issues at all. What version of the plugin are you using? Please make sure you are using the latest version, also if you haven't already, try downloading a fresh copy and load that.
-
Changed Status from Pending to Not a Bug
-
Please see this:
-
Changed Status from Pending to Closed
-
The way the Rust game calculates heli HP and decides if it is killed or not depends on maths within the game code which is based on percentages of rotor health against overall HP. Try to use the default values as a guide to creating more reliable custom settings. For example, the default "Easy" heli in my plugin is the same as the vanilla patrol helicopter in the game. The vanilla HP stats are: 10000 Main heli HP 900 top rotor HP 500 tail rotor HP If we do the math: Top rotor: (900/10000) x 100 = 9% of total HP Tail rotor: (500/10000) x 100 = 5% of total HP For the heli damage to function as you expect you need to keep these % ratios, or the built in game code calculations are wrong, this is why you are seeing this discrepancy. So whatever you decide is your main HP is, let's say 100,000 as in your config. That means the main rotor HP should be 9% of that, which is 9000 and the tail rotor HP should be 5%, so 5000. I should probably add that info on the plugin page for everyone to know.
-
Yes, but on second look, I think a patch will be needed by nivex to Loot Defender. I'm looking into it now. -
The plugin Loot Defender does that, but currently Loot Defender will ignore all Heli Signals helis. I will add a config option to allow Loot Defender to lock called helis, this will achieve what you want by using Loot Defender. This will be on the next update.
- 399 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 16 more)
-
Do you have any other plugins which handle supply signals?
-
I don't know what you mean. Lock what?
-
Were you taking the heli or was it someone else's? Are you the server owner? If it fired rockets and then went away, that means it killed the player/team. If the player then respawned somewhere else it could fly to their new position (depending on how the server owner has the config). Also, in the config is an option to retire the heli on all team killed. There are a few variables which would cause this behaviour. Another reason is if the calling player remains hidden for too long and does not engage, the heli will either retire or go elsewhere.,
-
Also getting the same:
-
According to the Oxide coding rules, hooks of type Object should return either null or true. Hooks of type Bool can return either true, false or null. Therefore StackModifier is incorrect and the dev should fix that. Or you can change the return value within the "CanCombineDroppedItem " hook in StackModifier so that anytime it returns false, you change it to return true.
- 399 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 16 more)
-
Yes, add the custom skinned supply signals to the loot tables of your loot plugin -
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
