-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repetitive tasks (ex. farming) not working #15
Comments
Is it possible to implement repetitive tasks function? Also, how can I delete all or a group of tasks at once? Thanks |
I don't have any plans on adding new features.
There is no group. You need to remove them one by one. Currently there is no button to delete all tasks. |
merhaba iyi çalışmalar bende asker destek dönderme ve asker yetiştirmeler çalışmıyor.güncelleme yapabilirmisiniz. |
iyi günler sonra asker geliştirme ve sonra asker gönder çalışmıyor bi güncelleme yaparmısınız. |
Update the scripts, the issue is fixed: |
merhab kolay gelsin iyi günler hastane içinde sonradan yetiştir ve sonradan
iyileştir yapabilirmisiniz.çalışmalatınız çok güzel sizi tebrik
ediyorum.her köy için asker kaçır yapmak mümkün mü?
adipiciu ***@***.***>, 2 Oca 2023 Pzt, 10:28 tarihinde şunu
yazdı:
… Closed #15 <#15> as
completed.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AWVG73LGJMUBYWOPSXOB5MLWQJ7TJANCNFSM5LU2C4PA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi adipiciu!
I have installed the latest version of your TTQ script (1.9.2). I tried to setup the repetitive troop sending option (like, every minute) on a trial account without Gold Club. Script sends successfully the first attack, but does not repeat attack a minute later - the task is marked as completed and no longer active. I also checked this with the Gold Club on some older versions (1.7.3) back in the days, and the script also failed to perform repetitive tasks. Can you please suggest the solution?
The text was updated successfully, but these errors were encountered: