Quote:
Originally Posted by logpw
Can somebody help and tell what im doing wrong?
My vms are pulling the same account on logging screens from shared folder accounts.txt
|
It took me a long time to figure out the shared accounts folder. I have had it running a few weeks now, but it's a real pain to get working. If they are pulling the same account, check all the "accused.txt" lines in your configs and at the bottom of your configs make sure you have the correct stuff in there as well (the config on the vm not the shared one). The bottom of your shared config should look something like this. Your paths will be different of course.
;Set single accs file for all bots in shared folder example = "Z:\BOTS\accounts.txt"
accsall="Z:\Share1\Shared\accounts.txt"
;Set log file in shared folder with all accounts that were used already = "Z:\BOTS\accsused.txt"
accsused="Z:\Share1\Shared\accused.txt"
;Minimize Game during some periodos to decrease the CPU/GPU load only for 3v3 Dominion, 1 to enable.
minigame=1
;Set the period when using the Minimize Game in seconds, 100 its the default, after 15 minutes of game it changes automatic to fixed 30sec.
minigamedelay=100
;When account is finished takes screenshot and saves on configured folder of the acc name/lvl ie: "Z:\BOTS\PICS\", 0 to disable.
screenfolder=0
accmode=2
roompath="Z:\Share1\Shared\rooms.ini"
roomplayers=10
randomwin=0
staticroom=1
As far as I know the way the shared accounts works is like this: It pulls an account from your shared account folder and puts it in the local VMs "account" folder. It then puts that account in the "accsused.txt" folder so the other bots won't try and take it. Any account in the "accsused.txt" shared folder will not be pulled by any other bot. However, this messes up sometimes and the bot will give you the error message like it's ran out of accounts. Usually when it does this, I delete the account off the local VM's "account.txt" file and off the shared "accsused.txt" and put it back on the shared "accounts.txt" folder. I then save an empty accounts folder on the VM and open the config file of that VM. If you change the line "pullacc=1" to "pullacc=0" and start the bot it will automatically pull the next account on the shared accounts file that is not in the accused file. The bot will automatically change the "pullacc=0" back to "pullacc=1" on its own in the config file.
----------------------------------------------------
On a Different Note, NHC:
Is there a way to delay the botmaster from capturing points in the config file? I want to lengthen the game time because I am having problems on high stress machines with the bot trying to capture points as soon as it logs in but not able to because the game has not started yet. It actually fails at catching all points because of this and causes issues.
Thanks