...just the first player element is used, and the second element is ignored. Ideally, it should HTTP 400 because of the superfluous players; it makes no sense to consider a run valid if the resulting run is different from the requested one.
I've only been able to test this on a full-game category and a level category, both of which require exactly 1 player for runs, so I can't tell if the same counts for categories which have an "up-to" player count requirement.
For example, on a category which requires exactly 1 player for runs, if you supply:
...just the first player element is used, and the second element is ignored. Ideally, it should HTTP 400 because of the superfluous players; it makes no sense to consider a run valid if the resulting run is different from the requested one.
I've only been able to test this on a full-game category and a level category, both of which require exactly 1 player for runs, so I can't tell if the same counts for categories which have an "up-to" player count requirement.