-
Posts
2,096 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ZEODE
-
- 295 comments
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 424 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- 2
-
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
I've answered you several times. I have started working on it, I don't have an ETA as it's going to be a huge update IF I can work out how to make the AI better. The plugin is sold as is, yes it's maintained and there will be updates. But I am not setting a timescale. I work a full time job, have young kids and a family life which is priority, always. I also have other plugins which break with Rust changes/updates which also require my time. Now, I'm not going to keep repeating myself. That is my position on things, an update will happen, but there is no ETA and it wont come any faster just because you keep asking. That's just the way it is my guy, life is busy.
- 295 comments
-
- 2
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
You are incorrect, which is causing hook conflicts with all the other plugins out there which use that hook correctly, so it does matter. The maintainer of your abandoned free version has already corrected this. Yes, returning false will override default behaviour, but with the conflict issues. we see. Ultimately I don't care if you correct it or not, your customers are the ones who will have to deal with the conflicts you cause. I am just raising it to let people know it's not an issue with my plugin, so they can take it up with you. I'm out.
- 201 comments
-
- 2
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Well, since then I decided not to and you didn't reply to me so I am doing my way. Because there is no reason to change since my config option is already there to handle it. I will update my documentation to reflect that and highlight it for people who don't see it. I will instead add a check to only act on HeliSignal items (supply signals) but this will still conflict until you fix your return value from that hook. On another note, you STILL have not addressed your incorrect usage of the concerned hooks, which is after all the reason for the conflict in the first place. Yet you continually do not respond to this issue. Will you fix the error in your return code for CanCombineDroppedItem ??
- 201 comments
-
- 1
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
Why are you still blaming this conflict on me/my plugins? As I’ve pointed out, you are incorrectly returning false from that hook, which is incorrect. You should only return either null or true from that hook, but you repeatedly ignore this fact and do not correct your error. Please check the assembly and/or Umods Oxide API pages for that hook to see the correct usage, then there wouldn’t be a hook conflict with my plugins or anyone else’s who use that hook correctly. As I explained in DM to Khan, you can simply turn off the basic stack handling in Heli Signals within the config under General Options: "Use This Plugin to Control Stacking/Combining Heli Signal Items": false," Using that config option will unsubscribe from those hooks on plugin load, but that doesn’t alter the fact that this plugin is not returning from those hooks correctly, which is causing the conflict.
- 201 comments
-
- 2
-
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
- 424 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 295 comments
-
- 3
-
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 22 comments
-
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.
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
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.
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 22 comments
-
- 201 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
I will look at this when I am home and can get to the computer to make changes to this if needed. I think I added that so the people who wanted to add custom items to their loot tables with custom names could do so. But unless people are putting incorrect vanilla names I fail to see how it’s preventing stacking with vanilla items. But I can put a check in to only alter the name if a custom name is provided and update my documentation if needed. You haven’t reached out to me to mention this issue, if you had I would have looked into it. I get what you are saying about not having to do work for third party plugins, but a quick DM and we could have sorted this. It works both ways, I have reached out to you ages ago about your incorrect usage of the CanCombineDroppedItem hook, which after many, many updates you still haven’t corrected and incorrectly return false from a hook which should return type object, not boolean, so should only ever return true or null. This causes conflicts with every plugin which uses that hook correctly. I DM’d you about it, then after no reply opened a support thread here: https://umod.org/community/stack-modifier/52770-cancombinedroppeditem-conflict-return-error But you have not replied to that thread either. If you have any issues in the future with any of my plugins, just reach out to me and we can discuss and sort them easily, as other devs have done and as I have to other devs. Z
- 201 comments
-
- #stacks
- #rust stacks
- (and 22 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 295 comments
-
- 3
-
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 424 comments
-
- #helicopter
- #helicopters
- (and 17 more)