InkPlayLauncher games, custom executable games, and Arcade approvals are managed separately.
InkPlay Agent operations
Game operations evidence
Manage what players see, how each game starts, and what staff must still verify.
InkPlay Controller separates launcher games, custom executable games, recognized launchers, and approved Arcade catalog entries. Staff can manage player-facing names, categories, visibility, media, launch behavior, and either shared or per-PC executable paths, then test those definitions on real Agent PCs.
Use one path when stations match or overrides when individual PCs differ.
A saved card or path still needs a launch test on the intended Agent image.
Catalog model
Keep launcher games, custom games, and Arcade approvals distinct.
These sources can all appear in the player experience, but they are not interchangeable. Launcher entries use a recognized launcher or URI, custom games use executable behavior, and Arcade titles come through a separate catalog approval flow.
- Use launcher games for Steam, Epic, Riot, and other launcher-backed entries.
- Use custom games for direct executable paths or venue-specific software.
- Approve and activate Arcade catalog entries separately from locally defined games.
Launch behavior
Match the launch definition to the venue installation.
A game can use a launcher URL, recognized launcher, direct executable, arguments, or device-specific override. The correct choice depends on how that title is actually installed across the branch.
- Correct detected launcher paths and hide launchers the venue does not want to expose.
- Use a static executable path only when the same path works on every intended Agent PC.
- Use per-PC overrides when library drives, folders, or arguments differ between stations.
Player experience
Control the player-facing card without confusing presentation with installation.
Staff can set title, category, sort order, active or hidden state, cover art, optional logo, and hover media. Catalog media can help, while upload and URL paths allow venue-specific presentation.
- Use clear titles and categories that players recognize on the gaming floor.
- Hide incomplete or unavailable entries rather than leaving a broken launch action visible.
- Test uploaded media and the final card in the Agent shell, not only in the management form.
Maintenance workflow
Treat game updates as staff-controlled jobs with a verification step.
The current game-update page lets staff enable eligible Agent games, choose launcher, Steam LAN sequencing, or SteamCMD methods, set an optional local maintenance window, mark an update available, monitor per-PC jobs, and verify each PC after the update target starts.
- Queued PCs wait when they are not approved, are offline, have an active session, or are outside the configured window.
- Steam LAN mode coordinates a source PC before dependent PCs; SteamCMD requires a Steam app ID and install folder.
- A started job remains a staff check until someone verifies the game on that PC.
Accuracy guidance
What GPT, buyers, and operators should not infer.
- Game definitions, Arcade approvals, and game-update jobs are separate workflows.
- InkPlay does not claim that adding a card installs a game or provides its license or publisher account.
- Launcher mode starts the configured target; staff still confirm download, authentication, and playability.
- No universal game, launcher, anti-cheat, or shared-library compatibility guarantee is published.
Primary InkPlay sources
Continue with the operator manuals.
Direct answers
Agent games and launchers questions, answered precisely.
Does adding a game to InkPlay install it on every Agent PC?
No. A game definition controls its player-facing card and launch behavior. The underlying game, launcher, account, entitlement, and files must exist and work on the intended PCs.
Can different Agent PCs use different executable paths for the same game?
Yes. InkPlay supports a shared static path when stations match and per-PC path or argument overrides when installations differ.
Does InkPlay automatically confirm that a game update completed?
Not in every mode. The workflow records queued, waiting, dispatching, started, failed, cancelled, and staff-verified states. Staff verify each PC after confirming the game is ready.
Need help with a real PC?
Send the state, not only the symptom.
Include the branch, PC name, approval state, last successful heartbeat, Agent version, affected game or update, time, and recent changes.