🐛BUG? minimum_requirements

[jovial lagoon]

minimum_requirements only determines the first written requirement.

This is how it is set up.

    click_requirement:
      minimum_requirements: 1
      stop_at_success: true
      requirements:
        discovered:
          type: string equals
          input: "%codex_has_discovery_mobs:mooshroom%"
          output: "true"
        perm:
          type: has permission
          permission: perm.mooshroom
      deny_commands:
        - "[message] &7You don't have 1 of the 2 permissions required."
    click_commands:
    - "[message] &7You have 1 of the 2 permissions required."

The %codex_has_discovery_mobs:mooshroom% returns “false”.
tradingcard.mooshroom% is True.
In this case, for some reason, the deny_commands are executed.

Next, rearrange the order of the requirements, putting “perm” first and “discovered” after.
Then click_command is now executed.
Is there something wrong with the settings?

Or is it a bug in minimum_requirements?

DeluxeMenus-1.14.1-DEV-196
PlaceholderAPI-2.11.6
paper-1.21.4-191

[near beacon]

you are not using them correctly, in order for the minimum requirement to detect a requirement you also need to include it as optional: true

      requirements:
        discovered:
          type: string equals
          input: "%codex_has_discovery_mobs:mooshroom%"
          output: "true"
          optional: true

otherwise both of the requirements must be met from the user

[jovial lagoon]

Thank you very much.
Thanks to your advice I was able to solve the problem.
I didn't see any information on “optional” on the Wiki...is there an up-to-date information compiled somewhere?

[near beacon]

i m pretty sure its there(?)

just hard to notice tbh