15. Keybinds
There are four separate places keys are set in a game running Redwire. Knowing which is which saves a lot of confusion.
| Where | What it binds | How to get there |
|---|---|---|
| Redwire → Settings → Keybinds | Redwire’s eleven mod actions | Right Shift → Settings → Keybinds |
| Redwire → Client Tools → (a tool) → Keybind | Toggling that one tool | Right Shift → Client Tools → pick a tool |
| Redwire → Scripts → (a script’s row) | Starting and stopping that one script | Right Shift → Scripts |
| Minecraft → Options → Key Binds | The game’s own controls | Escape → Options → Key Binds |
15.1 The one key to remember
Right Shift opens and closes the Redwire interface. It works everywhere — the main menu, singleplayer, a server, and over an open container.
While you are typing in a text box, Right Shift behaves as an ordinary shift key and does not open or close anything. You need it to type capitals, so it stays a modifier for as long as your cursor is in a box — inside Redwire, and in the search and address boxes on the re-styled Minecraft menus too.
15.2 Redwire’s eleven actions
Set in Settings → Keybinds. None are bound by default except Open Redwire.
| Action | What it does | Needs |
|---|---|---|
| Open Redwire | Opens and closes the interface (Right Shift) | — |
| Toggle Packet Logger | Starts or stops recording packets | — |
| Toggle Packet Interceptor | Turns interception on or off | — |
| Flush Packet Queue | Sends every held packet | — |
| Clear Packet Queue | Throws the queue away | — |
| Disconnect and Flush | Sends the queue, then disconnects | A server |
| Toggle Scanner | Starts, pauses or resumes a scan | A server |
| De-sync GUI | De-syncs the open container | A container screen open |
| Save GUI | Saves the open container’s state | A container screen open |
| Load GUI | Restores a saved container state | — |
| Close GUI Without Packet | Closes the screen without telling the server | A container screen open |
Each does exactly what the matching button does. They are the same code, so a keybind and a click can never behave differently.
The four GUI actions are explained in The In-Game Overlay.
Open Redwire edits Minecraft’s own binding. That one row and Minecraft’s Options → Key Binds → Miscellaneous are two views of the same setting, saved in
options.txt. Change it in either and the other follows.
15.3 Per-tool and per-script keybinds
Every one of the 42 Client Tools has its own keybind field, at the bottom of its settings.
Pressing it toggles that tool on and off without opening Redwire. This is what makes tools like Freecam, Zoom and Fullbright practical — you flip them mid-play.
Freecam has a second one: Control Player, which drives your body while the camera stays put.
Tools most worth binding:
| Tool | Why |
|---|---|
| Freecam | Only useful if you can enter and leave it quickly |
| Zoom | Held, like a spyglass |
| Fullbright | Flipped constantly — caves versus surface |
| Hidden Blocks | Costs performance, so run it only when you need it |
| Safe Walk | On for building at height, off otherwise |
Every script has one too, in the box immediately left of its Start button on the Scripts page. It toggles: press once to start the script, press again to stop it. Renaming a script carries its key with it.
15.4 Setting or clearing a key
- Click the keybind field. It turns red and shows
.... - Press the key you want. It binds immediately.
While the field is listening:
| Key | Redwire’s own fields (Settings → Keybinds, per-tool, per-script) | Minecraft’s Key Binds screen |
|---|---|---|
| Backspace | Clears the binding | — |
| Escape | Cancels, leaving the binding as it was | Clears the binding |
These genuinely differ, and it is not an oversight. Minecraft has always used Escape to unbind, and its screen has no other way to do it, so Redwire’s version of that screen matches vanilla exactly. Redwire’s own fields have Backspace for clearing, which frees Escape to do the more useful thing and back out of a mis-click.
A field showing N/A has nothing bound.
15.5 Conflicts
Redwire does not stop you binding a key that Minecraft already uses. If you bind Fullbright to
F, both Fullbright and Minecraft’s fog key fire on the same press.
Minecraft’s own Key Binds screen shows conflicts in red, but it only knows about Minecraft’s bindings — it cannot see Redwire’s. So:
- Check Minecraft’s Key Binds screen for a free key before binding it in Redwire.
- The function keys, the numpad, and the mouse’s extra buttons are usually unused.
- If two things happen on one press, something is double-bound.
15.6 Where bindings are saved
| Bindings | File |
|---|---|
| Minecraft’s own, and Open Redwire | <game>/options.txt |
| Redwire’s ten other actions | <Redwire folder>/settings.redwire |
| Per-tool keybinds | <Redwire folder>/tools.redwire, and inside each .redprofile |
| Per-script keybinds | <Redwire folder>/scriptkeys.redwire |
Per-tool keybinds are part of a profile. Loading a profile replaces them along with everything else, so two profiles can use different keys for the same tool.
Per-script keybinds are deliberately NOT inside the
.redscriptfile. A script is a document people send each other; a keybind belongs to your keyboard. Keeping them apart means a script you share does not arrive claiming one of someone else’s keys, and one you are sent does not claim one of yours.