Skip to content
Jigwright

Editor state

6 tools for working with editor state.

Split by whether they change your project. Read-only tools are always safe to try.

Reading

  • Editor State — What the editor is doing right now: which map is open, whether PIE is running, how many shaders are still compiling, and how much is unsaved. Check this when results look stale - shaders still compiling explains a lot of 'it did not work' reports.
  • Get Log — Recent Unreal output log lines, newest last. Most engine failures explain themselves here and nowhere else, so this is usually the fastest way to find out why something did not work. Filter by verbosity, category, or substring.
  • List Dirty Packages — Packages with unsaved changes, and whether each can actually be written. Use before saving to see what would be affected and what is blocked.
  • Ping — Liveness check. Returns the server version and whether the editor is ticking.

Writing

  • Redo — Redo the most recently undone transaction.
  • Undo — Undo the most recent transaction, exactly as Ctrl+Z would. Every HullForge mutation is transaction-wrapped specifically so this works. Reports what was undone.