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

TaskGarrison and taskCamp to trigger on internal eventhandlers #144

Open
nk3nny opened this issue Jul 10, 2020 · 4 comments
Open

TaskGarrison and taskCamp to trigger on internal eventhandlers #144

nk3nny opened this issue Jul 10, 2020 · 4 comments
Assignees
Milestone

Comments

@nk3nny
Copy link
Owner

nk3nny commented Jul 10, 2020

Explore enhancement:
TaskCamp and taskGarrison should trigger on internal eventhandlers instead of the "FIRED", "HIT" and "ENEMYNEAR" ones. It will allow for much more reliable conditions if we use our own eventhanders-- and it will escape problems because mission makers add their own.

It may also let clean-up be an easier thing.

@nk3nny
Copy link
Owner Author

nk3nny commented Oct 12, 2020

I suspect this system can be linked to #115
For cleanliness I will close for now. Implementation will not occur before 2.6 in either case.

@nk3nny nk3nny closed this as completed Oct 12, 2020
@jokoho48
Copy link
Collaborator

let it open when you have it assigned to 2.6.0

@jokoho48 jokoho48 reopened this Oct 12, 2020
@nk3nny
Copy link
Owner Author

nk3nny commented Apr 20, 2021

With the introduction of: https://community.bistudio.com/wiki/Arma_3:_Event_Handlers#Suppressed

BIS Suppressed eventHandler. That might be a better and faster approach to achieve the same. Suppressed EH also passes a bunch of other very interesting information too.. humm humm!

@nk3nny
Copy link
Owner Author

nk3nny commented Dec 16, 2021

I think this should be closed.

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

2 participants