List Buffout 4 crash logs on this machine, newest first.

Searches the standard Fallout 4 crash-log folders under the user's Documents directory (override with the F4_DOCS_DIR environment variable). Returns up to limit entries with absolute path, last-modified timestamp (ISO 8601) and size in KB, plus the directories that were searched. Read-only: nothing is opened or modified.

Parse a Buffout 4 crash log into structured sections.

With no path, parses the NEWEST crash log found in the standard folders; pass an absolute path (e.g. from list_crash_logs) to parse a specific one. Explicit paths must be crash logs: either inside the standard crash-log folders or named crash-*.log — anything else is refused with an error. Returns the exception (type, address, faulting module), probable call stack, F4SE plugin list, plugin load order as logged, modules, settings, and any parse warnings. The raw STACK dump is truncated to 50 lines to keep responses small. Returns {"error": "no crash logs found", "searched_dirs": [...]} when there is nothing to parse.

Read the live Fallout 4 load order and cross-check it against Data.

Parses %LOCALAPPDATA%\Fallout4\Plugins.txt ('*' prefix = enabled) and lists the .esm/.esp/.esl files actually present in the game's Data folder. Reports both mismatch directions: enabled plugins whose file is missing from Data (a classic missing-master crash cause) and files in Data that are not in the load order. Implicitly loaded plugins (Fallout4.esm, official DLC, Creation Club content) are never listed in Plugins.txt and are excluded from the mismatch lists. When Mod Organizer 2 manages the game, the on-disk Plugins.txt is NOT the real load order (MO2 virtualizes it): plugins_txt_reliable is false, the cross-check is skipped, and a warning explains why. Read-only.

Scan the installed Fallout 4 for versions, F4SE health, and mod managers.

Discovers the game root (F4_GAME_ROOT env var, known locations, then all Steam libraries), then reports: game exe version, F4SE loader/DLL version, Address Library presence and whether it matches the game version, Buffout 4 variant + version, a crash_logging report (which DLLs write crash logs; a recognized_bundle means those DLLs ship together as ONE mod — e.g. Buffout 4 AE + CrashLoggerAE — and are NOT rival loggers; trust its notes over pattern-matched folklore), all F4SE plugin DLLs, BA2 archive count, crash-log folders, and which mod manager is in use (MO2 / Vortex / manual / unknown). Call this FIRST in any diagnosis session — version mismatches here explain many crashes before the log is even read. Read-only.

One-shot crash diagnosis: parse log + scan environment + match signatures.

Runs the full advisory pipeline: parses the given crash log (or the newest one when path is omitted), scans the game environment, reads the live load order, and matches everything against the bundled crash signature knowledge pack. Returns a compact log summary, ranked findings (severity then confidence, each with cause, suggested user fix, and the matched evidence lines to verify against), plus the full environment and load-order dicts. Findings are ADVISORY ONLY — this server never changes any file; fixes are actions for the user to take themselves.

Look up a mod on Nexus Mods (read-only; requires NEXUS_API_KEY).

Accepts a Nexus URL (https://www.nexusmods.com/fallout4/mods/47359) or 'game/mod_id' (e.g. 'fallout4/47359'). Returns mod metadata (name, version, author, summary) and the available files with versions and upload dates — useful for checking whether a suspect mod has a newer version or a compatibility patch. Never downloads anything. Without NEXUS_API_KEY this returns an error explaining that mod lookups are optional; every other tool still works.

Verify the Nexus API key works and report account status.

Returns the account name, premium/supporter flags, and user id. Use this to troubleshoot lookup_mod failures. NEXUS_API_KEY is optional — only the two Nexus lookup tools need it.