Ffennaradocs

Home

Troubleshooting

Use this page when Fennara does not install, connect, run MCP tools, or complete a request the way you expect.

Quick checklist

Try these first:

  • Close Godot before installing or updating the plugin.
  • Reopen Godot after the installer finishes.
  • Fully quit and reopen any MCP app after installing or updating Fennara MCP.
  • Make sure your API key is saved in plugin settings.
  • If more than one Godot project is open, use Set as MCP Target.
  • If a request failed, copy the full error message and any incident ID shown.

Logs

Fennara plugin logs are written inside Godot's user:// data folder:

user://.fennara/logs/fennara_YYYY-MM-DD.log
user://.fennara/incidents.jsonl
user://.fennara/incidents.jsonl.old
user://.fennara/fennara.log

The daily fennara_YYYY-MM-DD.log file is the normal plugin log. incidents.jsonl stores structured local incident records. The .old file is a rotated incident log. fennara.log is a legacy fallback path.

user:// is Godot's user data location for the project, not the project folder itself.

Incident IDs

Fennara may show an incident ID when something fails.

Plugin Incident ID: PLG-...
Incident ID: INC-...
Request ID: ...

PLG-... means the Godot plugin recorded the issue locally.

INC-... means the backend recorded the issue.

Request ID identifies the specific plugin request when available.

When asking for help, include the full error text, the incident ID, the request ID if shown, and the latest plugin log.

Installer issues

Close Godot before running the installer. Godot can keep the Fennara GDExtension DLL or shared library loaded while the editor is open, which can prevent the installer from replacing plugin files.

If the installer says a file is still in use, close Godot and any Fennara tools, then run the installer again. For the normal install flow, see Get Started.

If the plugin does not appear after install:

  • confirm you selected the folder that contains project.godot
  • reopen Godot
  • enable the Fennara plugin in Godot's plugin settings
  • check that addons/fennara/fennara.gdextension exists in the project

MCP issues

After installing or updating Fennara MCP, fully quit and reopen the MCP app. Some apps keep MCP servers running until the app is restarted, so they may keep using an old Fennara MCP version.

If MCP tools are connected to the wrong project, open the correct project in Godot and use Set as MCP Target.

If an MCP app cannot find Fennara:

  • check the MCP executable path is absolute and exists
  • check the app's MCP config syntax is valid JSON, TOML, or whatever that app expects
  • restart the MCP app after editing config
  • make sure the Fennara plugin is installed in the target Godot project
  • make sure your API key is saved in plugin settings
  • make sure the account has an active trial or Pro subscription

Fennara MCP exposes the Godot-aware tool set, including SemanticSearch and shader search. It does not expose read_file or file_ops. See MCP tool availability.

If an MCP tool says the account needs an active trial or Pro, the device trial limit may already be used or the trial may have expired. Upgrade to Pro from Billing, then retry the MCP tool.

Connection and API key

If the plugin says the API key is missing, open plugin settings and paste your key from the Fennara dashboard.

If the plugin says the API key is invalid, copy a fresh key from the dashboard and replace the saved key in plugin settings.

If the plugin says the account is inactive, check your account status from the dashboard.

If the plugin says the account is not eligible for another free trial on this device, that device has already used the trial allowance. Upgrade to Pro to continue using plugin chat and MCP tools.

If the plugin reports a protocol or version mismatch, update Fennara with the latest installer from Get Started.

For setup steps, see Get Started.

Credits and models

If a request fails because credit is exhausted, check Pricing and credits and the Usage page.

If a request fails because a model is invalid or unavailable, choose another model from Models.

If a provider times out or fails upstream, retry the request or switch models.

Large chats, high reasoning effort, long tool outputs, and context summaries can use more credit. See Usage page for request-level details.

Tool failures

GDScript diagnostics come from Godot's language server. If diagnostics look stale after files changed, restart Godot and try again. For how Fennara uses diagnostics, see Diagnostics.

Scene validation warnings are real Godot configuration or engine warnings captured while loading or checking a scene. Treat them as useful signals, especially after scene edits.

If a screenshot or scene tool fails, check that the scene path exists, the project is open in Godot, and the correct project is set as the MCP target when using MCP.

If Fennara cannot recover from a tool failure, include the expanded tool card output and the latest plugin log when asking for help.

← Previous
Pricing and credits