search

Wiedmolol / CQMacroCreator

8 stars 11 forks source link

Invalid Kongregate Id #9

Open robgw84 opened 6 years ago

robgw84 commented 6 years ago

I just got a notice from the Automater that my Kongregate Authentication Ticket was incorrect, this was while it was already running rather than starting it up. It said "Its supposed to be 64 and its 64". When I went onto Kongregate to check it out it turns out that Kongregate was down and that apparently caused it.

Perhaps a way around this is to check the settings file to see if it was changed recently and if it hasn't been changed then the notice doesn't pop up as its determined that the Authentication Ticket hasn't been changed so its caused by something else. Then it just disables the program and it just checks every now and then until the Authentication Ticket is correct again before enabling it again. Rather than having the program crash or need to be shut down. Just a thought.

Wiedmolol commented 6 years ago

You are probably right about disabling the program and retrying to log in but the error hasn't really said your ticket was incorrect. It's just a message that pops out when log in fails, whatever the reason, and it's supposed to give you some info about your credentials cause in 99% cases they would be the reason why it failed.

Also, quite weird that kong being down makes it impossible to log in cause my apps never, ever send requests to kong. All is handled by PlayFab or by CQ website.

robgw84 commented 6 years ago

I cant remember exactly what it said, I tried to check it while I was typing that but by then Kongregate had come back up.

And I didnt mean it shouldnt give you any information at all, I just meant that it shouldnt crash the program or make you close it and should instead just wait until its able to connect again. Basically your credentials with kongregate shouldnt ever change, so any change to them in regards to the program should be done in the settings file, so if the settings file hasnt been changed recently then the program should determine that its an issue with kongregate like it was this time rather than saying your credentials are wrong, as saying that could lead to someone changing them and causing other issues, which I almost did if I hadnt found out Kongregate was down first.

Not sure if I am explaining very well, just thinking that it shouldnt say its wrong if it hasnt been changed.