And thats exactly why we did it.. We had way to many key requests to be handled so people had to wait.. So we quickly published our new auth system. Its still fine to use the old one as long as it is available and people are willing to wait for keys. Though i think we will stop supporting the old system when the new system is usable enoughThanks for your reply and yes just waiting for key <3
By the way nice tool very cute indeed
oh nvm... it just started working. I think the 'save credentials' option is buggyDo you have Screenshot? if its Login error it could possibly be IP Block in which you need to wait for like 8 hours to purge it. So if that the reason you need to wait?
So a Screenshot might help to understand what is the issue you are facing.
If the save credentials option loads unreadable scrap at startup then... it will crash when you try to login with that ^^ So yeah.. its experimental.. The whole thing is still experimental.oh nvm... it just started working. I think the 'save credentials' option is buggy
Literally every error unless specified otherwise triggers that message. There is no difference between IP Block or wrong credentials or random server error. Though i thought @Asphyxia made it print a special message when the IP is blocked but maybe not. I dont have access to the backend code right now.if its login error as per SS same like me its IP BLock not login <credentials error> for SURE.
Yeah sure.. But who wants to do that? with TOK it was important to have a one file package. Sure.. could find a workaround.. but... The redistributables are needed by many applications anywayactually you can include both dlls into the same package and make a sfx, make sure you include 32 bit only and there you go