TABLE OF CONTENTS
Introduction
This article will help the user to troubleshoot Home Button issues of Play'n GO games. ContainerLauncher forces you to use the Engage API, so once you start using the ContainerLauncher in the Game Launch URL (GLU), the operator will need to listen and handle the Exit Handler Mode events. When players are leaving our games through some buttons, like for example, lobby or playforreal we perform an action depending on which exit handler is active. There are currently two modes: “redirect” and “events”.
- Redirect works just as it sounds. The browser will try to direct the user to another site depending on configurations like lobbyUrl, playForRealUrl, and reloadGameUrl.
- Events will not perform any redirects by themselves. Instead, the game will simply shut down (screen becomes black) and we will send events through Engage to communicate what you might want to do next. It is the operators' responsibility to listen to these events and trigger the intended functionality such as removing the game frame or perhaps starting the game in play for real.
Prerequisites
The user should have the information related to your PID number, Game ID (GID), and where to change Game Launch URL (GLU) in your environment.
Process
Using Container Launcher
1. To launch desktop games using ContainerLauncher please use the parameter &lobby=<redirection URL> in the Game Launch URL, and the URL should be encoded on your end.
2. Verify if the changes were reflected by reloading the game.
Troubleshooting
The Game Launch URL (GLU) is not working.
- Please ensure that you have the correct GLU fields.
If you still need help after following the steps in this article, please Contact Support via Chat
Other Reference Documents
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article