Match Mode GUI Config [AARD-2026]

[AlexD717]

Task

Match Mode GUI Config

AARD-2026

Symptom

Currently, if users want to customize the match length, penalties, etc., they have to make their own json file following proper syntax, which isn't exactly user friendly.

Solution

In the Match Mode Setup panel, a new option now exists to create a match mode config.

Pressing that opens up a new panel that guides the user to create their own config.

Pressing accept starts match mode with the new config, and also saves the config to local storage allowing it to be used again.
There is also a Download as json button at the bottom, that downloads the entire config as a json file, allowing it to be shared across multiple devices.

Verification

• After creating a configuration and pressing accept, your defined values is applied to the match
• Match mode config can be downloaded as a json, and then uploaded
• Can't download an invalid json config
• Can't enter letters into number only configs

---

Before merging, ensure the following criteria are met:

• All acceptance criteria outlined in the ticket are met.
• Necessary test cases have been added and updated.
• A feature toggle or safe disable path has been added (if applicable).
• User-facing polish:
  • Ask: "Is this ready-looking?"
• Cross-linking between Jira and GitHub:
  • PR links to the relevant Jira issue.
  • Jira ticket has a comment referencing this PR.

[rutmanz]

1. I think the button (and behavior) after going into that screen should be to save, rather than to start the match.
2. I think that it makes more sense to have a toggle to enable the height limit and extension limit, rather than saying to put in the string "Infinity"
3. I think having an edit button for an existing config (potentially instead of the delete button, and the delete button goes inside of the edit screen) would make sense
4. If there's an easy way to do it, I think the checkmarks should be replaced with a play button to make it clearer what they do

[AlexD717]

1. I think the button (and behavior) after going into that screen should be to save, rather than to start the match.

Done

2. I think that it makes more sense to have a toggle to enable the height limit and extension limit, rather than saying to put in the string "Infinity"

Done

3. I think having an edit button for an existing config (potentially instead of the delete button, and the delete button goes inside of the edit screen) would make sense

I think this is out of the scope of this PR. Will make a separate Jira ticket for this

4. If there's an easy way to do it, I think the checkmarks should be replaced with a play button to make it clearer what they do

Done

[PepperLola]

Looks good. I do think that we should omit the id when downloading and uploading the JSON and have it generate one when uploading, since it doesn't really make much sense to keep and could potentially cause issues later (and just clutters the config file, if someone wanted to edit it manually). I can create a ticket for that since it's not within the scope of this PR.