Arena Entertainment
Proposed for Esports World Cup
Fans scan the stage QR to join games, predictions and prize draws between matches. Your crew runs each segment from one console.
Browser participation · no app install · no fan account
For event teams
15 formats in English, French and Arabic. Fans join by QR, with no app or account.
Four independent stages, crew permissions and manual or automatic pacing. Screen feeds for LED walls and OBS.
Arena and EWC designs for screens and phones, using the same games and console.
Participation, peak players and returning devices, with CSV exports and an optional reporting API.
Before rollout: confirm dates, stages, content, connectivity, prizes and support. Review the delivery scope →
Audience design
The same Trivia round in Arena and EWC, on the mainboard and phone.
Sharley’s standard design, with blue accents.
EWC artwork, typography and audience layout.
Screenshots from the application. Both designs use the same console; custom branding is agreed during setup.
Screen, phone and console
Game scenes, shared countdowns and results for the host and crowd.
Fans enter a nickname and stay connected between games. Reconnecting restores the current round.
Content, settings, live controls and audience tracking, with a Mainboard preview.
Game catalogue
Quizzes, crowd votes, phone arcade games and on-stage challenges. Open a format to see its rules and screens.
CS2 demo content shown.
Stage control
Each stage has its own QR, audience, game, language and standings. The console shows who is operating it.
Content preparation
Build question, image, sound and clip sets in one library. Stage timings and scoring are saved separately.
Player instructions
Fans see the goal and a short how-to while waiting. When the game starts, the phone shows the controls.
How a segment runs
Open the game lobby and invite fans to scan the QR.
The wall and phones share the countdown.
Fans answer. The operator tracks responses and reveals the answer.
Show the ranking, then move the same audience into the next game.
Prizes and rankings
Import the organiser’s prize codes and choose which results qualify. Each code is issued once, privately to the winner’s phone.
Champions ranks fans across games using placement points.
Prize codes and Champions explained →Event reporting
Review participants, peak concurrent players, time on air and returning devices by stage and segment. Export to CSV or use the optional reporting API.
The guide explains each metric and how rehearsal data affects reports.
Read the metric definitions →Access and safeguards
Crew receive console accounts and authenticated screen links.
The server validates actions and scores. Hidden answers and targets stay private until reveal.
Assign access by role. Content reviewers can work without stage controls.
No required email or phone number. The guide lists stored nicknames, results and device identifiers.
Audience capacity must be tested on the event hardware and venue network.
Deployment, continuity and current limits →Delivery scope
Confirm these items before setup and rehearsal.
Dates, stages, formats, running order and languages. Approved questions, media and brand assets.
Hosting, join links, venue network, LED / OBS and PA routing. Load testing and a rehearsed fallback.
Crew accounts, training and rehearsal. Confirm support hours, remote or on-site coverage and response times.
Prize stock, fulfilment and allocation rules. Report recipients, exports, data retention and integrations.
Next step
See a live round on the phone, the mainboard and the operator console, then go through your stages, content and event requirements.