Build from Match Vision

Match Vision is public source you can use as a complex starting point. It is a complete Angular app—not a special SDK or a closed platform component—with dashboard, local match history, settings profiles, compact windows, and stream/in-game overlays.

Open the public repository · Detailed fork guide · MIT license

Run the reference

With Node.js 22.22.3 or newer:

git clone https://github.com/W3Booster/app-match-vision.git
cd app-match-vision
npm ci
npm start

Open http://localhost:8082/?view=dashboard&demo=1. Synthetic SDK data works without Warcraft III or a W3Booster login. Explore ?view=overlay&demo=1 and ?view=compact&demo=1 too.

Find your starting point

The SDK owns transport, authorization, retry, and immutable match state. Match Vision owns its Angular signals bridge, visual presentation, and persistence policy. Keep that boundary when adapting it.

Register your fork

1. Fork the repository into your own account.

2. In W3Booster Developer Mode, create your own app. Recreate the scopes and player/observer settings from the public reference definition, or adapt the components alongside your new schema.

3. Replace the local identity explicitly:

   Copy

   npm run app:fork -- YOUR_NEW_CLIENT_ID
   npm run check
   

4. Commit package.json and the generated Angular binding. Change branding, repository metadata, and deployment destinations.

5. Use Test locally with application URL http://localhost:8082/?view=dashboard&demo=0 and overlay URLs http://localhost:8082/?view=overlay&demo=0. Launch through W3Booster.

The fork command validates the new definition before changing local files. It does not alter production records or transfer ownership. Ordinary SDK init refuses an existing identity mismatch; use app:fork for deliberate replacement and w3booster:sync for later updates to the same registration.

Same reference app, separate source forks

In Apps → Examples, Match Vision appears as the Reference implementation. It remains the same installed app as in the library, with shared settings and ratings. We do not create a duplicate “example Match Vision.”

Your source fork is a new app. It has its own users, settings, grants, and review. Score policy belongs to the app; the host provides generic application storage and explicit capabilities. Source reuse also does not grant arbitrary OS access or bypass platform data-access requirements.

The source is MIT licensed; retain its notice and review the repository's third-party media notices. The official production deployment trigger is guarded to W3Booster's repository—configure your own static host for your fork.

Continue with the detailed repository guide and publishing guide. Prefer a smaller starting point? Use the minimal starter or a focused example.