> For the complete documentation index, see [llms.txt](https://docs.roachracingclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roachracingclub.com/gameplay/racing/aerodynamics.md). # Aerodynamics Roach positioning on the racetrack affects race performance. **How Aerodynamics Works** * A running roach creates an air flow behind it * This cuts air resistance for roaches behind it, giving them a small speed boost. * The closer a roach is behind another, the stronger Drafting effect (similar to real-world racing) * Players can use this effect strategically to win races **Strategic Implications** The aerodynamics system creates interesting race dynamics where trailing closely behind another roach can provide a speed advantage. This encourages strategic positioning during races and can lead to exciting come-from-behind victories. **Leading Position** The leading roach faces full air resistance and doesn't benefit from drafting. However, in certain modes, the race leader collects rewards placed along the track.\ \ **Trailing Position** Trailing roaches benefit from reduced air resistance, allowing them to conserve energy and potentially overtake the leader at strategic moments. The optimal trailing distance is close enough to benefit from drafting but not so close as to be blocked by the leading roach. This mechanic creates interesting race dynamics where trailing closely behind another roach can provide a speed advantage, similar to drafting in real-world racing. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.roachracingclub.com/gameplay/racing/aerodynamics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.