Sneakersnstuff
You can only run this site with very very good proxies, other proxies will not be successful due to Cloudflare’s recent extensive system updates. API providers must adjust to the new system. As long as this notice is present, the module will not function as intended.
Requirements
Monitor Input: Product URL
Mode: Cart Checkout
Payment Methods: PayPal Card
Specific Sizing Support: True
Force Start Support: True
Different Billing/Shipping Support: True
Recommended Proxies: Residentials
Recommended Delay: ~1000
Recommendations / Knowledge
On a product launch (with a timer), the bot will solve Cloudflare, pick up the timer and start tasks a few seconds earlier; start tasks a few minutes (3-5) before release time / when Cloudflare goes up; once the product has dropped SNS website will perform poorly and thus requests will take a lot longer than usual to go through
SNS rarely schedules releases and almost only restocks raffled products, if you see a monitor ping, start tasks ASAP, speed is of great importance; items will very likely have a captcha, until your captcha provider responded, start solving captchas through the manual solver
99% of the restocks drop with a carthold (item being reserved in another customer’s cart), these usually last for 10 minutes, it is only a waste of proxies to run the entire 10 minutes after the item dropped; rather start about 8 minutes after you saw a monitor ping, once carted you have plenty of time to check out
On items with captcha, every add to cart attempt equals one captcha request, please keep that in mind, running restocks on hyped items can become very captcha intensive
A delay of 2000 is sufficent
Error Codes / Possible Errors
All Carts Reserved:
the item you are trying to cart has carthold, hyped items restock / drop with a carthold, which usually lasts for 10 minutes in which the item cannot be added to cart
ATC Captcha Invalid, solving:
the submitted captcha token for an add to cart attempt was invalid, meaning the captcha was older than two minutes (should happen in the rarest cases)
Internal Server Error:
SNS failed to properly process the request, open a ticket if this occurs more often
SNS Down (Maintenance):
the site is currently under heavy load and not reachable, usually if you are presented with this error, it will stay for some time and your tasks will not be able pick up the product
(…) Conn:
the request failed, this can either be caused by the website not responding or due to proxy connectivity issues
(…) [404]:
the requested page is unavailable
(…) [502]:
SNS' servers are under heavy load, it will take longer for requests to complete
(…) [403]:
the request was blocked by the server
Unknown Error (…):
Open a ticket in the Discord server and post the error code
Last updated