Do you guys pass a username/password?

On 3/7/2017 at 11:44 PM, Zach said:

Do you guys pass a username/password?

I pass a placeholder in. I use it with a custom login handler which will pull an acc from my database. My -bot tag is "-bot none:none:0000"

Edited March 9, 20179 yr by k9thebeast

7 hours ago, k9thebeast said:

I pass a placeholder in. I use it with a custom login handler which will pull an acc from my database. My -bot tag is "-bot none:none:0000"

I do this exact same thing.

On 3/9/2017 at 4:47 AM, k9thebeast said:

I pass a placeholder in. I use it with a custom login handler which will pull an acc from my database. My -bot tag is "-bot none:none:0000"

Ok, so that's the problem then. Without a unique name, the client cannot attach a random.dat file to the user. I don't believe there is a good way to fix this on our side. A possible fix on your side would be to pass an actual username.

12 minutes ago, Zach said:

Ok, so that's the problem then. Without a unique name, the client cannot attach a random.dat file to the user. I don't believe there is a good way to fix this on our side. A possible fix on your side would be to pass an actual username.

Thanks for the information - I'll be adjusting my system to make this work.

8 hours ago, Zach said:

Ok, so that's the problem then. Without a unique name, the client cannot attach a random.dat file to the user. I don't believe there is a good way to fix this on our side. A possible fix on your side would be to pass an actual username.

Thanks!

On 3/11/2017 at 10:46 PM, k9thebeast said:

Thanks!

Wanting to follow up on this. Can you confirm that it works for you with unique names being passed?

3 minutes ago, Zach said:

Wanting to follow up on this. Can you confirm that it works for you with unique names being passed?

Can confirm I've had no issues since passing CLI the real account information, thanks for the help!

Thanks for the response!

how do you fix this? by simply putting real acc info in the CLI line such as -bot RealAcc:RealPass:0123

ive been getting logged out of my scripts randomly (midway through any of my methods) after i implemented account grabbing from a file.

i have norandoms on and i use explvs handler like so im my script:

        if (!getClient().isLoggedIn() && getClient().getLoginUIState() != 4
                && hopping == false)
            return State.LOGIN;

even though the client has logged out (and isnt banned (loginstate 4)) it doesnt break my method, making login handler kick in.

it will be logged out and stuck in the random method making it not log in.

i never experianced this before grabbing acc info. I use proxys @ around 2/3 clients per ip

any help solving this is much appreciated

On 3/23/2017 at 7:30 PM, Lewis said:

how do you fix this? by simply putting real acc info in the CLI line such as -bot RealAcc:RealPass:0123

ive been getting logged out of my scripts randomly (midway through any of my methods) after i implemented account grabbing from a file.

i have norandoms on and i use explvs handler like so im my script:

        if (!getClient().isLoggedIn() && getClient().getLoginUIState() != 4
                && hopping == false)
            return State.LOGIN;

even though the client has logged out (and isnt banned (loginstate 4)) it doesnt break my method, making login handler kick in.

it will be logged out and stuck in the random method making it not log in.

i never experianced this before grabbing acc info. I use proxys @ around 2/3 clients per ip

any help solving this is much appreciated

I dont believe 

getClient().getLoginUIState() != 4

corresponds to ban. I think you need to use the onResponseCodeListener()

 

Try adding a log after your getState() method or whatever you are using to determine which state it gets stuck in.