-
Posts
2,108 -
Joined
-
Last visited
-
Days Won
17
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Everything posted by ZEODE
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 73 comments
-
- #rust
- #marketplace
- (and 8 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 307 comments
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 307 comments
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 61 comments
-
- 429 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 307 comments
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 429 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- 2
-
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 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.
- 307 comments
-
- 2
-
-
- #bradley
- #bradleyapc
- (and 14 more)
-
- 429 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.
- 202 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 ??
- 202 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.
- 202 comments
-
- 2
-
-
-
- #stacks
- #rust stacks
- (and 22 more)
-
- 429 comments
-
- 1
-
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 429 comments
-
- #helicopter
- #helicopters
- (and 17 more)
-
- 307 comments
-
- 3
-
-
-
- #bradley
- #bradleyapc
- (and 14 more)