Appearance
UE5
The Unreal Engine 5 stack pack. Building an Unreal project and reading a crash log both mean facing a wall of output – UBT and the automation tool bury a handful of real errors in thousands of lines, and a Saved/Logs file is longer still. This module wraps the two entry points that matter, the build batch files and the log, and turns each into a filtered table you scan instead of a scroll you skim. Every command is on demand – a build costs, so nothing here rides a hook – and both tools carry a parse path that reads a captured log, so you can distill an error with no live engine in reach.
In Practice
The two tools split cleanly: ubt.nu handles the build side, from shelling Build.bat to parsing a captured log, and log-distill.nu handles the runtime side, distilling a finished Saved/Logs file.
Build a target and read the errors as a table. You want to compile the editor target and see what broke without scrolling the build log:
nu ubt.nu build MyGameEditor Development Win64 --uproject MyGame.uproject --engine "C:/UE_5.4"It resolves the engine dir first – --engine wins, otherwise it reads the uproject's EngineAssociation when that value is itself a path – then shells Engine/Build/BatchFiles/Build.bat with the target, config, platform, and -project=, captures stdout and stderr together, and runs the log through the parser. The header line counts what it found, then one row per diagnostic follows:
ubt build MyGameEditor Development Win64, 2 errors, 1 warningssource severity code file line message
compiler error C2065 Source/MyGame/Player.cpp 142 'Health' : undeclared identifier
linker error LNK2019 UnrealEditor-MyGame.lib unresolved external symbol
ubt error Expected MyGame.Build.cs to declare a moduleIf the engine cannot be resolved, or Build.bat is not where it should be, it says so and stops rather than failing obscurely. Pass --raw and it prints the unparsed log untouched.
Parse a captured log with no engine. You already have a build log saved from CI or an earlier run, and no engine on this machine. The parser does not need one:
nu ubt.nu parse build.log --errors-onlyThe header still counts every error and warning in the log – --errors-only narrows the returned table to the errors, it does not change the tally:
parsed build.log, 3 errors, 0 warningsThis captured-log path is the one you can fixture-test, since it reads a file and touches nothing else.
Distill a Saved/Logs file. The editor crashed and left a log behind, and you want the errors and ensures, not the ten thousand Display lines around them:
nu log-distill.nu read --errors-onlyWith no logfile named it globs Saved/Logs/*.log and picks the newest. It parses every line into category, verbosity, and message, prints a count by verbosity so you see the shape of the log, then returns the noteworthy rows – Error and Fatal here, or Error, Warning, Fatal, and the ensure/assert failures by default:
Saved/Logs/MyGame.log, 1423 log lines parsed
verbosity count
Display 1187
Warning 198
Error 34
Ensure/Assert 3
Fatal 1line category verbosity message
902 LogWindows Fatal Unhandled Exception: EXCEPTION_ACCESS_VIOLATION
874 LogTemp Ensure/Assert Ensure condition failed: Mesh != nullptrAdd --category LogTemp to filter to one log category, or --all to keep every parsed line rather than just the noteworthy ones.
An example outcome. Three commands, three tables. A link error buried deep in the build log is now a labelled row, and the single Fatal in a fourteen-hundred-line crash log is one line with its category and message – you never scrolled either file.
The Two Tables
The module has two parsers because a build log and a runtime log are different shapes, and each tool returns the table that fits its source.
| Tool | Reads | Recognizes | Returns |
|---|---|---|---|
ubt.nu | a UBT or build log | MSVC compiler lines, linker and MSB lines, UBT's own ERROR/WARNING lines | source, severity, code, file, line, message |
log-distill.nu | a Saved/Logs .log | [time][frame]Category: Verbosity: message, with the verbosity optional | line, category, verbosity, message |
The build side reads three line shapes. A compiler diagnostic – file(line): error CODE: message – becomes a compiler row with its file and line. A linker or MSB line – file : error LNK/MSB/C####: message, with fatal optional – becomes a linker row with no line number. UBT and UAT print their own ERROR: and WARNING: prefixed lines, and those become ubt rows carrying just the message. The whole table is sorted by severity, so the errors group above the warnings.
The log side reads one shape with a special case. Every UE log line is [timestamp][frame]LogCategory: Verbosity: message, and the verbosity is optional – when it is absent the line is graded Display. On top of that, any line containing Ensure condition failed or Assertion failed is tagged Ensure/Assert whatever its stated verbosity, because a failed ensure is exactly the kind of line a scroll would miss.
Key Files
ubt.nu
The build wrappers – four subcommands over the Unreal build and automation entry points. build shells Build.bat with the target, config, platform, and -project=, then parses the captured log into a diagnostic table; uat wraps RunUAT.bat and reports its diagnostics the same way; commandlet runs UnrealEditor-Cmd.exe <uproject> -run=<name>; and parse runs the parser over a captured log with no engine. Engine resolution takes --engine first and falls back to the uproject's EngineAssociation when that is a path – a version id or a guid association needs the registry, which is finn's to wire to his install layout. It degrades clean throughout: a missing engine, a missing Build.bat, or an absent log each prints a plain message and returns rather than erroring out. --errors-only narrows the table and --raw dumps the log unparsed.
log-distill.nu
The Saved/Logs distiller – one read subcommand that turns a finished UE log into category, verbosity, line, and message, so a log dive is a filter and not a scroll. By default it surfaces the noteworthy lines – Error, Warning, Fatal, and the ensure and assert failures – and prints a count by verbosity alongside so you see the log's shape at a glance. --errors-only narrows to Error and Fatal, --category LogTemp filters to a single log category, and --all keeps every parsed line. With no logfile named it reads the newest *.log under Saved/Logs, and it degrades clean when the log is missing.
Connects to
- Shares its diagnostic parser with cpp – an Unreal build is MSVC underneath, so ubt.nu's compiler and linker line shapes are the same ones cpp's
msbuild.nureads, minus the project-name capture and the--explainlesson lookup that pack adds on top. - Reads and writes memory – the pull rule is to read the
ue5lesson slice before working in Unreal, and a build or cook error you diagnose here is the kind of gotcha that gets captured back into that same domain. - Placed by the installer – it installs as the
ue5part, copying the whole pack into a target project's.claude/stack/ue5/, on demand and inert until you actually run one of the tools.