Skip to content
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

FRQ: Forward Danger Event #115

Open
mr-guard opened this issue May 1, 2020 · 1 comment
Open

FRQ: Forward Danger Event #115

mr-guard opened this issue May 1, 2020 · 1 comment

Comments

@mr-guard
Copy link

mr-guard commented May 1, 2020

For some mods it would be nice to forward the dangerCaused events to external functions.
An example Use-Case would be Overthrow, where "Seen"-Events can partially replace nearbyUnits/targetKnowledge checks.

Basically add a custom CBA EH around here:

Something like:

if (_causeChanged) then {
    ["LAMBS_dangerCaused", [_dangerCaused, ...]] call CBA_fnc_localEvent;
};

There might be a few other interesting events.

@nk3nny nk3nny added this to the 2.5.0 milestone Jun 7, 2020
@nk3nny
Copy link
Owner

nk3nny commented Oct 12, 2020

@nk3nny
Reminder to self. Add this to 2.5.

Two options: 1. Either fully track the FSM queue update information -- which will channel more information through the eventhandler, but will theoretically allow users to write their own handlers for FSM information. Neat.

  1. Only update and publish the current Queue selected in accordance to priority/profile rules.

  2. Or both.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants