I'm curious as to why this happens when I try to get the bot to login to my account by starting the script and choosing the account.

It then freezes and I cannot click anything at all and have to end the task. Any help would be appreciated.

Edited October 18, 201312 yr by kief

You have not explained your problem I believe?

 

That or I'm missing something.

That's a fragment of a sentence, what happens when you choose the account?

Edit: Broken script problem, are you sure your account is logged in when you're starting the script?

Edited October 18, 201312 yr by ScorpioZ

Sorry about that, I edited it. I tried copy and pasting the error message and started the post expecting to be able to paste it, but then had to get gyazo.

This is due to the Player being null when the client checks if you are under attack. Disable the break manager and re-enable it once you are logged in. Or just log in manually and it will stop.

(h.class is the break manager)

This has been going on for the past 1-2 months and still sin't fixed.

I posted this awhile ago on a different thread with the same problem (which cortana locked because it was "fixed")

Edited October 18, 201312 yr by dreamliner

That's a fragment of a sentence, what happens when you choose the account?

Edit: Broken script problem, are you sure your account is logged in when you're starting the script?

It's not a broken script problem - it's maxi's break taker.

Huh, I agree with dreamLiner, Are you logged in while starting the script ? 

Yeah I got it working by just logging in the restarting it but I figured it should work without being logged in also.

Yeah I got it working by just logging in the restarting it but I figured it should work without being logged in also.

It should but it doesn't. And one of the mods is going to close this because the problem is "solved" when it really isn't. We need Maxi to fix his break taker. All he has to do is check if the player isn't null lel

 

Yeah I got it working by just logging in the restarting it but I figured it should work without being logged in also.

It should but it doesn't. And one of the mods is going to close this because the problem is "solved" when it really isn't. We need Maxi to fix his break taker. All he has to do is check if the player isn't null lel

 

It is pretty much solved, we know the cause and we know how to fix it :P

 

also, OSBot keeps track of the gamestate, because when you're at the login screen your player isn't null but it might still crash, so maxi would need to check the gamestate and not for the player.

Yeah I got it working by just logging in the restarting it but I figured it should work without being logged in also.

It should but it doesn't. And one of the mods is going to close this because the problem is "solved" when it really isn't. We need Maxi to fix his break taker. All he has to do is check if the player isn't null lel

It is pretty much solved, we know the cause and we know how to fix it

 

also, OSBot keeps track of the gamestate, because when you're at the login screen your player isn't null but it might still crash, so maxi would need to check the gamestate and not for the player.

We know how to temporarily fix the problem. We know where the problem lies, and until it's fixed in the main OSBot break taker, then the problem is not solved.

line 174: !a.myPlayer().isUnderattack()

If you have never logged into the client, myPlayer returns null. This has nothing to do with gamestate. It's common sense to check for nulls before you evaluate something that could be null.