Troubleshooting
Answers to the issues people hit most. Still stuck? Reach out on the support Discord.
The toolbar button or tab is missing
Section titled “The toolbar button or tab is missing”- The editor lives inside the Blueprint editor. Open a Blueprint first, then look for the Toggle Code Editor button on its toolbar, or press Alt + C.
- Confirm the plugin is enabled in Edit → Plugins and that you restarted the editor afterward.
- It can also be summoned from the Blueprint editor’s Window → Code Editor menu.
Selecting a node loads nothing
Section titled “Selecting a node loads nothing”The editor only loads code for nodes backed by editable C++ functions:
- Pure Blueprint functions have no C++ source to show.
- Engine nodes resolve to precompiled source and open read-only.
- A node with no resolvable source loads nothing.
Select a node from your own C++ classes to see it populate.
A file is read-only and won’t save
Section titled “A file is read-only and won’t save”This is expected for engine source and any file the OS marks read-only. The plugin will not edit source it cannot rebuild. Make the edit in your own project code instead, or open the file in your IDE.
Save and Build does nothing or fails
Section titled “Save and Build does nothing or fails”- Save and Build uses Unreal Live Coding. Make sure Live Coding is available and enabled for your project, and that your C++ toolchain (Visual Studio build tools) is installed.
- Live Coding hot-reloads function bodies reliably. Changes to headers
(new or changed
UPROPERTY/UFUNCTION, changed signatures, new members) usually need a full editor restart and a normal compile. - Watch the build output for compile errors; a failed build leaves the old code running.
My header change didn’t take effect
Section titled “My header change didn’t take effect”Header-level changes are a Live Coding limitation, not a plugin bug. Close the editor, rebuild from your IDE (or with a normal compile), and reopen. Keep edits to function bodies for the fast in-editor loop.
AI features are greyed out or erroring
Section titled “AI features are greyed out or erroring”- Add an API key under Project Settings → Plugins → Code Editor: Claude API Key for Claude, OpenAI API Key for ChatGPT.
- Check the model and endpoint values for your provider are correct.
- Errors usually come from the provider: an invalid or unfunded key, a model name your account cannot access, or a network/proxy block on the endpoint.
- If responses get truncated, raise Regular Max Tokens (or Simple Query Max Tokens for short chats).
AI calls feel slow or expensive
Section titled “AI calls feel slow or expensive”Trim what gets sent:
- Lower Max History Messages and the Max Tokens caps for chat.
- For inline completion, use a smaller completion type and a tighter context type (for example N Lines Above Cursor with a small line count). Toggle them live with Ctrl + Alt + T and Ctrl + Alt + R.
An inline suggestion appeared but I want it gone
Section titled “An inline suggestion appeared but I want it gone”While a suggestion is highlighted, press Escape to discard it; the inserted text is removed. Keep it by continuing to edit.
A shortcut isn’t working
Section titled “A shortcut isn’t working”- Click into the code pane so it has focus, then try again.
- If a chord clashes with another binding, remap it under Keyboard Shortcuts in settings, or use Reset Keybindings to Defaults to start clean.
Code changed outside the editor
Section titled “Code changed outside the editor”If you edited the .h / .cpp in your IDE while the tab was open, reselect the
node to reload the latest from disk so you don’t save a stale copy over it.