Read group counts from main site when automatching scrambles on scrambles matcher

[Sixstringcal]

When generating scrambles, I like to overgenerate a lot in case the absolute worst happens (two extra groups per round of each event). When I submit, this becomes annoying because I have to drag (and sometimes the drag and drop just breaks and I have to refresh the page and go through the process again: see thewca/worldcubeassociation.org#7220

It would be great if it could read the number of groups I have per round per event that I set in the main site and populate only A, B, C if I have 3. Obviously, if something happens like an extra round is used, but it's maybe set F from round 1 I'll have to manually do that, but cases like that come up less often, and the general case would make my life measurably improve.

[dunkOnIT]

Scrambles matcher is not currently being maintained - we are planning a rewrite to TNoodle to make scrambles matcher unnecessary.

However, I think this is a great point, as I do exactly the same thing (overgenerate scrambles) in my comps - so keeping the issue around to capture a requirement for the TNoodle rewrite.

[Jambrose777]

I'm not sure we'd want to implement this. It could potentially produce A LOT of errors. The reason we have the validator check that the # of scrambles match in the results and what's listed on the website is so that the Delegate can validate correctly what was used in the case of a mismatch. If everything is automatic based on the numbers, then the Delegate will never get a warning, and they could very easily not include scrambles that were used in the competition.

[Sixstringcal]

I see. Makes sense.

I guess for me it's just a pain when I habitually over generate and then manually remove. I also worry when I do that that I might grab the wrong one in drag and drop.

I would also point out that it's possible that a delegate might read the current message and think maybe they should just up the scramble set count on the site (although, with tnoodle basing things off the site, it's admittedly much less likely, and I'd like to think our delegates wouldn't do that, at least intentionally).

I think it's still a solvable issue, but I guess not as simply as I thought. I'll try to come up with something better.

[Jambrose777]

One idea might be to generate the correct amount using the log in feature, then using legacy generate your extra sets. That way the extra sets are separated out and still available if you need to use them.