ZEODE

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

Changed Status from Pending to Closed Changed Fixed In to Next Version

Changed Status from Pending to No Response

Changed Status from Pending to Closed Changed Fixed In to Next Version

Changed Status from Work in Progress to Fixed Changed Fixed In to Next Version

Also, just saying to turn on friendly fire isn't the answer, surely they turn off friendly fire for a reason, to turn it back on again as a workaround for a plugin conflict is not a solution. A quick look through your support section shows users having conflicts as I explained, this will always be the case unless you provide an API and allow devs to prevent Real PVE interfering in certain hooks under certain conditions. It is 100% necessary, IMO.

I disagree, I sent you a example showing all the hooks which will affect the working of my plugins Bradley Drops and Heli Signals. What I need and what many other devs will need is an API so that we can prevent the normal behaviour of RealPVE so it doesn't interfere with the working of our plugins. Similar to other PVE plugins that include a API call in their hooks such as "CanEntityTakeDamage" etc like TruePVE and other plugins. Currently there are many hooks which RealPVE will action and do things with that would be unnecessary and unwanted for the correct working of mine and others plugins. We just need a way to prevent RealPVE interfering in those instances.

Between us we will get the issue resolved

I have identified many Oxide hooks which are causing conflict with my Heli and Bradley plugins and potentially many other plugins out there too. An API call at the start of these hooks I have identified (and probably many others) that any dev can use in their plugins would be required for complete compatibility now and going forward, not just for my plugins, but for potentially many other plugins out there too. I have forwarded on some modifications to IIIaKa that could be used to make compatible with my plugins alone, but if API calls were implemented, it would be very easy for me to add code to my plugins to handle this and work with any changes made, and any other dev too.

https://discord.gg/KXJBwZ6uj9

Please join my Discord for a solution

Please join my Discord so I can help you further

Changed Status from Pending to Work in Progress Changed Fixed In to Next Version

You wont be able to fix it, the plugins need some re-writing to fix the conflicts. I have reached out to the other dev and we will work it out. A update will come to fix ASAP.

Can you confirm by testing calling a heli with team while Real PVE is unloaded? It might save me hours investigating this

I have reached out to the dev to see if they will issue a licence to enable me to test, waiting to hear back, without it I am unable to. If you are able to test without Real PVE loaded and it works as it should, at least we know where the issue is or to look elswhere.

I know compatibility with TruePVE is good, I have no experience with Real PVE. Easiest way to see would be for you to test with Real PVE unloaded, see if damage occurs then.

Changed Status from Pending to No Response

I have checked over my code for damage, and have concluded that it is good. So there must be a conflict somewhere with your PVE plugin or with plugins which control damage to and from helis or other entities. What sort of plugins like that do you have?

I have another report of this and have already looked into it. My code to handle damage is good, so it must be a conflict with another plugin, possibly a PVE plugin, which handles player damage from Heli. What PVE plugin do you use and what other plugins to control heli damage etc?

Changed Fixed In to Next Version

Changed Status from Pending to Work in Progress