Not this exact same bug, but another bug with holdAction is, is that when you add 2 hold actions to an object, 1 action will not have its action text.
1. Picture: The helicopter only has the custom Eject option
2. and 3. Picture: Was taken in the DAP Ghosthawk, it has both "Jettison Fuel Tank" and the Eject option.
The EJect option doesnt have its text shown tho, only the Jettison Fuel Tanks one

@davidovitch, as soon as you activate the action, you immediately assign true to test variable, which blocks the action from being shown. So I don't see any bugs here.

@julius, the fix is in Capsule mod.

Hi @schatten,

I understand why the action is no longer shown after test is set to true. However, the issue I am reporting concerns the action that is already in progress.

conditionShow should control whether the action is available before it is started. Once the hold action has begun, its continuation should be controlled by conditionProgress, which remains "true" in this example.

Here, changing the variable inside codeStart causes the progress icon of the currently running action to disappear, even though conditionProgress is still valid and the action continues.

The expected distinction would be:

• conditionShow: determines whether a new action can be displayed and started;

• conditionProgress: determines whether the currently running action can continue.

Therefore, setting test to true should prevent the action from being shown again, but it should not hide the progress icon of the action that is already running.

That distinction is the issue I am trying to report.

@davidovitch, thanks for clarification, that makes sense for me. But I'm afraid the fix may break existing missions. Maybe @bis_fnc_kk can say something about this issue?

@davidovitch, as a workaround you can use this code for codeStart param:

{
    hint "Started!";

    _target setVariable ["test", true, -clientOwner];
}