> For the complete documentation index, see [llms.txt](https://cesium.gitbook.io/cesium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cesium.gitbook.io/cesium-docs/modules/crystal/auto-double-hand.md). # Auto Double Hand Selects a hotbar totem in your main hand when your health drops or danger spikes. Selects a hotbar totem in your main hand when your health drops or danger spikes. ## What it does Auto Double Hand watches your health and the danger around you. When either crosses a threshold it switches your main hand to a hotbar totem, so you are holding a totem in both hands. If the offhand totem pops, the main hand one covers you. ## When to use it Use it against crystal and anchor players, where two hits can land inside a second. It buys you one extra pop when you most need it. ## Settings You can adjust these in the module panel: * Health threshold * Danger trigger (crystal or anchor nearby) * Swap back when safe ## Video {% hint style="info" %} A short clip of this module is on the way. {% 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cesium.gitbook.io/cesium-docs/modules/crystal/auto-double-hand.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.