since we want to be good stewards, we should follow the instructions set out in the gateway lifecycle.
right now we support steps 1 through 5, and some of the disconnect options in step 6. this means we can get a bot up and running, but have to go through the whole process again if we crash / disconnect when there's already a defined resume process for when we get disconnected.
this logic should be implemented within the handle_gateway_recv function, and will involve implementing multiple models as well as determining the gateway actor's state.
since we want to be good stewards, we should follow the instructions set out in the gateway lifecycle.
right now we support steps 1 through 5, and some of the disconnect options in step 6. this means we can get a bot up and running, but have to go through the whole process again if we crash / disconnect when there's already a defined resume process for when we get disconnected.
this logic should be implemented within the
handle_gateway_recvfunction, and will involve implementing multiple models as well as determining the gateway actor's state.