> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/retailers/round1.md). # Round1
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** coming soon... *** ## **Preliminary Checklist** Before creating Round1 tasks, confirm that you have completed the following: * [ ] Updated StellarAIO to the latest version * [ ] Created profiles with valid billing, shipping, payment and email information * [ ] Added clean, high quality ISP and/or residential proxies. It's best to use multiple proxy providers and/or multiple proxy pools * [ ] Enabled cook group notifications for product URLs, PIDs, and drop updates * [ ] Precreated your tasks before the drop 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: ``` phase 1, phase 2, phase 3, etc. ``` ### 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: ``` https://round1usa.cmpgn.page/Rls7N5 ``` #### Using a Placeholder When the correct product information is not available yet, enter a random placeholder so you can save your tasks. Example: ``` 83195729 ``` 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: ``` 3000 ``` 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 Guest-mode drop setup: 1. Create valid profiles. 2. Add multiple groups of clean ISP and residential proxies. 3. Create Guest tasks with a placeholder URL. 4. Use a delay around 3`000`. 5. Use real info that you are able to provide with a matching ID. 6. Use real emails over catchalls example: gmail, yahoo.outlook.etc. 7. 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: ``` 3 tasks per profile ``` 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. ### Option 1: Start Early — Recommended Start your Guest tasks before the drop. The tasks may display: ``` Module Disabled ``` 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. ### Option 2: Start When the Queue Goes Live You can start tasks when the Pokémon Center queue becomes available. This requires faster reaction time and gives you less time to correct setup problems. ### Recommended Timeline Before the drop: 1. Update Stellar. 2. Confirm your profiles and proxies. 3. Precreate your sign up tasks with a placeholder PID. 4. Start your tasks early. 5. Monitor Stellar and cook group announcements. 6. 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.stellaraio.com/stellar/retailers/round1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.