Matched pattern isn't the same across entries

[Fusezion]

Describe the bug
The matched pattern is not the same between all cases of parse and trigger/check/changemode
They're just all over the place

To reproduce

effect:
  patterns:
    test effect 1
    test effect 2
  parse:
    broadcast "Effect Parse Test: %matched pattern%"
    continue
  trigger:
    broadcast "Effect Trigger Test: %matched pattern%"

condition:
  patterns:
    test condition 1
    test condition 2
    test condition 3
  parse:
    broadcast "Condition Parse Test: %matched pattern%"
    continue
  check:
    broadcast "Condition Check Test: %matched pattern%"

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

Server information

• skript-reflect: 2.6
• Skript: 2.11.0
• Bukkit: Paper
• Minecraft: 1.21.4
• Java: 21
• OS: Windows 10

Additional context
This occurs with expressions as well I just didn't have test code on hand

[sovdeeth]

Cause is using the matched pattern value from the CustomExpression/CustomEffect init, rather than which's matched pattern, the lookup from the structure's info. Solution is to use which's matchedpattern for parsing as well.

Related, all matched patterns are one higher than expected due to the dummy pattern at 0, which should probably be corrected for as the user doesn't know it exists.