> For the complete documentation index, see [llms.txt](https://help.refractbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.refractbot.com/introduction-to-botting/cookgroups.md). # Cookgroups A cook group is an online community, usually hosted on Discord, where members share release information, strategies, and resources for securing limited products. If you are serious about botting, you need one. It is not optional. ## Why you need a cook group A cook group does two things for you: it tells you what is dropping and when, and it fills every gap our guides deliberately leave open. * **Knowing what is dropping:** drop calendars, restock alerts, monitors, and early links. Refract checks out products. It does not tell you what to run it on. That information comes from your group. * **Account, profile, and proxy generation:** how to create them, where to get them, and what is currently passing on each site. * **Jigging:** which methods each retailer currently tolerates. * **Cancellations:** what members are doing right now to reduce them. * **Provider recommendations:** which proxy, server, and other providers are actually performing. Every item on that list is something the Refract team does not help with. When our guides say "ask your cook group," this is the list they are pointing at. ## What to look for Quality varies a lot between groups. An active group with a real community beats a big name. Look for: * Recent, active discussion for the sites you run * Success posts from members, not just staff * Guides and support channels that are actually maintained {% hint style="warning" %} **Not in a cook group yet?** Ask around in the community for an active one to join, and start there. There are many options, and members are usually happy to point you somewhere active. {% endhint %} --- # 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://help.refractbot.com/introduction-to-botting/cookgroups.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.