Hibbett Restock Guide

Before setting up for Hibbett restocks, please familiarize your self with general task creation which can be found here.

Setting Up For Hibbett Restocks:

The fastest and most efficient way to run for Hibbett restocks is by using SKU and cloud mode. Variants will be provided via share links for certain shoes in the Discord channel titled "run-for-restocks" which will be updated periodically.
Hibbett restocks occur in 30 minute intervals. Knowing the exact time they will restock is not possible so it is best to check monitors to see at what interval the product you are trying to go for is restocking.
In order to run restocks with variants, it is highly recommended to use the "Cloud" feature to maximize the product you can run. You will want to start tasks 5-7 minutes before the expected restock as payment tokens expire and thus do not allow tasks to be ran 24/7.

If cloud mode I selected, tasks will utilize cloud monitoring. Instead of showing a timer, tasks will say "Waiting for Restock" and are waiting for the cloud monitor to ping and tell tasks to spam payment.

Note: tasks must be started before the cloud ping goes off.

Why am I getting retrying payment?

Retrying payment means that the product is out of stock and that the task is trying to submit the payment again in hopes that the product comes back in stock.

Should I use residential or datacenter proxies?

What delays should I run for restocks?

Speed plays a big factor in Hibbett restocks. For best chances on restocks, it is best to drop task delay to about 1000 right before the restock. Monitor delay does not matter if you are running with drop time. Note: DO NOT run 24/7, only run it for a short period of time during a potential restock.

How long should I let my tasks run before stopping?

Do I need to use the "Restock" mode?

Restock mode is slightly faster than cloud mode, but the restock mode usually reamins locked. It is best to use cloud mode unless otherwise made note in Discord.

Last updated 8 months ago