Blyzer Events

Description

Blyzer.net is a platform for organising sports and e-sports tournaments, leagues and races – registrations, schedule, results, tables and statistics in one place.

Blyzer Events connects your WordPress site to your Blyzer.net events. Add an event, paste its API key and place the “Blyzer event” block, the Elementor widget or a shortcode anywhere on your site. Results update automatically as the organiser enters them on Blyzer.net – while the event is in progress even without reloading the page.

Features

• Easy to set up – a 3-step guide, a connection check right after you paste the key and a preview of the whole event
• “Blyzer event” block for the block editor and a “Blyzer event” widget for Elementor – choose the event and what to show, no shortcodes needed
• Live updates – while the event is in progress the results on the page refresh by themselves (every 60 seconds by default), only when the browser tab is visible
• Countdown to the start of the event and a “Register a team” button while registration is open
• Event info – logo, name, sport, status with a LIVE indicator, dates, venue and counts
• Whole event on one page with tabs – shows only the sections that have data
• Groups – standings tables like on Blyzer.net (played, wins, draws, losses, overtime results, score, goal difference, points, form)
• Playoff – a real bracket with connecting lines, highlighted winners, byes and teams not yet known; double elimination (winners, losers, grand final) and additional playoff are shown separately
• Matches – schedule and results grouped by round, group, playoff round or day, with live score, final and upcoming states
• Teams – a grid of team cards with logos (or initials when there is no logo)
• Players – statistics with the columns your event uses (goals, assists, cards …)
• Races – stage results and overall standings including DNS / DNF / DSQ
• Always looks like Blyzer.net – Blyzer colours, hexagon crests and the Rajdhani font bundled with the plugin (no requests to Google); dark by default, light or automatic on request
• Sends your visitors to Blyzer.net for more – the next and last matches with a “Full schedule on Blyzer.net” button, top 10 players with “All statistics on Blyzer.net”, every match, team and the event link to its page on Blyzer.net (opens in a new tab)
• Optional small “Results from Blyzer.net” logo under each widget (off by default)
• Works in any theme – styles are isolated, tables scroll on phones with a sticky team column, no jQuery
• Fast and robust – data is cached; when Blyzer.net is not reachable the last loaded data is shown and the site does not slow down
• Your own HTML templates – globally or per event – with a simple {{placeholder}} syntax
• Translation ready (Slovak translation included)

Shortcodes

Replace 123 with the ID of the event (shown in the “Available shortcodes” box when editing the event).

• [blyzer_tournament id="123"] – the whole event with tabs
• [blyzer_event id="123"] – event info
• [blyzer_groups id="123"]
• [blyzer_playoff_rounds id="123"]
• [blyzer_matches id="123"]
• [blyzer_teams id="123"]
• [blyzer_players id="123"]
• [blyzer_race_stages id="123"]
• [blyzer_race_standings id="123"]

Optional attributes:

• theme="dark", theme="light" or theme="auto" – colour scheme (all shortcodes, default from the settings, dark unless changed)
• limit="10" – show only the first N items; blyzer_players shows the top 10 by default, limit="0" shows all players
• upcoming="3" and recent="3" – blyzer_matches shows all live matches, the next 3 and the last 3 by default; upcoming="all" (or limit, or status) shows the full schedule as before
• group="A" – only the given group (blyzer_matches, blyzer_groups)
• status="played", status="upcoming" or status="live" – filter matches (blyzer_matches)
• phase="groups", phase="playoff" or phase="friendly" – filter matches by phase (blyzer_matches)
• team="45" – only matches or players of the team with this Blyzer ID (blyzer_matches, blyzer_players)
• group_by="round", "group", "day" or "none" – how matches are grouped; by default a league is grouped by round and a tournament by group and playoff round (blyzer_matches)
• order="desc" – newest matches first (blyzer_matches)
• form="yes|no", extra="yes|no", diff="yes|no" – show or hide the form, overtime and goal difference columns; by default they are shown when the data has them (blyzer_groups)
• extend="0" or extend="1" – only the main or only the additional groups / playoff (blyzer_groups, blyzer_playoff_rounds)
• sort="sum", sort="name" or the label of a statistic, e.g. sort="g" – order players (blyzer_players)
• sections="groups,playoff,matches" – which tabs to show (blyzer_tournament; also extra, teams, players, standings, stages)
• header="no" – hide the event info above the tabs (blyzer_tournament)
• live="no" – do not refresh this shortcode automatically while the event is in progress (all shortcodes)
• apply="no" – hide the “Register a team” button (blyzer_event, blyzer_tournament)

Block and Elementor widget

In the block editor add the “Blyzer event” block, in Elementor the “Blyzer event” widget. Choose the event (✓ means the connection works, ⚠ means the API key needs checking), what to show and optional settings. They show exactly the same as the shortcodes.

Live updates

When an event is in progress (Blyzer.net marks it as live, or a match is live), the results on the page refresh automatically. The page asks your own WordPress site for the new results, never Blyzer.net directly, and only while the browser tab is visible. The interval (60 seconds by default, at least 30) and turning it off for the whole site are in Blyzer Events → Settings; a single shortcode can turn it off with live="no".

Examples – top 10 scorers: [blyzer_players id="123" sort="g" limit="10"], next five matches: [blyzer_matches id="123" status="upcoming" limit="5" group_by="none"]

Templates

Every shortcode (except blyzer_tournament) uses a built-in template unless you set your own in Blyzer Events → Settings → Templates, or for a single event in the event editor.

• {{title}} – prints a value (HTML is escaped)
• {{totalStatistics.g}} – prints a nested value
• {{#items}} … {{/items}} – repeats the block for every item; for non-list values shows the block when the value is not empty
• {{^items}} … {{/items}} – shows the block when the value is empty
• {{@index}} – order of the item in a list, starting at 1
• {{count}} – number of items

Besides the fields from Blyzer.net the plugin adds ready-made fields, so templates need no logic – for example statusLabel, isLive, isWinnerHome, home.name, initials, playedAtDate, diffLabel or formItems. The full list for each shortcode is shown next to the template editor.

Styling

The widgets always use the Blyzer.net look (colours, hexagons, the Rajdhani font). Developers can still adjust details with CSS custom properties on .blyzer-events, for example --blyzer-surface, --blyzer-text, --blyzer-border, --blyzer-radius or --blyzer-font. All built-in elements use classes starting with bze-.

External services

This plugin connects to the Blyzer.net API to load the data of your events. Without it the plugin cannot display anything.

• Service: Blyzer.net API, operated by the Blyzer.net platform. Endpoints: https://www.blyzer.net/api/event/all (all data of the event in one request, used first). When it is not available (HTTP 404), the plugin remembers that for a day and uses up to eight requests instead: https://www.blyzer.net/api/event, /api/event/teams, /api/event/groups, /api/event/playoff-rounds, /api/event/matches, /api/event/players, /api/event/race-stages and /api/event/race-standings.
• What is sent: the API key of the event you entered in the event editor, in the X-Auth-Token HTTP header, and the standard technical headers of an HTTP request. The User-Agent is BlyzerEvents/<version>; WordPress – it does not contain the address of your site. As with any internet request, Blyzer.net sees the IP address of your web server. No data about your site visitors is sent. The key is never shown on your site, in the block or in any response of your site.
• When: from your server, when a page with a Blyzer block, widget or shortcode is displayed (or refreshed during a live event) and the cached data has expired – at most one request per event per cache period, no matter how many visitors there are. With the cache duration set to 0 a request is made on every page view (live updates still use at least a 10-second cache). Also when an event is saved or opened in the editor (connection check) and when you click “Verify API” in the list of events. When Blyzer.net asks the plugin to slow down (HTTP 429 with Retry-After) no requests are sent for that time.
• Terms of service: https://www.blyzer.net/sk/obchodne-podmienky
• Privacy policy: https://www.blyzer.net/sk/ochrana-osobnych-udajov

Stream links from the API are shown only when they point to YouTube, Twitch or Facebook (https). All other links point only to www.blyzer.net, blyzer.net or cdn.www.blyzer.net.

The Rajdhani font and the Blyzer.net logo are bundled with the plugin and loaded from your own site – no request goes to Google Fonts or to Blyzer.net for them.

Images (event and team logos, player photos, flags, sport icons) returned by the API are loaded by the visitor’s browser directly from Blyzer.net servers (https://cdn.www.blyzer.net and other blyzer.net subdomains), so the visitor’s IP address and browser information reach those servers. Only HTTPS addresses on blyzer.net and its subdomains are used. Live updates are loaded by the visitor’s browser from your own site (/wp-json/blyzer-events/v1/render), not from Blyzer.net.

Credits

• Rajdhani font by Indian Type Foundry, licensed under the SIL Open Font License 1.1 (assets/fonts/OFL.txt). Bundled as a Latin subset in WOFF2.
• Blyzer.net logo and name are trademarks of Blyzer.net, the author of this plugin.