y like when i update master and reclone i have no problems :( its prob it with 72VMs pulling the new nhc.exe one after other i can understand.Quote:
The reason it's simple but there is nothing great that can be done.
The problem of wipe the accounts.txt happen with "defected" nhc4.exe, when all your vms are downloading the file often 1 or other have problems with the download and this defected files open and clear the accounts.txt file that its one of the first "jobs".
So it's kinda of each update risky. However I notice if you go to accsused you know the last account that was pulled so you need then to put from that one ahead.
Maybe solution its change to a better webserver lol, in EU.
So i hope not too many updates are pushed the next days :D.
Implementing a database would also improve this issue very much but i know its a lot of work and prob not worth it.
So a sugestion: dont let the bot autoupdate let it check if it has the newest .exe from a shared folder. The bots get stuck anyway if you push an update and it would be less time fixing.
Another Sugestion: let the VM restart with shortcut to nhc4.exe in autostart folder (If there is a new update). Restart the machine at a random number between 1 and 120 Seconds or so :). That could work also. Or just delay the download with rendom time :) .
for now mby i try to programm a little thing that watches the accounts.txt every 30 seconds or so if it reaches filesize 0KB the last version is restored. Running outside of the vms on 1 PC