Tournament
A Tournament
object describes a tournament for which a single result is published. A Tournament
consists of a number of Match
objects, a number of Registration
objects, and other optional information.
name | String | The tournament's name. |
---|---|---|
short_name | String | An abbreviated version of the tournament's |
tournament_site | TournamentSite | Where this tournament happened. |
scoring_rules | ScoringRules | Validation rules for scoring matches in this tournament. |
start_date | Date | The tournament's start date, including time zone, as an ISO 8601-formatted string in the tournament's local time zone. |
end_date | Date | The tournament's end date, including time zone, as an ISO 8601-formatted string in the tournament's local time zone. |
registrations | Array of Registration | The organizations registered to play in this tournament. |
phases | Array of Phase | The phases of play in this tournament. |
rankings | Array of Ranking | The rankings used at this tournament. |
audience | One of the following:
| The intended audience of the tournament. |
level | One of the following:
| The level of the tournament, within the context of its |
question_set | String | Free-form string of question set(s) used at this tournament. |
content | One of the following:
| The subject matter of the tournament question set(s). |
info | String | Free-form string of other information relevant to tournament. |
TournamentSite
name | String | The tournament site's name (e.g. "Hyatt Regency O'Hare"). |
---|---|---|
place | String | The location of the tournament. Free-form; the purpose is to enable people to find the site. An example might be "9300 Bryn Mawr Avenue, Rosemont, Illinois". |
latitude | Number | The latitude of the tournament's site (for geolocation). |
longitude | Number | The longitude of the tournament's site (for geolocation). |
ScoringRules
name | String | The name for this set of scoring rules. |
---|---|---|
teams_per_match | Number | The number of teams that participates in each match. If omitted, assume |
maximum_players_per_team | Number | The maximum number of players that may be active at once, per team, in a match. If omitted, assume |
regulation_tossup_count | Number | The standard number of tossups heard in a match. If omitted, assume |
maximum_regulation_tossup_count | Number | The maximum number of tossups heard in a match that does not go into overtime. (Different from |
minimum_overtime_question_count | Number | The smallest possible number of overtime tossups or tossup-bonus cycles (as determined by |
overtime_includes_bonuses | Boolean | Are bonuses used in overtime? If omitted, assume |
total_divisor | Number | The largest integer that is guaranteed to be a factor of a valid final score for one team in one match. If omitted, assume |
maximum_bonus_score | Number | The maximum possible score on a single bonus. Omitting this means there are no bonuses. If present and |
bonus_divisor | Number | The largest integer that is guaranteed to be a factor of a valid score on a single bonus. If omitted but |
minimum_parts_per_bonus | Number | The smallest number of parts that may exist in one bonus. If omitted but |
maximum_parts_per_bonus | Number | The greatest number of parts that may exist in one bonus. If omitted but |
points_per_bonus_part | Number | The number of points earned for a correct answer to one bonus part. Omitting this while specifying |
bonuses_bounce_back | Boolean |
|
lightning_count_per_team | Number | The number of lightning rounds received by each team in each game. If omitted, assume |
maximum_lightning_score | Number | The maximum possible score on a single lightning round. If omitted but |
lightning_divisor | Number | The largest integer that is guaranteed to be a factor of a valid score on a single lightning round. If omitted but |
lightnings_bounce_back | Boolean |
|
answer_types | Array of AnswerType | The different answer types possible in this tournament. |
AnswerType
An AnswerType
object has details about how tossups can be answered. If you’re talking about the traditional -5/10/15 answer types or some subset thereof, you can skip this and use the value
field instead.
value | Number | The number of points a player receives for this answer type. |
---|---|---|
label | String | How to label this answer type on reports. If omitted, turn the |
short_label | String | How to label this answer type on reports when space is limited, perhaps in a table column header. If omitted, use the |
awards_bonus | Boolean | Whether or not the team that gets this answer value will next receive a bonus question. If omitted, assume |