05-29-2023, 06:45 PM
I'm trying to fully automate ClashFarmer so I can leave it running 24x7 unattended in a virtual machine, but the only automations possible currently are extremely wasteful and overall are quite poor..
The only automation possible currently is using the break schedules in the "Other" tab and using Windows Task Scheduler to start the ClashFarmer.exe on boot, so you can leave it running in a VM. This does work, but has a number of disadvantages:
I need one of the following things to achieve full automation:
Does anyone have any better ideas? For a project born entirely out of a desire to automate something, it's automation ability is surprisingly lacking...
The only automation possible currently is using the break schedules in the "Other" tab and using Windows Task Scheduler to start the ClashFarmer.exe on boot, so you can leave it running in a VM. This does work, but has a number of disadvantages:
- My army takes ~50 minutes to train, so after a couple of attacks CF is mostly useless and just idling which increases my screen on time needlessly and probably increases my risk of a CoC ban
- If I set the break schedule to always active, the auto-start bot to 'On' and use the Windows Task Scheduler to start/stop ClashFarmer.exe at the frequency I choose, I lose the attack log when the process quits as it isn't saved anywhere
- Telegram doesn't support bot-to-bot communications so the remote control feature can't be used to automate control of ClashFarmer
- You are stuck with the break schedules you set, they can't incorporate any randomness and you'll need to change these manually
I need one of the following things to achieve full automation:
- Log the attack log to an outfile such as C:\Program Files (x86)\ClashFarmer\attacklog.log (I can then pick it up with a script to parse/save and no longer have any issues with launching/killing the CF process via a script)
- Implement command line switches for ClashFarmer.exe (e.g. /startbot or /stopbot) - This would let me script incredibly granular and random play times to maximise attacks and minimise active time to avoid bot detection
- Implement more granular controls of the schedules, for example half hourly increments or entirely custom
Does anyone have any better ideas? For a project born entirely out of a desire to automate something, it's automation ability is surprisingly lacking...