HIBBETT

INFORMATION

Running Hibbett restocks is actually the preferred way to bot Hibbett. As this site drastically increases their anti-bot systems before and during a drop, botting it relies heavily on your bots PX solution. Some bots are not able to effectively bot Hibbett initial and some are but HEAVILY depend on the botters proxies. Overall botting Hibbett's initial drops is a bit of a shit show.

When it comes to Hibbett they will restock a-lot of stock over a long period of time at set restock times which we will discuss later. Below is how you should setup for Hibbett restocks as well as some tips.

RESTOCK TIMES

⏰ xx:17 + xx:47

xx:17 and xx:47 mean the 17th and 47th minute of EVERY hour after the initial drop. Sometimes they don't restock on one time or the other, its a random pick between the 17th minute and 47th minute however as they are so far apart you can easily run for both. Although Hibbett have started their restocks as early as the following hour after an initial drop. Most restocks will start at 10:17am the day after the drop and then at every hour through out the day.

SETUP

Keywords

For your monitor input you will want to use the products variants which will be provided in the release channel or via your bots guide. The formatting of this is dependent on your bot but in most cases its similar to the example below.

Item X

5.0 - 38326344 5.5 - 38326351 6.0 - 38326369 6.5 - 38326377 7.0 - 38326385 7.5 - 38326393 8.0 - 38326401 8.5 - 38326419 9.0 - 38326427 9.5 - 38326435 10.0 - 38645727 10.5 - 38326443 11.0 - 38326450 11.5 - 38326468 12.0 - 38326476

Monitor Input For Item X:

38326344
38326351
38326369
38326377
38326385
38326393
38326401
38326419
38326427
38326443
38326450
38326468
38326476

Delays

Delays are somewhat insignificant with the way Hibbett restocks work however we suggest a delay of around 1000-3333ms monitor and retry/error

Start Time

As we know Hibbett restocks at xx:17 and xx:47. This gives you plenty of time to run both restock times. Running for Hibbett restocks can be quite confusing due to how they work so we will quickly touch up on that now.

Most if not all bots should have an option in Hibbetts task creation page to set a drop time. This is important for initial and for restocks. We don't mean a task scheduler we mean a drop time input. We wont go into too much detail on why this is useful for initial but essentially the way you always want to start your tasks almost an hour before the initial drop as they ramp up their anti-bot measures as time closes in on the initial drop, so users will set the drop timer for whenever the drop is then start tasks an hour early.

This allows the tasks to cycle through all the necessary processes before it gets to the last stage, the submit order stage. Right before it submits the order it will stop the task and then sit waiting for the drop time you selected when creating the task. Once the task reaches the the input drop time, for example lets say the user input the drop time for 10:00:00am for the initial drop, the products stock will load and the task will attempt to submit the order IMMEDIATLY. This is the exact same process for restocks however you don't ned to worry about starting tasks an hour early.

Lets say its the day after the release and you are going to run restocks. Its 9:30am and you know that there might be a restock at 10:17am. You will want to setup your tasks using the drop time feature setup for 10:17am. Once your tasks are setup you can start them basically anytime along as its around 10 minutes before the restock time. This is because if you are using residentials its likely that many IP's in your resi pool are banned so it is a trial and error process of getting all your tasks on unbanned IP's. Lets say you are running 10 tasks using residentials. Its likely that atleast 50% of those tasks will be banned so you will need to stop and start them so they rotate to a new proxy in your proxy group and try again. This can take quite a long time so make sure you give your self plenty of time to work through your tasks.

Lets say you got all of your tasks ready, they have cycled through the correct procedure and are now waiting on your drop timer to finish. The restock time comes around and all your tasks attempt to submit order, you might hit a few, you might not and they might not even restock. So your best bet is to setup ready for the next one at 10:47am etc... All you have to do is stop your tasks, update the drop timer to xx:47 and start them again. You might have to go through the process of filtering out bad proxies but you can essentially start your tasks ready for the next restock straight after you have stopped tasks with the previous one. Like we said your tasks will go through the checkout process, pause right before it tries to submit the order then countdown your drop time input.

Although the Hibbett checkout process can use a-lot of residential data it wont use any data whilst it counts down waiting for the input drop time to finish. So to summarise, run for any restock then once your done, stop your tasks and update the timer for the next scheduled restock. Rinse and repeat every hour until you hit.

Proxies

Most if not all ISP's will be banned, even for restocks so make sure your provider explicitly says they work on Hibbett as many providers will advertise they work but they actually wont. Ideally you will want to use ISP's as they are faster but its hard to find ones that are unbanned. That leaves you with resis. Most resis will be fine, depending on the quality more or less IP's from your resi proxy pool will be banned so you will need to filter them out like we discussed above.

Task Count

You don't need too many tasks, as it can take up quite a-lot of data we suggest about 1-2 tasks per size you are running. If your only running a few sizes you can run more tasks per however overall you don't need too many tasks.

Captchas

There are no captchas for Hibbett initial or restocks