Round1
Complete guide on our Round1 module
Round1 task creation is relatively straightforward, but the site uses Hcaptcha and sensitive to proxy quality. Preparing your tasks, proxies and profiles before a drop is important.
Video Guide
Preliminary Checklist
Before creating Round1 tasks, confirm that you have completed the following:
Round1 can be run on a local computer or server. Both can perform well, provided the system can handle your tasks.
Supported Modes
Entry
Entry mode is the only mode currenty needed for round1, it is used to submit entrys for limited products.
Task Prep Breakdown
Name
An optional name used to organize your tasks.
For example:
Mode
Select Entry to create Round1 entry tasks.
Entry mode does not require a round1 account or session.
Profile
Select the profile or profile group Stellar should use during checkout.
Your profile should contain:
A valid email address
Correct shipping information
Correct billing information
A valid payment method
Information matching the selected region
Incorrect or inconsistent profile information can cause address, payment, or profile declines. also keep in mind to use REAL names for matching IDs as they tend to check IDs during pick up.
Checkout Proxy
Select the proxy group the task should use.
High-quality proxies are especially important for Pokémon Center because poor or blocked proxies can cause:
Proxy blocks
loading issues
Captcha issues
Homepage loops
Slower page loading progress
Failed sign up attempts
A practical approach is to:
Prioritize clean ISP proxies for your main tasks.
Use high-quality residential proxies for your remaining tasks.
Test multiple proxy pools and providers instead of relying on one source.
Ask your proxy provider which proxy type currently performs best on Round1.
Product URLs
Enter the product URL that the task should attempt to use for signups.
A Product URL is the identifying portion of a Round1 entry page.
Example URL:
Using a Placeholder
When the correct product information is not available yet, enter a random placeholder so you can save your tasks.
Example:
The placeholder allows you to create tasks until you are able to input the actual sign up link. Once your cook group provides the confirmed product URL.
Delay
The delay controls how frequently the task retries applicable steps.
Recommended starting delay:
Lower delays may allow faster retries but can increase the risk of blocks and errors. Higher delays are generally safer but may respond more slowly.
Start Time and End Time
These optional settings control when a running task may begin processing and when it should stop.
If you use a scheduled start or end time, confirm the correct date, time, and timezone before the drop.
Recommended Drop Setup
For a standard drop setup:
Create valid profiles.
Add multiple groups of clean ISP and residential proxies.
Create tasks with a placeholder URL.
Use a delay around 3
000.Use real info that you are able to provide with a matching ID.
Use real emails over catchalls example: gmail, yahoo.outlook.etc.
Mass edit the placeholder to the confirmed URL as soon as possible before the drop.
How Many Tasks Should I Run?
A common starting point is:
Scale based on:
Number of valid profiles
Number and quality of your proxies
Number of proxy providers and pools
Computer or server performance
Current task limits announced by Stellar
Drop-specific instructions
More tasks do not automatically produce better results. Running more tasks than your proxies, profiles, or computer can support may reduce overall performance.
When Do I Start My Tasks?
There are two common approaches.
Start Early — Recommended
Start your tasks before the drop.
The tasks may display:
This is normally expected when the Round1 module has not been enabled yet. Once Stellar enables the module, running tasks can automatically start running.
This approach gives you time to identify profile, proxy, or setup problems before the drop.
Recommended Timeline
Before the drop:
Update Stellar.
Confirm your profiles and proxies.
Precreate your sign up tasks with a placeholder PID.
Start your tasks early.
Monitor Stellar and cook group announcements.
Mass edit the confirmed product URL before the drop goes live.
The sign up proccess is strictly first come, first served.
Common Errors and Fixes
Module Disabled
What it means: The Round1 module has not been enabled for the current queue or drop.
What to do:
Leave correctly configured tasks running.
Wait for the module to be enabled.
Monitor Stellar announcements.
Restart only if Stellar staff recommends it or the task remains stuck after the module is confirmed active.
Last updated
Was this helpful?