Detecting if a CLI argument is enabled?

[Hayase]

Is there a way to detect if a CLI argument has been enabled such as "-allow norandoms" and if so, how?

Edited April 19, 2017 by Hayase

[Eagle Scripts]

Just now, Hayase said:

Is there a way to detect if a CLI argument has been enabled such as "-norandoms" and if so, how?

You can check if the value of getParameters() is not null / the length > 0 if I'm not mistaking

[The Undefeated]

4 minutes ago, Eagle Scripts said:

You can check if the value of getParameters() is not null / the length > 0 if I'm not mistaking

Can confirm that this works, just do a null check on getParameters().

 

[Alek]

He asked specifically for CLI arguments in general, which I don't think scripters can access. The only thing you can grab is script parameters from CLI. In general, all scripts should be fully usable without any specific OSBot settings enabled or disabled.

[Hayase]

16 minutes ago, The Undefeated said:

Can confirm that this works, just do a null check on getParameters().

 

Doesn't work for me, attempting, "-allow nointerface" just says "null" for me. I can't sort any arguments from "-allow"

log("Parameters set: " + getParameters());

 

8 minutes ago, Alek said:

He asked specifically for CLI arguments in general, which I don't think scripters can access. The only thing you can grab is script parameters from CLI. In general, all scripts should be fully usable without any specific OSBot settings enabled or disabled.

I was looking for was a way to hop worlds on the logout screen to run away from PKers and the only way to do it is by having norandoms turned off or else the auto login just brings you back in to die,

[Alek]

32 minutes ago, Hayase said:

Doesn't work for me, attempting, "-allow nointerface" just says "null" for me. I can't sort any arguments from "-allow"

log("Parameters set: " + getParameters());

 

I was looking for was a way to hop worlds on the logout screen to run away from PKers and the only way to do it is by having norandoms turned off or else the auto login just brings you back in to die,

Well if its not an SDN script you can just tell people to start OSBot with norandoms flag?

[Hayase]

13 minutes ago, Alek said:

Well if its not an SDN script you can just tell people to start OSBot with norandoms flag?

This is for a future SDN script but maybe if might not be a viable script after all

[Alek]

34 minutes ago, Hayase said:

This is for a future SDN script but maybe if might not be a viable script after all

You can't force users to enable certain settings, the botter is free to decide whatever they want.

[The Undefeated]

8 hours ago, Hayase said:

Doesn't work for me, attempting, "-allow nointerface" just says "null" for me. I can't sort any arguments from "-allow"

log("Parameters set: " + getParameters());

 

I was looking for was a way to hop worlds on the logout screen to run away from PKers and the only way to do it is by having norandoms turned off or else the auto login just brings you back in to die,

I didn't understand it correctly, my bad. You could also let the bot hop worlds but that takes more time. Don't forget you're required to use script parameters to get the login details and login when using -norandoms.