Break connect()/reconnect() attempts after deletion (and more).

[pvzin]

As Imba suggested, I'm bringing this idea for you guys.

- First Suggestion:
Even though we get the very known printerror() message (Incorrect account or password provided to connect/reconnect function.) after a deletion, the bot continues trying to log back into the game.
This will eventually lead to an IP block if we don't notice what happened and close the bot.
Because of that, I suggest connect() and reconnect() should stop working (or be breakable) whenever a char gets deleted (or its acc/psw info changes).
We could even get a new printerror() message following the previous one, something like: Connect/Reconnect function was stopped because the provided account or password info is incorrect.

- Second Suggestion:
Basically, a new function that will make it able to read printerror() messages, or just make printerror() readable somehow.
If we had this, we could've already made the first suggestion work. However, I think it could be used for other matters too

Well, that's it.
Hope to hear from you guys about it.
Thanks.

[pvzin]

bump!

[Lucas Terra]

Thanks for reporting. Will fix that.

[pvzin]

Thanks for reporting. Will fix that.

What about the suggestion, Lucas?
Is it doable?

And thanks!

[pvzin]

I've edited the OP and brought some new info.
BUMP!

[pvzin]

bump!

[pvzin]

bump!

[pvzin]

bump!

[pvzin]

bump!

[pvzin]

bump!