Skip to content

Inconsistent Check behaviour when using DependsOnKeys #458

@Herobrine24

Description

@Herobrine24

Issue:
When setting up an install option with multiple negative DependsOnKeys values and ACTION_ALLOW_SELECT as the NotMetAction, the install option will remain selected when NotMetAction is true due to first having selected the first install option as ordered in DependsOnKeys. If NotMetAction is true and the non-first option is selected, this conditional option will become unchecked.

Expected behaviour:
The selection of the first OptionKey causes the conditional install option to become unchecked.

Initial state:
Image

First OptionKey is selected:
Image

Non-first OptionKey is selected:
Image

Example Mod:
RemoveEnemyGrenades_1.0.zip

Example Mod with workaround:
RemoveEnemyGrenades_1.0.zip
A hidden OP_NOTHING option is used as the first OptionKey in DependsOnKeys to achieve the desired behaviour.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions