@nicolettenaya, to give you a bit more rationale into why this isn’t feasible:
- When the Tulip Player client is closed (Xed out, power outage, etc.), it can’t do anything and we can’t rely on it being Xed out because a power outage would also count as a Player being closed.
- On the server side, we notice that it has disconnected but we don’t know why it has disconnected it can be one of many things, like an Internet outage, etc). Then, we save that logic for when the operator logs in again.
However, this is something that we can look to eventually tackle as a separate suggestion. I know this doesn’t solve your problem but I hope it lends some insight into why this happens.