From v3.0 forward. All automated actions are executed by a TaskSender. Once you log in with the bot. A TaskSender will be created for every farmlist on your account. One special sender will be created as well. This special sender is called the "Utility sender". This sender contains the CropChecker and AttackChecker. You can assign farmlists to different senders using the "Change sender" buttons. Then you can start these senders by checking the checkbox in the "Send" column. But first you need to enter its "From" and "To" times in the table. This is the delay inbetween waves in minutes These times specify how often the sender and its tasks will be executed. The actual delay is then set randomly in the specified from/to interval. You can also set a senders profile using the "Set profile" button. More on that in the Profiler section.
Another feature of the FarmSender is not sending farms that have had a loss on the raid or if the raid got defended by the enemy.
By default, when a farmlist gets sent, the bot will simply uncheck every farm with red/orange swords before sending it. You can disable and tweak this in the settings.
I recommend linking multiple farmlists to a sender to simulate a real user. The use of the profiler is also advised!
Profiler sets a farmlists profile. Depending on the hour of day the profile factor changes. The final delay calculated before is then divided with according factor. This changes frequency of the waves being sent making the bot less noticable and more natural.
The points in the graph specify the factor = 200% is a 2.0 factor. This means the final delay is going to be divided by 2 making the frequency of attacks 2 times faster. 100% makes no change. 50% makes the farmlist sender effectively twice slower. Making the delays inbetween attacks longer (during the night for example). This feature is fairly new and you should be careful with it. You can save profile into a file and load it up from file later.
The profiler minimum factor is "0.1". You can drag the slider lower and it will snap to "0". This factor will simply stop the sender entirely for the specified hour. This for example useful to simulate the player sleeping or similar.