-
Notifications
You must be signed in to change notification settings - Fork 739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explosives - Add exclusion from dynamic defuse action #8171
Explosives - Add exclusion from dynamic defuse action #8171
Conversation
Uhm, strange. Its clearly allMines, yet Allmines didn't only build it also worked properly. Undocumented variable? Co-authored-by: BaerMitUmlaut <BaerMitUmlaut@users.noreply.github.com>
Co-authored-by: BaerMitUmlaut <BaerMitUmlaut@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does setVariable
work on mines? If so why not just do something like _mine setVariable [QGVAR(excluded), true, true]
.
That way seems cleaner to me and there's no problem with MP synchronization.
@veteran29 Nope, sadly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As it works with a GVAR should I add an event to allow easier MP compatibility or is this more of a write-your-own-thing for the developer that wants to call the functions?
Maybe event implementation would be better indeed. That way people can just call it with globalEvent
if they want it global, or local/targetEvent
otherwise (eg. certain people shouldn't be able to defuse).
Fix information in the function headers Co-authored-by: jonpas <jonpas33@gmail.com>
…lthzer/ACE3 into allow-defusalAction-exclusion
I have merged the functions and made an event available to call it. Currently the event is named "ace_allowDefuse" a nice accessible name, is this right or should I add the "explosives" prefix? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Event name is good.
Co-authored-by: jonpas <jonpas33@gmail.com>
Co-authored-by: jonpas <jonpas33@gmail.com>
Add the new event here as well please. |
Co-authored-by: jonpas <jonpas33@gmail.com>
In the "ace_explosives" header I'll assume? Although those looks like Called events not callable's. |
Yeah. It's documentation for both, you can reference one of the other sections for a Callable one. |
Good to merge from my side, it's been a while though so leaving to @PabstMirror to press the button. |
* Add GVAR(noDefusalAction) * add changes * Prep functions * Update addons/explosives/functions/fnc_excludeMine.sqf Uhm, strange. Its clearly allMines, yet Allmines didn't only build it also worked properly. Undocumented variable? Co-authored-by: BaerMitUmlaut <BaerMitUmlaut@users.noreply.github.com> * Update addons/explosives/functions/fnc_stopExcludingMine.sqf Co-authored-by: BaerMitUmlaut <BaerMitUmlaut@users.noreply.github.com> * Header Fixes Fix information in the function headers Co-authored-by: jonpas <jonpas33@gmail.com> * Remove Individual Functions * Compacter Functions * Event * remove tab (facepalm) * Jonpass' Review Fixes Co-authored-by: jonpas <jonpas33@gmail.com> * Fix exitWith mistake * Refractor of allowDefuse Co-authored-by: jonpas <jonpas33@gmail.com> * Update addons/explosives/functions/fnc_allowDefuse.sqf Co-authored-by: jonpas <jonpas33@gmail.com> * Update Documentation * Rephrase documentation * Another rephrase * Relabel Locality * Update addons/explosives/functions/fnc_allowDefuse.sqf Co-authored-by: BaerMitUmlaut <BaerMitUmlaut@users.noreply.github.com> Co-authored-by: jonpas <jonpas33@gmail.com> Co-authored-by: PabstMirror <pabstmirror@gmail.com>
When merged this pull request will
Add the functionality to exclude a mine from the "forced" defuse action the explosives module creates in interactEH
Additions in existing files
New Files
As it works with a GVAR should I add an event to allow easier MP compatibility or is this more of a write-your-own-thing for the developer that wants to call the functions?