have you uninstalled everything and reinstalled. it was doing this to me and i just had to reset client and jagex launcher

I ran this across 20 instances so the time is x20.  How is anyone meant to test the script properly with multiple accounts in 6 hours?  I will run it again in a few hours and get screenshots for you.

I need to force stop the login solver  programmatically because i want to handle membership and bans on my end without having to physically be here to change the script or load a new account. The problem is when I get the high severity response for a ban or it needs membership the script goes straight to onExit() while the login solver is still running. This makes it so all schedules stop (cant just put it on repeat) and i cannot execute a reload.  What I am currently doing is once the response is detected i change a boolean in my custom login that tells shouldExecute() to return it to false. Then in the in the onExit function i tell the database this account was banned or this account needs membership and i reload the script. The login solver is getting the message to return false in the shouldExecute() but it is just calling shouldExecute() over and over again until the onExit() finished the script. Therefor, I cannot reload any scripts because i will just get the error "Stop your current script before trying to start another."  

Since yesterday I have not been able to log in on any Jagex accounts, I have patched into runelite client and still nothing.  I have confirmed these accounts work on other clients and mobile client. I am unable to use my purchase. imgur link with additional photos: https://imgur.com/a/hSnssed

Nomor 08159650666 adalah saluran WhatsApp resmi dari DBS Indonesia yang berfungsi sebagai pusat layanan pelanggan atau customer service.https://www.dbs.id