Importing from Oengus does not handle co-op runs properly

[duncte123]

Oengus has several run types on the platform, one of these is COOP.

When the run type is COOP speedcontrol should import all runners into a single team as opposed to a team for each runner.

Oengus currently has no concept of a "team" when it comes to a run so handling stuff like COOP_RACE is going to be a bit more difficult.

An possible solution could be for speedcontrol to support a teams object within custom data, I would imagine an object to look something like this:

{
  "Team A": [
    "username1",
    "username2",
  ],
  "Team B": [
    "username3",
    "username4",
  ],
}

where the key is the name of the team and the array is a list of names that run. The username list would need to be in order when it comes to a relay but that is a concern for the end user.

[Planks]

Speedcontrol has a very simple schema for horaro imports as follows

In the runners field a comma deliniates members of a team and the text "vs." deliniates a new team

So a 2p coop race looks like

Player1, Player2 vs. Player3, Player4

I suggest making it possible to input these deliniators into the equivalent field in Oengus is more attractive and compatible than a custom data object as it can be used as-is as a string by the end user or broken out by regex into it's component parts

[duncte123]

I suggest making it possible to input these deliniators into the equivalent field in Oengus is more attractive and compatible than a custom data object as it can be used as-is as a string by the end user or broken out by regex into it's component parts

That is technically already possible if you input a custom runner name, but due to the way oengus is structured internally a seemingly simple change like this is deceptively difficult to actually implement