-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Message/alert not sent when process dies #11
Comments
Just to make sure: by alert you mean the Telegram message, correct? I can also safely assume that your Telegram settings are properly configured and sending the test message works when pressing the button? |
@tzerk sorry for late reply. You are correct, I can send a test telegram message fine. It also sends fine when I'm actually disconnecting with the game still running. But if the game just closes, no notification. |
@Zumochi Ok, I see the problem. It is more or less the expected behaviour, as the message is only send if BDO is running, but not connected. I could implement some sort of flag that is set once the observed client was running and online once so it will also message if the process completely shut down. I will see what or rather when I can implement it. |
@Zumochi Check out version 0.1.9, which hopefully adds the requested functionality. I don't know how often this problem (ie, the client dies) occurs for you, but I would appreciate feedback if the new version is working for you (or not). |
Hi, I'm afraid it doesn't seem to work that well yet. When I manually kill the process (sometimes when I try to reopen the game from tray I get audio, mouse and a completely black screen, only fix seems to be is to kill the game), it just says "Status: not running" but doesn't increase the failed checks counter. |
The application detects fine if the process is running or not, but it doesn't alert when the game dies after it has been running & connected before.
This should probably be fixed.
A notification doesn't have to be sent when it is first detected the game isn't running, but it should be when it closes after it has been up before.
The text was updated successfully, but these errors were encountered: