Can't log out other connection

[PatrickDattilio]

I think this is due to the login cleanup #61

[marshall-davis]

I think it existed before that and was something I missed. Are you sure it worked before and do you know how to replicate that message reliably?

It may have to with the clean up because we send that extra parameter now. I can do some checking to if the response is not normal and drop out of the automated stuff. There was another case in which this would prevent input when needed too, I thought I put in an issue but apparently not.

[PatrickDattilio]

To reliable get that message, login to the lobby, kill the client, run the client quickly and log in again.

I think we need to check for this prior to the self.send("Nope") otherwise it considers it the n

Do we know what Zealotry sends ("Nope" ?) This might be an easy way for them to blacklist the client...

[marshall-davis]

When I mentioned the "extra parameter" the "Nope" was exactly what I was talking about. Your suggested fix and mine are the same.

I am not worried about what string we send. If they choose to block a client based on that it will cause more trouble for them than it's worth, I believe. That being said, I will dig a little deeper into the Zealotry code and try and find out exactly what it does.