-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Add specific cooldown for each bot account #106
Comments
Idea: Could also be done with a queue. globalcommentcooldown will need to be reworked anyway to allow being applied to certain accounts and not the whole bot. |
Soo I'm finally addressing this, sorry for the long wait. What I think I'm going to do:
I'm not 100% sure yet how this is affected by This should be the best solution I think |
On second thought I don't think it is going to help much and will just make everything more complicated. So what I still might be doing is to make a database where each bot account gets a cooldown directly after commenting for three reasons:
However this means we have to rethink how the botaccountcooldown is used as it will make the running session wait for each account to become available again when re-shuffling. Is this really worth it? Seems like a lot of work for not so much benefits. |
If I start more sessions with randomizeAccounts true or just false but I start when same sessions are at bot 0/1/2/3 ( very small delay between them) the accounts get cooldowns that result fails so it would be a fix to add a cooldown on each account after comment sent / failed so that account cannot be used again until that /account cooldown isnt done.
Edit: if the 1st session is started and bot 1 commented, the 2nd session its started same time with bot 1 so bot 1 have a cooldown so set session 2
advancedconfig.json
account delay is setted to 10 seconds for example, the 2nd session is paused foradvancedconfig.json
session cooldown 30 seconds for example and after that 30 seconds session will start again.The text was updated successfully, but these errors were encountered: