-
Notifications
You must be signed in to change notification settings - Fork 54
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
Prevent ACEX HC transfer before unloading #479
Conversation
Reinforcement groups ownership transfer can break the unload waypoint, causing the infantry to fail to disembark. This PR checks for presence of ACEX headless, blacklists the vehicle and infantry groups, and removes the blacklist after they reach their waypoints.
Did you test it with and without ACEX? |
Actually, I copied in from the wrong editor window. The |
I don't know how the heck I uploaded such a wrong file. |
...lesExpansion/addons/modules_f_ares/Reinforcements/functions/fn_ReinforcementsCreateUnits.sqf
Outdated
Show resolved
Hide resolved
…/functions/fn_ReinforcementsCreateUnits.sqf Co-Authored-By: ampersand38 <ampersand38@gmail.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.
Could suffer from a race condition when the waypoint for some reason gets completed before setting the waypoint statement. The current scheduled framework does not make life easy.
@ampersand38 |
Will investigate further on Friday. |
Is this possible because |
Moved `setWaypointStatements` closer to `addWaypoint` to reduce chance of race condition.
@oOKexOo ^^ |
Tested on dedi server with this pbo. |
Yes it would, but the cleaner way is to put them in a unscheduled block (e.g. |
Reinforcement groups ownership transfer can break the unload waypoint, causing the infantry to fail to disembark.
This PR checks for presence of ACEX headless, blacklists the vehicle and infantry groups, and removes the blacklist after they reach their waypoints.