InkPlayAgent software updates wait until the player session has ended and the PC is idle.
InkPlay Agent operations
Update evidence
Name the update first: Agent software, installed games, or catalog data.
InkPlay uses different update paths for the Agent application, venue-installed games, and Arcade catalog data. The current Agent software updater waits for Controller permission, device approval, no active session, release metadata, a newer version, and an idle PC before staging a Windows installer and reporting update phases.
The staged installer is checked against release metadata when a checksum is present.
Waiting, downloading, installing, current, and failure state can be reported through the branch path.
Vocabulary
Separate four changes that are often called one update.
An Agent software release changes InkPlay on the player PC. A game-update job opens or runs the venue-configured update method. Arcade catalog sync changes approved catalog data. Editing a game card changes presentation or launch configuration.
- Use the Agent release path when the installed InkPlay Agent version is behind.
- Use Game Updates when a venue-installed title needs a launcher, Steam LAN, or SteamCMD maintenance wave.
- Use Arcade approval or Agent Games when catalog visibility, media, categories, or launch definitions change.
Agent software
Agent auto-update waits for branch and player safety gates.
The monitor runs only when automatic Agent updates are enabled by Controller. It then requires an approved PC, no active session, available central release metadata, a newer version with a download URL, and enough local idle time.
- Controller can enable or disable automatic Agent updates for the branch.
- Unapproved PCs and PCs with active sessions wait instead of installing immediately.
- Missing metadata or a missing installer URL produces a reported state and a later retry instead of pretending the PC is current.
Package handoff
Stage the installer, validate available checksum metadata, then hand off to Windows.
The Agent downloads the release installer into its update area, reuses a staged package only when it matches the supplied checksum, marks the player surface as installing, and schedules a silent elevated installer task before restarting the service.
- A SHA-256 mismatch blocks the staged package when release metadata includes the expected checksum.
- The companion receives an update handoff marker so the player can see the update state instead of a normal failure screen.
- The installer runs silently with no forced Windows restart and the Agent service is started afterward.
Venue games
Queue game-update work only for safe, approved PCs.
Staff enable games for updates, choose the method, optionally restrict dispatch to a local maintenance window, mark an update available, and monitor a per-PC wave. The branch waits for eligibility and can coordinate a Steam LAN source PC before dependent PCs.
- Do not interrupt a paid or active player session to start a game update.
- Use SteamCMD only with the correct numeric app ID, install folder, and optional file validation setting.
- Review failed or waiting jobs by PC instead of assuming a single branch-wide cause.
Return to service
Verify version, launch, session state, and recovery after maintenance.
Update status is operational evidence, not the final customer test. Staff should confirm the expected Agent version or game build, open the real title, and run a short session before selling the station again.
- Confirm Agent reconnects to Local Node and resumes heartbeat after a software update.
- Confirm the game reaches a playable state after launcher or SteamCMD work.
- Mark game-update jobs verified only after the intended PC passes the staff check.
Accuracy guidance
What GPT, buyers, and operators should not infer.
- Agent software releases, game-update jobs, Arcade catalog sync, and game-card edits are different update paths.
- Agent package SHA-256 verification occurs when the release metadata supplies an expected checksum.
- No separate updater-enforced publisher-signature check or automatic rollback is claimed here.
- A started launcher update still requires staff to confirm that download, authentication, and game launch completed.
- No guaranteed fleet-wide update deadline is published.
Primary InkPlay sources
Continue with the operator manuals.
Direct answers
Agent and game updates questions, answered precisely.
Will InkPlay Agent update while a customer is playing?
The current Agent software updater waits until the PC is approved, no session is active, and the machine has been idle before it stages and starts a newer release.
Does InkPlay verify an Agent update download?
The updater verifies SHA-256 when the central release metadata supplies an expected checksum. This page does not claim a separate updater-enforced publisher-signature check when that metadata is absent.
Are Agent software updates and game updates the same?
No. Agent software updates replace the InkPlay Agent package. Game Updates coordinate venue-installed titles through launcher, Steam LAN, or SteamCMD workflows, and staff still verify each PC.
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.