1. Start: 1 minute before drop
  2. We suggest regular mode but safe mode is a good fall back option now.
  3. Monitors: We suggest using both Desktop Category and Combo per item desired.
  4. Monitor/Error Delays 0-750
  5. It is suggested to make multiple tasks with Checkout Delays ranging from 500-3500.
  6. Choose size for clothes/ shoes or Random for Accessories/Hats

See Supreme 101 guide for more info (https://projectdestroyer.com/2018/08/27/cop-supreme-101/)   

MODES

Supreme (mobile) – Request based checkout methodology.

Supreme (desktop) – Request based checkout methodology.

*Note Mobile and desktop are just 2 variations of Supreme regular mode.

Run a combination of (mobile) and (desktop). You can use any monitor type with either (mobile) or (desktop) sites.

Supreme (safe) – Browser based checkout methodology

  • Leave each window open when running.
  • Use captcha harvesters to harvest captchas for these as well.
  • Use fast proxies or local host

*Note If you experience an issue where the item carts and then a blank screen shows at checkout (but the [1] and “Checkout Now” buttons are still showing) then you should either stop and start task again or click the [1] and direct to cart, then go back to checkout ).

This is an issue caused by slow proxies and poor error handling on Supremes end – an error throws that they don’t handle correctly and so the checkout form fails to load. Use fast proxies or local host to avoid this altogether.

Restocks

  1. Monitor type does not matter in URL mode, use any.
  2. Use the URL from Supreme website for the item + color you want.
  3. Do not select Captcha for Restocks.
  4. Monitor & Error Delays (see note for restocks)
  5. Checkout delay 0
  6. Style: Use the same color as the URL you chose
  7. Choose size for clothes/shoes or Random for Accessories/Hats
  8. DO NOT USE SAFE MODE FOR RESTOCKS

Note for restocks

Because Supreme has started to ban IPs now, if you don’t have proxies, you will have to experiment with Error/Monitor Delays. If you don’t have proxies, 3-4 tasks with an Error Delay of 500 and a Monitor Delay of 1000 is recommended (You should test this as well). To test, setup number of tasks, with desired delays, and run them, time how long they run until you see the “429” error, then wait 20-30 minutes, adjust delays, and test again.  (Failed Carting is the same as the 429 error, too many requests. Temp rate limiting ban.)

Example of Testing w/ proxies: 5 Tasks with 100/100 Delays run for 58 sec until I get 429. Adjust Delays to 500/500 and try again. Do this until you do not get the error msg anymore, then take note of what your settings are for next time.

See Supreme 101 guide for more info (https://projectdestroyer.com/2018/08/27/cop-supreme-101/)

For complete guide refer to the link below –

https://docs.google.com/document/d/107P0pdSwHT_O0coonKwBDAfBYmDouozFcl7EobboNyY/edit?usp=sharing