Client Overview
The ZCORE platform has two parts: the web panel at zcore.club and the Windows launcher that runs on your machine. This page covers both — the launcher is where most things changed recently, so it gets the larger share.
Windows Launcher
The launcher is the desktop app you start to inject modules into your game. It has a fixed 720×420 window with four screens you'll see during a normal session: splash, login, home, and the inline update overlay.
Splash screen
The first screen on every start. The launcher checks the backend, queries platform status, and pulls update information.
You'll see a breathing logo, a progress bar, and a status pip with one of these labels:
| Label | What's happening |
|---|---|
INITIALIZING | App boot, font + window init |
CHECKING SERVER | Reaching api.zcore.club |
CHECKING UPDATES | Comparing your local build against the deployed one |
READY FOR LOGIN | All good — login form appears next |
SERVER ERROR | API unreachable — see Troubleshooting |
If the backend reports maintenance or offline status, the splash stays up with the operator's message instead of advancing to login. There's nothing to do — wait for the announcement on Discord that the platform is back.
Login
The login screen has a username field, a password field, a Remember me checkbox, a Forgot password? link, and the Sign in button.
- Remember me — when checked, your credentials are stored locally and the launcher auto-logs in on the next start. The stored copy is encrypted against your Windows user account, so another user on the same machine can't decrypt them. Unchecking the box on a later login clears the stored copy.
- Forgot password? — sends you to the recovery flow on
zcore.club. - Login binds your account to the machine's hardware ID (HWID). The first successful login locks the binding; subsequent logins from a different machine fail with
Hardware ID mismatch — contact supportand require an HWID reset from your Profile.
If the platform is in maintenance mode you'll see "System is in maintenance mode. Try again later." — log in again once it's back online.
Auto-update (post-login)
After a successful login, the launcher compares your local build with the deployed one. If they don't match, an update is applied automatically:
You don't need to download anything manually — the launcher swaps itself out, then restarts. The whole thing usually takes a few seconds. If the download fails (network drop, etc.) you get a SERVER ERROR on the splash; just relaunch.
Want to keep the same launcher window open across an update? You can't — Windows can't overwrite a running .exe, so the launcher exits and the new build comes up in its place.
Home view
The post-login screen has four horizontal regions, top to bottom:
| Region | What it does |
|---|---|
| Top bar | Brand mark, settings gear, your user pill (avatar + name) |
| Hero | The currently selected game with its subscription days remaining and a large Inject button |
| Game rail | One tile per game you have an active subscription for — click to switch the hero |
| Status strip | Live system indicators (see below) — also shows the launcher version |
Status strip
Each pip lights up green when the requirement is satisfied:
| Pip | Meaning |
|---|---|
| EFI | The ZCORE EFI hook is active on this boot — set up by booting from the EFI USB stick before Windows started (Installation step 4) |
| Driver | The kernel driver is loaded and responding (turns green after first inject) |
| HVCI | Hyper-V Code Integrity (Memory Integrity) is off — required |
| SB | Secure Boot state — informational |
If any required pip is red, injection will fail with a clear error from the launcher. The pre-flight is so you catch the problem before clicking Inject. See Troubleshooting for fixes.
Injection
Click Inject on the hero. The button fills as a progress bar and labels each stage:
| Stage | What's happening |
|---|---|
Checking driver | Probing whether the ZCORE driver is already loaded |
Loading driver | Loading the driver (skipped if already loaded from a previous inject) |
Authorizing | Backend confirms your subscription and HWID |
Downloading | Pulling the per-game module |
Launching | Starting the module process |
Running | Inject succeeded — module is attached to the game |
The button turns green with a ✓ on success. From here you can switch focus to the game; the launcher window can be closed.
If the inject fails, the button turns red and the message names the stage that failed. The most common causes are listed in Troubleshooting.
Re-inject
If you click Inject again (e.g. after restarting the game) the launcher automatically terminates the previously launched module and starts a fresh one. You don't need to manually kill anything — running two modules at once isn't supported and the launcher prevents it.
Settings (top-right gear)
Toggle the in-launcher options:
- Window appearance preferences (when applicable)
- Sign out (clears the saved auth session; "Remember me" credentials stay until you uncheck the box on next login)
Points & heartbeat
While the launcher is signed in it sends a heartbeat every 5 minutes. You earn 1 point per heartbeat, accumulated on your account and visible on your profile.
Session types
The same login backs two session formats depending on where you authenticate:
| Type | Where | HWID required | Duration |
|---|---|---|---|
| Web session | Browser at zcore.club | No | 8 hours |
| Client session | Windows launcher | Yes (locked at first login) | 30 days |
Web Panel
Everything you do on the launcher has a mirror on zcore.club. The web panel is what you use to buy, manage, and review — the launcher is the operational tool.
Dashboard
Your home screen on the web. It shows:
- Your games — active subscriptions with direct inject access from the browser (web session)
- System status — whether the ZCORE backend is online, in maintenance, or offline
- Client version — current launcher release and download link
- Active subscriptions / pending purchases — quick count
- Game & module status — per-game operational status
- Announcements — platform news from the team
Store
Browse all available games and subscription plans. Each game card shows the minimum price and plan options. Select a game to see all tiers and durations. After purchase, your subscription enters pending status until an admin confirms it (usually within a few hours).
Subscriptions
A split-panel view of all your subscriptions. Filter by active, inactive, or all. Select a subscription to see:
- Expiry date and time remaining (progress bar)
- Plan name and game
- Inject button — triggers injection from the web panel (uses the web session)
- HWID reset request — if you need to switch machines
Status values:
| Status | Meaning |
|---|---|
active | Valid, injection allowed |
pending | Awaiting admin confirmation |
expired | Past expiry date |
cancelled | Cancelled by admin or user |
rejected | Purchase request denied |
Configs
Save and manage your in-game settings as named configs. Configs are per-game and versioned — each save increments the version number.
- Create a new config with a name and description
- Edit the config content in the built-in editor
- Publish a config to the marketplace to share it publicly
- Delete configs you no longer need
Configs are only available for games you have an active subscription for.
Marketplace
Browse configs shared by other members. Filter by game, sort by date or downloads. Download a config to use it as a base for your own. Configs can be rated and commented on by the community.
Community
A shared space for member activity and social features.
Status
Real-time health checks for the ZCORE API and per-game module status. Auto-refreshes every 30 seconds. Use this page to confirm whether an issue is on your end or a platform outage.
Profile
- Change your nickname, email, and password
- Upload an avatar and banner image
- Link your Discord account
- Set your birthday
- View session details (current device, token type)
- Request an HWID reset