Blake13 Posted July 14, 2017 Posted July 14, 2017 Is there any way to disable the Auto login solver in my script?
IDontEB Posted July 14, 2017 Posted July 14, 2017 open the client with CLI and use the -norandoms parameter
Blake13 Posted July 14, 2017 Author Posted July 14, 2017 1 minute ago, IDontEvenBot said: open the client with CLI and use the -norandoms parameter Is there a way to make the script disable it? Kinda a pain to use CLI just for a specific script
Charlotte Posted July 14, 2017 Posted July 14, 2017 -allow norandoms on cli Use a custom login handler.
Blake13 Posted July 14, 2017 Author Posted July 14, 2017 3 minutes ago, Charlotte said: -allow norandoms on cli Use a custom login handler. Wouldnt I need to override the current login handler? What class would I need to override for that?
Eagle Scripts Posted July 14, 2017 Posted July 14, 2017 (edited) If I'm not mistaking Alek is either working on, or added a new method in which you can disable any specific OSBot RandomEvent. Have a look on his recent posts.| Edit: nvm, is only for break disabling You'll have to use the cli parameter norandoms instead, like the other users above me already stated though Edited July 14, 2017 by Eagle Scripts
Google Posted July 14, 2017 Posted July 14, 2017 Hmm use the default profile instead of entering your account's username and password when adding a bot?
Blake13 Posted July 14, 2017 Author Posted July 14, 2017 6 minutes ago, PulseImpulse said: Hmm use the default profile instead of entering your account's username and password when adding a bot? Scripts do not start if you use the default account not already logged in
Alek Posted July 14, 2017 Posted July 14, 2017 Im never giving Scripters the ability to handle usernames and passwords at an SDN capacity. You will need to use CLI norandoms and write all the bank pin and login code. It really isnt that difficult, Im sure there are snippets by now. 2
Blake13 Posted July 14, 2017 Author Posted July 14, 2017 4 hours ago, Alek said: Im never giving Scripters the ability to handle usernames and passwords at an SDN capacity. You will need to use CLI norandoms and write all the bank pin and login code. It really isnt that difficult, Im sure there are snippets by now. So if I wanted to make a ban checker it would never be released to the SDN? And I would need to use CLI with it every time I wanted to use that specific script?
Lemons Posted July 14, 2017 Posted July 14, 2017 9 minutes ago, Blake13 said: So if I wanted to make a ban checker it would never be released to the SDN? And I would need to use CLI with it every time I wanted to use that specific script? Yep, can always release the source tho 1
Alek Posted July 14, 2017 Posted July 14, 2017 37 minutes ago, Blake13 said: So if I wanted to make a ban checker it would never be released to the SDN? And I would need to use CLI with it every time I wanted to use that specific script? I bet if I took a poll and did not allow scripters to vote on it, 90% of the voters would vote NO to allowing scripters access to your usernames and passwords. 1
Mikasa Posted July 14, 2017 Posted July 14, 2017 7 minutes ago, Alek said: I bet if I took a poll and did not allow scripters to vote on it, 90% of the voters would vote NO to allowing scripters access to your usernames and passwords. We need to just use @5uck as an example of why it won't be allowed.
Alek Posted July 14, 2017 Posted July 14, 2017 Edit: Try bot.switchAccount(); It's an older method I wrote.
Blake13 Posted July 15, 2017 Author Posted July 15, 2017 14 minutes ago, Alek said: Edit: Try bot.switchAccount(); It's an older method I wrote. Scripts don't run until you log in so I would need a working account every time I want to run the ban checker. Also when trying to start a script on a locked account it will fail to log in and scripts will not run Here is a video I just recorded showing some problems im having