> For the complete documentation index, see [llms.txt](https://lucidious89-tutorials.gitbook.io/deluxe-battle-kit-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucidious89-tutorials.gitbook.io/deluxe-battle-kit-tutorial/deluxe-battle-kit-for-v21.1/mid-battle-scripting/command-keys.md). # Command Keys Trigger Keys are only half of the equation, however. Once you have a Trigger Key set that will trigger at a specific point in battle, you need to set something that you want to actually *happen* at that point in battle. This is done by setting yet another hash as this Trigger Key's value. In this hash, you can set a whole new set of keys with their own set of values. These keys are what actually prompt specific commands to be carried out. Because of this, I will refer to these set of keys as "Command Keys". In the following subsections, I will go over every possible Command Key, how they can be set, and what actions they will perform. Command Keys which have related effects or affect similar areas of battle have been grouped together to make them easier to find. Note that Command Keys are always strings, and always begin with a lower case letter. --- # 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://lucidious89-tutorials.gitbook.io/deluxe-battle-kit-tutorial/deluxe-battle-kit-for-v21.1/mid-battle-scripting/command-keys.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.