17. Troubleshooting

Common problems, in the order people usually hit them.

17.1 Redwire will not load

The game crashes on startup, or Redwire is not in the mod list.

Check, in this order:

Minecraft is exactly 1.21.11. Not 1.21.10, not 1.21.12. Redwire hooks deep into the game’s internals and those hooks are version-specific.
Fabric API is installed, and it is the 1.21.11 build. Redwire cannot start without it. This is the single most common cause.
Only one Redwire jar is in mods. Updating without deleting the old jar leaves two, and they fight.
Java 21 or newer. Most launchers handle this; if yours does not, point the instance at a newer Java.

If it still crashes, the crash report in <game>/crash-reports/ names the mod that failed.

17.2 Right Shift does nothing

Are you typing in a text box? Right Shift stays a normal shift key while your cursor is in one, so it does not slam the interface shut mid-word. Click away from the box and try again.
Has the key been changed? Check Minecraft’s Options → Key Binds → Miscellaneous for Open Redwire, or Redwire’s own Settings → Keybinds. They are the same setting.
Is another mod using Right Shift? Rebind one of them.
Did Redwire actually load? See §17.1.

17.3 The Dashboard shows N/A everywhere

You are in singleplayer or on the main menu. Most of the Dashboard describes the server you are connected to, and there is not one. This is normal.

On a server and still seeing N/A? Some values only arrive when the server sends them. Give it a few seconds after joining. A server that never sends its brand will keep showing N/A for that row permanently — that is the server’s choice, not a fault.

17.4 The packet logger shows nothing

Did you start it? The logger is off by default. Packet Tools → Start Logger.
Are your filters hiding everything? Set Direction, Category and Status back to All, and clear the search box.
Did you suppress the packets you were looking for? Check the Suppressed Packets list and remove anything that should be logged.

17.5 The interceptor catches nothing

Both of these must be true:

The interceptor is enabled — the button in Interceptor Controls.
At least one packet type is ticked in the Intercepted Packets list.

Either alone does nothing. Also check you ticked the right side: a ClickSlot packet is C2S, a OpenScreen is S2C.

17.6 “Byte view unavailable on this connection.”

You are in singleplayer. A singleplayer world passes packets between two parts of the same program, in memory — they are never turned into bytes, so there is nothing for the hex editor to show.

Decoded Fields still works. For the hex editor, join a real server, including your own world opened to LAN.

17.7 The Scanner finds nothing

You must be connected to a server. The button is greyed out otherwise.
An empty plugin list is a real result, not a failure. Vanilla, Fabric and Forge servers do not use the plugin:command convention at all, so there is nothing to find. So do some proxies, which only show you their own commands.
Some servers hide their command list. Several anti-exploit plugins do this deliberately.
Results are cleared when you leave a server. Scan again after joining.

17.8 A Client Tool does nothing

Is it actually enabled? The Enabled switch at the top of its settings, not just having the tool selected.
Is a setting it depends on switched off? Greyed-out settings do not apply. See Client Tools §10.3.
Is it a tool the server overrules? Several tools are honest about their limits in the reference: Anti Debuff cannot stop a server-side effect, Friendly Endermen only works where your game owns the entity, Air Place only works where the server does not check. Read the tool’s entry.
Does it need something to be true? Auto Fish needs a rod in hand and water in front of you; Auto Eat needs food that is not blacklisted.
Check latest.log for a line about it. A tool whose per-tick work fails now writes Client tool 'name' threw while ticking; it is being skipped once, with the error under it. Before this, such a failure was silent and stopped every tool below it in the list from running that tick — so one broken tool could look like several unrelated ones being broken.

17.9 Remote Control clients cannot find each other

Same Redwire version on every client. A mismatch will not connect.
Same local network. Two computers on different Wi-Fi networks, or one on a guest network, cannot see each other.
Firewall. Redwire broadcasts on UDP port 45610 and opens a TCP connection to the host. Allow Java through your firewall on private networks.
Check the code, including character order. It is not case-sensitive.

Realms screens, player reporting, and in-game container screens are deliberately untouched. So is any screen added by another mod.

Anything else being vanilla means the swap did not happen — worth reporting, with the name of the screen and how you reached it.

17.11 The interface is too big, too small, or the wrong colour

All in Settings → Appearance:

Text Scale — 0.5× to 2×.
Transparency — 0% solid to 90% see-through.
Theme — red, blue or purple.

Redwire’s Text Scale and Minecraft’s GUI Scale are separate settings. Changing Minecraft’s does not resize Redwire’s interface, and vice versa.

17.12 A script does nothing when started

Does it have an Event block? Nothing else can start a script. A canvas full of Actions with no Event will run and do nothing.
Are the blocks actually wired? A block with no incoming flow wire is never reached.
Are the required fields filled in? Fields marked * must have a value.
Is the event’s filter too narrow? An OnChat with a filter only fires on messages containing that text. Clear the filter to test.
Is the script even running? The button reads Stop while it is. The editor is read-only while a script runs — that is how you can tell at a glance.
Are you in the right place? Blocks that need a world do nothing on the main menu.

17.13 I lost my settings

Everything is in the Redwire folder — see Files and Folders.

Did you change Redwire Directory? Changing it does not move your files. Your old setup is still in the old folder; copy it across, or set the path back.
Did you load a profile? Loading one replaces every tool setting with no undo.
Are you on a different instance? Each Minecraft instance has its own Redwire folder unless you have pointed them at a shared one.

17.14 A bulk send stops part-way

You ask for 500 copies, the connection stays up, no error appears — and the server clearly only acted on a fraction of them.

First, find out where they went. Turn on the Packet Logger and run the burst again, then count the entries for that packet. The logger records inside the client’s own send call, so it counts what your client handed to the network:

All 500 are there. Your client sent them; the far end discarded the rest. Read on.
Far fewer are there. Something stopped the run early — worth reporting, with the packet name.

If the server discarded them, there are two separate reasons it might have.

The packets were out of date. Container packets name the window they belong to, and a server silently drops one naming a window it has moved on from. Redwire refreshes that number on every copy it sends — see Packet Tools — so this should not bite unless you have hex-edited the packet, which switches the refresh off deliberately.

The server limits your packet rate. This is the common one, and nothing on the client can talk it round. Many servers cap how many packets a second they will accept from one player, and several drop the surplus silently rather than kicking you. Shop and menu plugins often add their own cooldown on top.

The tell is that Delayed works and Instant does not. Switch Mode to Delayed in ticks and set the delay to 0 — that sends one packet per tick, 20 a second, which almost everything tolerates. Raise the delay until it goes through cleanly. It is slower, and that is the trade: Instant hands the whole run over in a single tick, and a server that will not take it that fast will not take it that fast.

17.15 I switched account and something is off

Full detail is in Accounts §18.8; the three that are not obviously about accounts at all:

The server still shows your old name. You switched while connected. A server is told who you are once, when you join, and never asks again — leave, switch, then rejoin.
You can join but not talk. Signed chat uses a key tied to the account. Redwire rebuilds that key when it switches, so a server rejecting your messages means that step failed — worth reporting, with the server version.
Your accounts came back empty after moving the Redwire folder. The names are still there but the tokens are not, which means accounts.key did not travel with accounts.redwire. Copy the key file across from the old folder.

17.16 Getting more information

Crash reports: <game>/crash-reports/. The report names the mod that failed.

The game log: <game>/logs/latest.log. Everything the game and its mods printed this session.

When reporting a problem, the useful things to include are:

your Redwire version (bottom of the main menu),
your Minecraft, Fabric Loader and Fabric API versions,
what you did, what you expected, and what happened instead,
the crash report or log if it crashed.