> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/miltech-fighters-m2k-c/product-guides/keybinding-guide.md).

# Keybinding Guide

<table><thead><tr><th width="184">Description</th><th>Keybind</th><th>Notes</th></tr></thead><tbody><tr><td>Release/Shoot Weapons (Missiles, Bombs, Guns)</td><td><code>TOGGLE WATER RUDDER</code></td><td>Same keybind is used for all three, however, only shoots the selected and armed weapon. More info <a data-mention href="/miltech-fighters-m2k-c/aircraft-and-systems/weapon-and-defensive-systems.md">Weapon and Defensive Systems</a></td></tr><tr><td>Release Flares</td><td><code>TOGGLE ALTERNATOR 3</code></td><td>More info <a data-mention href="/miltech-fighters-m2k-c/aircraft-and-systems/weapon-and-defensive-systems/countermeasures.md">Countermeasures</a></td></tr><tr><td>Spoilers</td><td><code>TOGGLE SPOILERS</code></td><td>Spoiler axis, spoiler extend and spoiler retract will NOT work on this aircraft. Spoilers are binary (extended/retracted), and a "fake spoiler" is used to simulate drag induced by other components. As such, TOGGLE SPOILERS is the only valid keybind on this aircraft.</td></tr><tr><td>Afterburner</td><td><code>TOGGLE AFTERBURNERS</code></td><td>This aircraft follows the same afterburner logic as you may find on the F-18. Hence, afterburner toggle is a necessary keybind.</td></tr><tr><td>Nose Wheel Steering</td><td><code>TOGGLE ALTERNATOR 4</code></td><td>The default NWS Keybinds that you may be familiar with (SET NOSE WHEEL STEERING TO LIMIT) are not available for this aircraft. Due to the design, we needed a "TOGGLE" rather than a "SET" variable, hence why we chose to use this keybind variable.</td></tr><tr><td>Drag Chute</td><td>Not Available</td><td>It could be keybinded using the corresponding LVAR, but "native"  keybinds are not planned at this time.</td></tr></tbody></table>


---

# 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.miltechsimulations.com/miltech-fighters-m2k-c/product-guides/keybinding-guide.md?ask=<question>&goal=<user_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.