1. A description of the suggestion:

Change the 'Default' bot account to no randoms client.

2. How will this suggestion impact scripters and/or botters?

Would give scripters a easy way test a script with norandoms enabled without having to restart a client over and over everytime they change code.

Would in general be a easy way to get a no randoms client, and since default has no access to login anyway I don't see a downside. (I have only used default a couple of times throughout my time on osbot and that was mainly just to have a proxied client, so unless I am missing a common use for it it shouldn't have a negative effect on anyone.)

3. Post any examples such as code or pictures to supplement your description (optional)

Edited August 29, 20178 yr by GPSwap

Default account is intended for new users to botting (or to the client) who do not want to enter their game username/password into the client. Although with a default account AutoLogin and BankPin doesn't work, I left it enabled. This will show the user why we need that information and encourages users to set up an actual profile.

Just now, Alek said:

Default account is intended for new users to botting (or to the client) who do not want to enter their game username/password into the client. Although with a default account AutoLogin and BankPin doesn't work, I left it enabled. This will show the user why we need that information and encourages users to set up an actual profile.

ahh okay thats fair enough, maybe another defaultly set account for no randoms? or do I just have to suck it up and repeatedly launch with cli

2 minutes ago, GPSwap said:

ahh okay thats fair enough, maybe another defaultly set account for no randoms? or do I just have to suck it up and repeatedly launch with cli

Good follow up, mind me asking why you would need a "default" account and not a regular account with norandoms? Right now you can only have one "Default Account", it sounds as if you are using multiple?

4 hours ago, Alek said:

Good follow up, mind me asking why you would need a "default" account and not a regular account with norandoms? Right now you can only have one "Default Account", it sounds as if you are using multiple?

edit: just read jamies reply below its much more coherent

its not that ,I'm trying to test a script and I keep having to restart client to start it with cli to have it set to no randoms to run updated script and test if the fix worked, (unless im being a moron and there is a way to open client with norandoms without cli) and to me since the default account cant use login anyway it just seemed like a convienient place to put a way to open the client as no random, in my response I meant having another account thats always in the account list(the way the "Default" account is) that would just be "no Randoms" and if that account was selected it would boot the client in no randoms, so to check a update on a script you would just need to end script then start again like normal

 

Edited August 29, 20178 yr by GPSwap

14 minutes ago, Alek said:

Good follow up, mind me asking why you would need a "default" account and not a regular account with norandoms? Right now you can only have one "Default Account", it sounds as if you are using multiple?

I'm just assuming here but currently the only way to allow norandoms is to load via CLI. If I use my own account grabbing / setting method within a script I can't load osbot normally and run, I have to load via CLI which is a pain for testing.