A simple, yet quite unknown feature on Toornament is the fact that you can Export the list of your participants or registrations directly from the platform, with a simple click. This will generate a CSV file, and is useful if you need to gather all your participants’ data at once!
A few weeks back was hosted the ESWC Summer, in Bordeaux, France. There, hundreds of participants and thousands of enthusiasts gathered for 2 days of intense competitive gaming action.
For this new edition, the ESWC once more trusted Toornament for its competition management, using the platform from registrations to result reporting on site, and as the main tool at the heart of their production line, with a Live Website and a streamlined video production, for both online and offline assets.
Let’s see how they used Toornament to create this new live environment!
Whether you’re a tournament organizer at heart, or have participated in tournaments and now wish to move forward and organize your own, Toornament is the platform to go, with a huge range of settings and possibilities for you to create your dream competition.
In this article, we’re going to see how to create and run your very first tournament, nice and steady.
|V2 Release is scheduled on the 31st of May, and all changes listed in this article will then become effective.|
With the new version just around the corner, it is time for us to address organizers/developers using our API on what’s about to change for them.
First of all, we’d like to take this opportunity to remind everyone that the Toornament API is still in a beta state, and a constant work in progress, changes are bound to happen, and all feedback is, as usual, appreciated and taken into account.
To the users of our Scheduling Tool or CS:GO Bots (eBot and AdminBot), nothing to worry about, those will still work perfectly fine, the bots just won’t be able to send stats for a while, but without creating any issue.
New pagination system
Two endpoints now have parameters pagination:
now has 100 items per page
now has 256 items per page (no change for tournaments with less than 256 participants)
Changes in the “Matches” endpoints
In all endpoints, the
timezone property now returns
null in matches and does nothing if you try to send Timezone information.
You have to use the one situated in the tournament’s endpoint.
date properties are now returned with the Timezone setting of the tournament.
When set to 1, the
with_games parameter will no longer return participants information. They can be found in the match opponent properties.
Deprecated feature: Schedule
We are not talking about match schedules here, but the Schedule feature, used to create events linked to the tournament.
This one goes down the drain entirely, and the endpoint returns an empty array.
The tournament engine has been rebuilt from scratch and now uses a brand new staging system.
stages API endpoints will no longer be working, a new version of the endpoints will be released soon.
Upon the release of the new version, game statistics as seen in CS:GO (when a bot is used), DOTA2, League of Legends and Bloodbowl 2 won’t be available.
Their return is a priority to us. In the meantime, all endpoints properties related to specific game statistics (opponent lineup, pick&bans etc.) will return
The API used to write statistics with the CS:GO bots will return
code 200 responses, but with no action attached.
The API documentation will be updated with all these modifications when the V2 is released on the 31st of May.