Seams like when I run 4 bots
East ladder
3 pals mfers 7-9 min games
1 Uber smiter that runs and also sits in game and waits 15 mins on keys to be delivered
They run fine for a hour or two
No chickens
Then after the hour or two
That’s when the failed to join games start
I have a lot of delays added
For crashes have a min delay
For failed to join I have a hour delay
Etc etc
I am using 1 key per bot
2 keys per mule
Any ideas what I can do to fix this issue?
It is like clock work
They run for a hour or two
Then not for like 3 hours
Then they work again for 1-2 hours
And so on
I use the trunk version
She I try one of the other versions ?
Did you try to increase the game time of those mfers?
You should increase the game time, cause you have 4 game creators.
There were a lot of topics on github\issues or you can search either the discord channels about time recommendations.
Since June 2017 when was added the possibility to have 8 chars from same IP in the same game, they also switched the tracking to IP+key+account.
The temporary restriction is applied to IP, but If you get a 12-24-48 h restriction, it isn’t enough to change only the IP, but all tracked things should be changed (IP + keys + accounts) during the restriction time, otherwise the restriction will be re-applied soon. Repeated attempts to avoid the temporary restrictions will finish with a 5-7 days restriction applied to accounts.
Just checking for clarity, as you replied to my topic to come here for the answer and I am a little confused.
Is the temporary restriction, when the game crashes and you keep getting Fail to join for about 10 minutes? Does that mean if you change the IP address you should be fine?
Although if you get a 12-24-48 restriction you have to change all three IP/Account/Key ( what does the 12-24-48 restriction look like?? I didn’t have any signs of a temporary restriction or a 12-24-48 one before I got hit with a 7 day waiting in line.)
How do you prevent the waiting in line as that was what my topic was about, not FTJ.
I have heard some people mention it is more lenient if you are joining games, rather than creating the games. ( this would be in reference to the Waiting in Line not FTJ)
It’s a kind of temporary restriction. Keep in mind that repeatedly leaving of the games before 2 minutes will bring issues, as a way to combat the Diablo clone hunting bots.
Someone says that this restriction is recorded on IP and if you want to have 1 minute avg runs, you need to do this on 2 IPs, and switch between them like in the past with cdkeys.
… but in time any exploit of a vulnerability can conduct to … a new patch.
Any waiting in line should be treated as a temporary restriction.
The simple solution is to avoid to be flagged, keeping the game time length at proper value according to how many separate solo bots (game creators) you have, and total number of bots/same IP
30 games/h involves either some restrictions to not repeatedly leave the games before 2 minutes - the fix to stop the DC hunters.
100 games/12h can be expressed as 100 games / 720 minutes, so the avg of game length ~ 7.2 min (432 sec)
for playing non-stop (24/7) you should not push the limits, because the limits aren’t 200/24h, 300/36h, a.s.o, for the same IP.
Notes 2:
In case of using followers you should add some delays for joining or leaving games, otherwise you can get issues.
In case of account restriction, the used keys (and IP) will be flagged. When you get this, you have to wait without any connection for 5-7 days (in case you cannot change easily the IP and you either don’t have other keys), or to change the IP and use other accounts & keysets. Using the keys that were run with first restricted accounts, this will restrict other accounts and it will flag that new IP, too. Or using an ok key for restricted account it will flag that key too, and also other accounts opened with that key will be restricted.