Data Structure
Structure and list of collected data
Players & Teams Structure
01. Players
-
Main Information
idhandle
-
Additional Information
first_namelast_namecountry_codebiosocialsvlr_id
-
Confidential Information
discord_idval_idrso_tokenrso_refreshrso_expires_atrso_linked_at
Link
-
player_idteam_idrolejoined_atleft_at
02. Teams
-
Main Information
idname
-
Additional Information
country_codewebsitesocialsbiovlr_id
Each team/player must have a name and an identifier; other information is added by the team/player or by administrators via tournament data.
Players/teams have the right to modify/delete 'Additional Information'.
The val_id and discord_id are not displayed or shared. They are provided by the player via Discord.
Tournaments Structure
03. Tournaments
-
Main Information
idnameregioncategorystatus
-
Additional Information
prize_poollocationstart_dateend_datevlr_id
04. Tournament_phases
-
Technical Structure
nameformatorderparent_id
Participants
List of teams registered for the event
Each tournament must have an identifier, a name, dates, a region, a category, and a status. They are collected by our team or upon request during a tournament addition request.
Matches Structure
05. Matches
06. Match_Vetos
07. Game_Maps
08. Game_Player_Stats
09. Game_Map_Rounds
10. Game_Map_Round_Player_Stats
We collect a lot of match information to provide detailed statistics. We retrieve:
- Basic match information (Mandatory)
- Match vetos
- Played maps, with results and stats
- Global match stats
- Each round's result (Who wins, and how)
- Each player's stats per round (KDA/Economy/Weapon/Armor/etc)
These stats are not always collected, but we strive to obtain them to display the most complete statistics possible.
News Structure
11. News
-
Main Information
idauthortitlecontent
-
Additional Information
statusis_featuredpublished_at
Link
-
Link between news and a tournament/team/player, allows display on profile.
Each news item must have an identifier, a title, content, and an author.
The status is hidden but allows for display (Draft = In progress, Published = Visible on site, Archived = Hidden on site but accessible via API).
Other Data Structure
12. Page_views
-
Main Information
uriviewed_atcount
We store the number of visits per page per hour; we do not store who visited, from which region, or the exact time.
This data is stored and private. It is never shared; we use it to visualize site usage and adapt our infrastructure as needed.