Retry & Monitor Delays

We suggest to use Rons CSV Editor, found at https://www.ronsplace.eu/Products/RonsEditor/Download to make these changes!

Retry Delay

The retry delay is the amount of time in milliseconds that the bot will wait until it retries to submit your information. Having this too low could result in another loop or decline and having it too high could result in the item going OOS. Retries are done on things such as card decline, failure when submitting, proxy ban, or similar!

Retry delays are more forgiving than monitor delays and you typically are able to put them lower than your monitor delay.

Please view our recent release channel for the delays that you should use. These delays are different depending on the site and release type. As these sites change, the delays that are allowed also change.

Monitor Delay

Having a good monitor delay is very vital. This could be the make or break in having success.

Monitor delay is the amount of time in milliseconds (ms) for the bot to wait until it should refresh the page to see if there is a new stock that has been loaded. The faster this is, the sooner you’ll know if there is an update to the site. Monitoring too fast could lead to a ban which makes your task useless (use proxies to avoid these bans).

Please view our recent release channel for the delays that you should use. These delays are different depending on the site and release type. As these sites change, the delays that are allowed also change.