-
Posts
2,149 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ZEODE
-
You’ve not given any detail on how or when this error has happened, or under what circumstances. But it appears something in that part of code was null/destroyed. I will check to make sure I haven’t missed a null check somewhere.
-
- 314 comments
-
- 3
-
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
I believe I have identified what might have caused this, assuming you have the item shortname correct. Also I did find a minor issue which could occur with item creation which has been fixed. But could it have been a typo in the shortname? This would then cause an issue as the item would fail and I failed to null check for this.
-
Changed Status from Work in Progress to Closed Changed Fixed In to Next Version
-
- 22 comments
-
Please don't copy and paste your config file in future, uploading it is the way since its so big. This plugin will be getting a overhaul soon so I will look at all issues then. Usually if players arent getting damage its an issue with how people set up rules for their PVE plugin. Is it a PVE server? If so look at your rulesets.
-
Changed Status from Pending to Not a Bug
-
Then your players are not doing very well and leaving the heli for too long without attacking it, unless its retiring in the middle of a fight. In which case either a player in the team is using the retire command or another plugin is interfering with it
-
They work with this config option: "Number of rockets to fire during orbit strafe (Default = 12)": 12, Number of rockets to fire during the orbit strafe is set there, the default = 12. The variance allows you to specify the maximum variance either negative or positive of additional/less rockets to fire during an orbit strafe. So as default, it will fire a maximum of between 9 and 36 rockets during an orbit. ie 12 - 3 = 9 and 12 + 24 = 36. The default config options match the default Rust numbers for vanilla heli. The actual number is chosen at random between the specified range as set in the config.
- 435 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
Changed Status from Work in Progress to Closed
-
Changed Status from Pending to Closed Changed Fixed In to Next Version
-
Changed Status from Pending to Not a Bug
-
Changed Status from Pending to Work in Progress
-
Also, check you have correctly configured the custom reward item in the config.
-
Some context on how and when this error occurred would be great, this gives me nothing to go on.
-
Changed Fixed In to Next Version
-
Using that hook wont change the way this plugin works with LockOnRockets, however, I have identified the issue and it will be fixed in the next update. Without using OnEntityKill.
-
This is impossible, unless you have a config error or another plugin is conflicting and preventing heli gun fire. Upload your config file here for me to check if you like.
-
Changed Status from Pending to Not a Bug
-
Already a config option, although a command is not necessary. Check the config file under Patrol Helicopter Options
-
- 435 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
Changed Status from Pending to Closed
-
Yes, this is probably due to the default heli lifetime for vanilla helis being set at default value. There is a server convar for this value "heli.lifetimeminutes". I will address this in a future update, but for now try setting this convar to the longest you will need for your heli profiles (set to the highest despawn time you use) in your startup or server.cfg file. Remeber the convar is minutes, not seconds.
-
It's possible, but will be for a future update. Once I have got on top of the few remaining bugs on this plugin I need to give Bradley Drops some love Haven't had any reports from anyone else about this, no. I am working on Heli strafe to address another bug though and this will bring improvements which might sort this issue too.
- 435 comments
-
- #helicopter
- #helicopters
- (and 17 more)