my_connection_lost event

docs/_static/csv/bot.csv

@@ -3,4 +3,5 @@ on_my_connect	teamtalk.Server	Called when the bot has successfully connected to
 on_my_login	teamtalk.Server	Called when the bot has successfully logged in to the teamtalk.Server
 on_my_logout	teamtalk.Server	Called when the bot has successfully logged out from the teamtalk.Server
 on_my_disconnec	teamtalk.Server	Called when the bot has successfully disconnected from the teamtalk.Server
+on_my_connection_lost	teamtalk.instance	Called when the bot has lost connection to the teamtalk.Server
 on_my_kicked_from_channel	teamtalk.Channel	Called when the bot has been kicked from teamtalk.Channel

docs/whats-new.rst

@@ -20,6 +20,11 @@ This document holds a human-readable list of changes between releases.
 version: 1.3.0 - unreleased
 ---------------------------------
 
+Added
+~~~~~
+
+- Added the handling of the bot lost connection to the server event.
+
 Fixed
 ~~~~~
 

teamtalk/instance.py

@@ -852,6 +852,10 @@ async def _process_events(self) -> None:  # noqa: C901
             banned_user = TeamTalkBannedUserAccount(self, banned_user_struct)
             self.banned_users.append(banned_user)
             return
+        if event == sdk.ClientEvent.CLIENTEVENT_CON_LOST:
+            self.bot.dispatch("my_connection_lost", self)
+            return
+
         else:
             # if we haven't handled the event, log it
             # except if it's CLIENTEVENT_CMD_PROCESSING or CLIENTEVENT_CMD_ERROR or CLIENTEVENT_CMD_SUCCESS