Tiny Tool Development

// Editor Tools / Available on Fab

LogLevelEditor

A focused editor dashboard for discovering Unreal log categories and changing verbosity.

Finds Unreal log categories and changes verbosity levels in a focused surface.

Make Unreal log categories discoverable and adjustable from the editor so debugging gets signal without config spelunking.

Show on Fab Read GitHub documentation Back to catalogue
product slidesCommitted walkthrough media; documentation carries the detailed operating context.

// PRODUCT WALKTHROUGH

Visual orientation backed by the product facts below.

Use the gallery as quick orientation, then inspect mechanics, actions, outputs, integrations, and boundaries.

Overview Turn Unreal logging noise into readable debugging signal

Find the channel. Set the level. Stay in flow.

// THE PAIN

Before the plugin enters the chat.

The one log line you need is buried under fifty you do not.

PAIN

You know the answer is in the log — but not which category, and not at which verbosity. Opening Default.ini mid-debug is slow, easy to typo, and risky on a shared branch.

Turn LogTemp to Verbose and the output window becomes unreadable. Mute too much and the clue never appears. Every detour out of the editor costs focus.

What that feels like

  • Relevant categories are hard to discover without config spelunking.
  • Session tweaks and project-wide logging policy get mixed up under pressure.
  • Debug loops stall on noise before they reach the one useful line.
// WHAT YOU GET

After — in the editor, not in a slide deck.

Find the category, set verbosity in a dashboard, and stay inside the session you are debugging.

GAIN

LogLevelEditor puts category search and verbosity control in a dedicated editor dashboard — so you narrow the signal without rewriting project logging policy.

  • Searchable categories in-editor instead of config archaeology.
  • Per-session verbosity without rewriting project logging policy.
  • Faster narrowing when a bug only shows up in one subsystem.

// HOW IT WORKS

The product architecture, inspected from the plugin surface.

These are the moving parts I would place on the page so buyers can understand what they are actually getting beyond the slide narrative.

01 / Discover

The scanner finds available log categories.

Source scanning and category discovery build a readable inventory of log categories relevant to the project.

02 / Adjust

Verbosity changes happen through a focused dashboard.

Operators can query a category, set verbosity, hide noisy categories, and clear hidden state without editing config files mid-debug.

03 / Persist

Overrides can be backed by project assets/settings.

DataAsset-backed overrides and settings make logging choices more deliberate than ad-hoc Output Log commands.

// FIT

Who actually reaches for this.

Debugging sessions where teams need more precise logs without digging through configuration files.

Helps debugging when logs need to become more precise without hunting through configuration files.

// SURFACE

Where it lives in Unreal.

Log category discovery, verbosity controls, settings reference, user workflow, FAQ, and troubleshooting documentation.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

Grouped from plugin modules, public APIs, automation hooks, and documented workflow surfaces.

Category discovery

The first value is finding the right category quickly.

  • Scan available categories from project and engine context.
  • Search or query specific categories.
  • Separate relevant logs from Output Log noise.
  • Use source scanning to reveal categories that are not obvious from docs.

Verbosity control

Debug loops need targeted signal, not a global wall of Verbose output.

  • Set category verbosity from the editor dashboard.
  • Hide categories that overwhelm the current investigation.
  • Clear hidden category state when the session changes.
  • Avoid typo-prone config edits during active debugging.

Team debugging hygiene

The product gives teams a shared place to reason about temporary log state.

  • Keep session-level investigation separate from project logging policy.
  • Make category status visible enough for handoff.
  • Use a focused tool instead of scattered console history.
  • Document baseline decisions after the bug is understood.

// OPERATOR TOOLS

Concrete actions, expected result, and mutation boundary.

This is the part that keeps product marketing honest: buyers can see which buttons, APIs, or MCP tools matter and what they change.

// ACTION

scan_categories

Why it matters
Builds the category inventory.
Operator result
Debuggers can see what can be controlled.
Change surface
Refreshes scanner state.
// ACTION

query_category

Why it matters
Shows current state for one category.
Operator result
Operators avoid changing the wrong target.
Change surface
Read-only.
// ACTION

set_category_verbosity

Why it matters
Changes the logging level for a category.
Operator result
The current debug loop gets more or less signal.
Change surface
Updates verbosity override/session state.
// ACTION

clear_hidden_categories

Why it matters
Removes dashboard hiding filters.
Operator result
The category view returns to a clean baseline.
Change surface
Updates hidden category state.
// ACTION

hide_category

Why it matters
Removes irrelevant categories from the current dashboard view.
Operator result
The investigation view stays focused without deleting the category itself.
Change surface
Updates dashboard visibility/filter state.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Open the dashboard and discover available log categories.

02

Adjust verbosity for the categories relevant to the current issue.

03

Reset or document the chosen logging baseline after debugging.

// PROOF AND BOUNDARIES

Signals that make the product specific, plus the limits worth saying out loud.

Each card turns implementation facts into buyer-facing proof without pretending the tool solves the wrong problem.

Tools scan, query, set verbosity, hide, clear hidden
Persistence DataAsset-backed override model
Audience Programmers, QA, technical artists, support sessions
Boundary Log control, not full observability
Scanner value Source/category discovery avoids guessing category names during debugging
Session value Noise can be narrowed without editing Default.ini mid-issue

Outputs

What the plugin leaves behind when the workflow is doing useful work.

  • Category inventory

    A browsable map of logging categories.

  • Verbosity overrides

    Targeted debug levels for current investigation.

  • Hidden category state

    Noise filters for dashboard readability.

  • Category query result

    Focused status for one category before it is changed.

Inspection basis

The concrete code, API, and tool surfaces used to shape this product page.

  • MCP tools

    scan_categories, query_category, set_category_verbosity, hide_category, and clear_hidden_categories are the concrete control points.

  • Scanner

    A source scanner and category inventory explain why this is more than a wrapper around console commands.

  • Settings model

    DataAsset-backed overrides make debug choices more explicit than ad-hoc output log history.

Integrations

Where the product connects without losing ownership of its own domain.

  • Unreal Capability Mesh

    Category actions can become routeable diagnostics controls.

  • Unified MCP Server

    Local tools can query or adjust logging through a shared endpoint.

  • QA/support workflows

    Teams can ask for precise log changes without sending config instructions.

  • Debug handoff

    A category inventory and explicit verbosity state make support instructions easier to reproduce.

Safety model

The boundaries that make the tool understandable before automation enters.

  • Targeted category changes

    Operators change one category instead of globally increasing noise.

  • Queryable state

    Current category settings can be inspected before adjustment.

  • Clear filters

    Hidden categories can be reset when the investigation ends.

  • Dashboard hiding is reversible

    Hidden categories are a view concern, not deletion or permanent policy.

Not for

The cases where the product promise would be the wrong expectation.

  • Teams looking for telemetry dashboards, metrics, or trace analysis.

  • Projects where logging policy must only be changed through source review.

  • Incidents that require distributed tracing rather than local Unreal log category control.

// PRODUCT MEDIA

Tutorial and platform embeds stay attached to product context.

YouTube, Discord, LinkedIn, and Fab widgets are reserved for product presentation, explanation, support context, or tutorials. No third-party widget loads automatically.

Tutorial video

YouTube

Product walkthroughs, setup explanations, and tutorial material.

Embed source pending. No third-party widget is loaded here.

Open platform
Primary support context

Discord

Discord-first product support, quick questions, setup discussion, and community context.

Embed source pending. No third-party widget is loaded here.

Open platform
Professional context

LinkedIn

Company background, provider identity, project credibility, and listing context.

Embed source pending. No third-party widget is loaded here.

Open platform
Marketplace context

Fab

Product listing context, license details, purchase route, and marketplace availability.

Embed source pending. No third-party widget is loaded here.

Open platform

// INFORMATION

All essential product signals in one place.

Status Available on Fab
Category Editor Tools
Unreal Engine 5.4; current descriptor/build line UE 5.8
Source state LogLevelEditor.uplugin VersionName 1.1.5 / Version 4
Primary surface Log category discovery, verbosity controls, settings reference, user workflow, FAQ, and troubleshooting documentation.
Marketplace Fab listing available
Direct sales None on this website
Support route Discord first; product context lives on this page
Listing context Fab for marketplace, LinkedIn for public provider identity
Fact surface 3 functions / 3 settings / 3 failure modes / 1 bridge
Boundary Standalone editor surface for discovering Unreal log categories, inspecting verbosity, filtering noisy channels, and persisting intentional overrides.
Primary workflow Scan source roots for log categories, review runtime/default verbosity, set intentional overrides, and persist selected changes in a DataAsset.

// NOTES

Practical boundaries.

The tool is focused on editor-side logging control and does not replace project-wide observability.

Fab handles marketplace availability and purchase details.

// LEGAL / PRIVACY

Static information page.

Purchases, downloads, marketplace accounts, and platform-specific license details are handled outside this website. Product or tutorial widgets are loaded only after activation, where configured.

Provider details are listed in the legal notice. The current site template does not set first-party cookies and does not load analytics scripts.

Legal Notice Privacy Policy

// RESOURCES

Open the channel that matches the next question.

Fab listing

Listing, license, purchase, account, and download context are handled by Fab.

Open

GitHub documentation

Manuals, quickstarts, settings references, troubleshooting, technical notes, and release material live in GitHub.

Open

Discord support (primary)

Start quick questions, setup help, support context, and product-fit discussion on Discord.

Open

Plugin support email

Formal plugin support requests can be sent to the dedicated support mailbox.

Open

LinkedIn company context

Company background, public provider identity, and listing context are available on LinkedIn; support still starts on Discord.

Open

// RELATED

Nearby tools in the catalogue.

Editor Tools

Code Copyright Editor

Keeps copyright headers, project notices, metadata, and CI checks consistent.

View page
Editor Tools

Lightweight Editor Mode

Reduces Unreal Editor viewport and rendering cost through reversible profiles.

View page
Editor Tools

Naming Convention Utility

Previews, scores, and applies Unreal asset naming rules through a guarded Naming Workbench.

View page

// TOOL NAVIGATION

Continue through the catalogue.

Each tool page keeps the product overview here and routes deep technical material to GitHub.

Previous: Lightweight Editor Mode Next: Naming Convention Utility