Use the shared game library
Use a branch-shared game library path when the venue wants Agent PCs to launch games from a controlled shared location.
The branch can manage shared game launch entries consistently while keeping paths safe and understandable.
Before you start
- Confirm the venue has a shared library location that Agent PCs can reach.
- Set up Agent PCs and game cards first.
- Use owner/admin access for shared library configuration.
Decide when shared library helps
A shared library is useful when many PCs use the same game files or launch structure. It is not required for every branch.
- Use shared paths when games are centrally managed.
- Keep local-only games configured separately if needed.
- Avoid shared paths that normal Agent PCs cannot reach.
Keep paths safe
Shared library paths should stay inside the intended game library. Staff should not use this feature to browse arbitrary network locations.
- Use a clear root library location.
- Use relative executable paths for individual games where the UI expects them.
- Reject paths that point outside the approved library.
Test shared launches
Test on real Agent PCs before relying on shared launch entries for customers.
- Launch a shared-library game from at least one test PC.
- Confirm the same entry works from another PC in the same group.
- Document games that need local installation instead.
Verify it worked
- The shared library root is reachable from the intended Agent PCs.
- At least one shared-library game launches on a real Agent PC.
- Staff know which games are shared and which are local-only.
Troubleshooting
Shared game launches on one PC but not another.
Check network access, mapped path expectations, and whether both PCs can reach the same library location.
The path points outside the game library.
Correct the library root and executable path before publishing the game card.