> 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/roach-management/roach-mood.md). # Roach Mood How asset price movements affect roach performance Every Roach is born with an assigned Mood, shown as an arrow on the roach’s cryptocurrency icon. Mood can be Bullish (arrow up) or Bearish (arrow down) How Mood Affects Races\ \ Mood influences every race by giving a small passive boost or slowdown depending on market movement. Read more about it here (hyperlink)\ \ If the chart of your roach’s asset is going UP during the race:\ – Bullish roaches receive a small passive speed boost (even without opening trades)\ – Bearish roaches receive a slight passive slowdown\ \ If the chart of your roach’s asset is going DOWN during the race:\ – Bearish roaches receive a small passive boost\ – Bullish roaches get a slight slowdown\ \ This effect is minor but noticeable over multiple races.\ \ **Long-Term Balance**\ Mood creates short-term variability in race dynamics, but over a full round the system remains balanced by biology. \ \ This means:\ \- Mood may give temporary advantages or disadvantages\ \- All roaches have equal long-term racing potential overall\ \- Mood affects how a roach performs in specific market conditions, not its overall power.\ \ **Changing Your Roach’s Mood** If you want to modify your roach’s biology (including Mood), you can use a Reroll.\ Read more about Rerolls [here](/gameplay/roach-management/roach-reroll.md). --- # 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/roach-management/roach-mood.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.