You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oengus Schedule Import consider every multiplayer run as races putting each player into their own team.
While Oengus doesn't provide a way to parse players into team like it's usually done (by hand) on horaro with commas and vs, it provides a runType (SINGLE,RACE,COOP,COOP_RACE,OTHER,RELAY,RELAY_RACE).
Handling anything other than OTHER, COOP_RACE and RELAY_RACE is pretty straight forward to handle.
I guess it's safe to put players in their own teams when OTHER (probably only used for Setup buffer).
RELAY_RACE and COOP_RACE are more tricky, even though they are very rare. Maybe we could assume there's only
teams of equal sizes ? and that the first half of the runners array is team 1 and the second half team 2 ?
But I don't think Oengus offer marathon organisers to sort the runners.
I've create a feature request on Oengus #oengusio/oengusio/issues/141 but I doubt it will be any kind of priority anytime soon
The text was updated successfully, but these errors were encountered:
Oengus Schedule Import consider every multiplayer run as races putting each player into their own team.
While Oengus doesn't provide a way to parse players into team like it's usually done (by hand) on horaro with commas and vs, it provides a runType (SINGLE,RACE,COOP,COOP_RACE,OTHER,RELAY,RELAY_RACE).
Handling anything other than OTHER, COOP_RACE and RELAY_RACE is pretty straight forward to handle.
I guess it's safe to put players in their own teams when OTHER (probably only used for Setup buffer).
RELAY_RACE and COOP_RACE are more tricky, even though they are very rare. Maybe we could assume there's only
teams of equal sizes ? and that the first half of the runners array is team 1 and the second half team 2 ?
But I don't think Oengus offer marathon organisers to sort the runners.
I've create a feature request on Oengus #oengusio/oengusio/issues/141 but I doubt it will be any kind of priority anytime soon
The text was updated successfully, but these errors were encountered: