@TheLittleNaruto That word is already said in the latest 10 words. Please use another. (In case I'm mistaken, run >>rmword lol and then >>reply 6771515)
Nope, I'll scan the logs later. It might have received a close socket with status 1000 meaning the chatserver asked to gracefully close the socket. It is the only situation that I don't retry a connect.
message: {"r721":{"e":[{"event_type":4,"time_stamp":1521210087,"id":15487162,"user_id":261079,"target_user_id":261079,"user_name":"FOX 9000","room_id":721,"room_name":"Shadow\u0027s Den"},{"event_type":3,"time_stamp":1521210088,"id":15487163,"user_id":261079,"target_user_id":261079,"user_name":"FOX 9000","room_id":721,"room_name":"Shadow\u0027s Den"}],"t":15487163,"d":2}} ws close for 721 websocket close handling 1000
@PrincessLuna it looks like something triggered the leaving of account, as that are the events for @ProgramFOX leaving and re-joining, and next my bot receives the close socket event from the Stack Exchange chat server. And although the socket closed, kenny doesn't get logged out and happily continues posting the pre-programmed timer-based responses.
