Tiny Tool Development

// Editor Tools / Available on Fab

Naming Convention Utility

A preview-first Naming Workbench for Unreal asset profiles, compliance, selective apply, and audit reports.

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

Turn naming policy into profile-aware, previewed Unreal-safe asset rename batches through a dockable Naming Workbench with compliance, plan hashes, selective apply, and audit reports.

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 Naming Workbench for profile-aware Unreal asset cleanup

Scan folders, compare profiles, score compliance, and apply reviewed rows.

// THE PAIN

Before the plugin enters the chat.

Everyone agrees on SM_ until a bulk rename touches real project references.

PAIN

The style guide is clear on prefixes, suffixes, folder rules, and exception handling. The Content Browser tells a different story: legacy names, duplicate targets, profile exceptions, and texture decisions spread across real project folders.

A bulk rename without preview is how pipelines learn fear. One collision, stale plan, or broken reference can cost more than the original cleanup ever would have saved.

What that feels like

  • Naming drift spreads silently until someone opens the wrong folder on onboarding day.
  • Manual renames do not scale past a handful of assets.
  • There is no shared compliance score, profile diff, or reviewed plan hash before Unreal's rename workflow runs.
// WHAT YOU GET

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

Scan in a dockable workbench, choose a profile, review compliance, then apply only the accepted plan.

GAIN

Naming Convention Utility turns naming policy into selectable profiles, recursive scans, compliance summaries, canonical plan hashes, audit reports, and guarded selective apply.

  • Dockable Naming Workbench with folder scope, filters, row details, compliance, and report export.
  • Built-in Epic Recommended and Tiny Legacy profiles plus editable project_custom rules.
  • Collision checks, duplicate-target skips, canonical plan hashes, and selected-row apply.
  • Rules from DataAssets, DataTables, CSV, or JSON references without a one-off script.

// 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 / Profile

Naming profiles define policy before folders are scanned.

Built-in Epic Recommended and Tiny Legacy profiles can be compared, copied, and extended through project_custom rules.

02 / Rules

Convention data defines prefixes, suffixes, and folder expectations.

Rules can come from DataAssets, DataTables, CSV, or JSON references so naming policy becomes project-owned data.

03 / Preview

Folders are scanned before Unreal renames anything.

The Naming Workbench validates planned names, detects collisions and duplicate targets, reports compliance, and produces a canonical plan hash.

04 / Apply

Approved rows use Unreal asset workflows.

Apply operations can target selected rows and verify the plan hash before mutating assets through Unreal's rename path.

05 / Audit

Reports keep cleanup evidence reviewable.

JSON and Markdown reports capture profile, scope, compliance, skips, plan hash, and apply results for team review.

// FIT

Who actually reaches for this.

Projects where asset names are pipeline signals and renaming should happen through profile-aware, previewed, reportable Unreal-safe operations.

For projects where asset names are pipeline signals and folder cleanup needs reviewable policy, profile choice, selective apply, and audit evidence.

// SURFACE

Where it lives in Unreal.

Naming Workbench, built-in profiles, project_custom rules, folder scans, compliance preview, profile diff, plan-hash guard, selective rename, settings reference, audit reports, FAQ, and troubleshooting.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

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

Workbench review

The tool moves naming cleanup into a dockable review surface.

  • Choose folders, run recursive scans, and filter preview rows.
  • Inspect row details, proposed names, skip reasons, and validation state.
  • Review compliance before mutation.
  • Export preview and apply reports for leads or automation.

Profile governance

Naming standards remain explicit project policy instead of one-off script behavior.

  • Use built-in Epic Recommended and Tiny Legacy profiles.
  • Copy a built-in profile into editable project_custom rules.
  • Diff profiles before changing the active standard.
  • Import rule data from DataAssets, DataTables, CSV, or JSON references.

Guarded apply and audit

The business value is confidence before large asset cleanup.

  • Detect collisions, existing targets, duplicate targets, invalid names, and unsupported classes.
  • Use canonical plan hashes to protect against stale previews.
  • Apply selected accepted rows instead of the whole scan by default.
  • Fix redirectors after rename when the setting is enabled.

Rule maintenance

Once a preview is clean, the plugin keeps cleanup repeatable.

  • Populate default convention data.
  • Convert DataTable rules to DataAssets.
  • Clear and rebuild convention sets when policy changes.
  • Keep naming cleanup tied to project policy assets.

// 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

preview_folders

Why it matters
Scans selected folder trees against the chosen profile and convention rules.
Operator result
A compliance summary, rename plan, skip reasons, and canonical plan hash.
Change surface
Read-only preview.
// ACTION

apply_folders

Why it matters
Executes approved rename plans, optionally limited to selected target paths and guarded by a plan hash.
Operator result
Assets follow the configured naming convention and apply reports are written.
Change surface
Renames assets through Unreal workflows.
// ACTION

rules_diff

Why it matters
Compares naming profiles or rule sets before policy changes are accepted.
Operator result
Teams can review policy drift before it affects rename plans.
Change surface
Read-only comparison.
// ACTION

convert_datatable_to_data_asset

Why it matters
Turns tabular naming rules into convention assets.
Operator result
Policy can move from spreadsheet-like data into project assets.
Change surface
Creates or updates convention assets.
// ACTION

populate_default_conventions

Why it matters
Seeds a baseline naming rule set.
Operator result
Teams start from known Unreal naming patterns.
Change surface
Writes convention data.
// ACTION

clear_conventions

Why it matters
Removes the current convention set when policy needs to be rebuilt.
Operator result
Teams can reset stale rules before importing or populating a new baseline.
Change surface
Updates convention data.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Open the Naming Workbench, choose a profile, and scan selected Content Browser folders.

02

Review compliance, collisions, skipped targets, row details, and the canonical plan hash.

03

Apply accepted rows through Unreal asset rename workflows and export JSON or Markdown audit reports.

// 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.

Module type Editor module
Dependencies AssetTools, AssetRegistry, ContentBrowser, EditorScriptingUtilities, Niagara, ToolMenus
Editor surface Dockable Naming Workbench
Profiles epic_recommended, tiny_legacy, and editable project_custom
Rule forms DataAssets, DataTables, CSV, and JSON references
Controls Preview, profile diff, apply selected, convert, populate, clear, export reports
Safety Compliance, collisions, duplicate-target skips, canonical plan hash, selected-row apply
Rename path Unreal AssetTools rename workflow with optional redirector cleanup enabled by default
Reports JSON and Markdown audit outputs

Outputs

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

  • Rename preview

    A reviewable list of current names, proposed names, compliance, skips, and warnings.

  • Plan hash

    A canonical hash that ties apply requests to the reviewed preview.

  • Convention assets

    Project-local naming policy objects.

  • Profile diffs

    Reviewable changes between built-in and project-custom naming policy.

  • Renamed assets

    Approved assets updated through Unreal-safe operations.

  • Audit reports

    JSON and Markdown evidence for preview and apply runs.

  • Validation exceptions

    Conflicts, invalid targets, duplicate targets, and unsupported classes that need human policy decisions.

Inspection basis

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

  • Tool surface

    preview_folders, apply_folders, rules_diff, convert_datatable_to_data_asset, populate_default_conventions, and clear_conventions are exposed.

  • Workbench code

    The inspected implementation includes a dockable Naming Workbench with profile selection, filtering, row details, compliance, and report export.

  • Dependencies

    AssetTools, ContentBrowser, EditorScriptingUtilities, and Niagara support Content Browser and Unreal asset workflows rather than filesystem-only scripts.

  • Rule model

    Convention DataAssets, DataTable import paths, and profile data make naming policy project-owned data.

  • Safety review

    Preview, collision validation, duplicate-target skips, selected-row apply, and plan hashes are central because asset renames can affect references.

Integrations

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

  • Content Browser

    The workflow targets asset organization where artists and technical artists work.

  • Unreal Capability Mesh

    Preview, profile diff, and apply steps can be exposed as governed routes.

  • Unified MCP Server

    MCP tools can expose the same preview/apply/report behavior to local automation.

  • Team style guides

    Existing naming standards become executable project data.

  • CSV/DataTable/JSON policy sources

    Existing rule lists can be moved toward convention assets instead of being retyped.

Safety model

The boundaries that make the tool understandable before automation enters.

  • Preview gate

    Apply is separated from inspection and tied to the reviewed plan hash.

  • Compliance review

    Profile-aware scores show naming health before mutation.

  • Collision detection

    Conflicting, duplicate, invalid, existing, and unsupported targets are surfaced before mutation.

  • Selective apply

    Accepted rows can be applied without forcing every preview row into the same rename batch.

  • Unreal rename path

    Assets are renamed through AssetTools, not moved by raw filesystem operations.

  • Reset path

    Convention sets can be cleared and rebuilt when the naming policy changes.

Not for

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

  • Teams with no shared naming policy.

  • Filesystem-only cleanup outside Unreal asset management.

  • Bulk rename work where collision review is intentionally skipped.

// 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 NamingConventionUtility.uplugin VersionName 1.1.1 / Version 4
Primary surface Naming Workbench, built-in profiles, project_custom rules, folder scans, compliance preview, profile diff, plan-hash guard, selective rename, settings reference, audit reports, FAQ, and troubleshooting.
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 4 functions / 3 profiles / 4 capabilities / 3 settings / 3 failure modes / 1 bridge
Boundary Preview-first Unreal asset naming workbench with built-in profiles, compliance summaries, plan hashes, audit reports, and guarded AssetTools rename workflows.
Primary workflow Define naming rules in a DataAsset or imported DataTable, open the Naming Workbench or Content Browser action, preview a rename plan, inspect compliance and skip reasons, and apply only accepted Unreal-safe renames.

// NOTES

Practical boundaries.

The tool helps enforce project naming conventions, but naming policy still belongs to the project team.

Fab contains listing, license, and checkout 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

LogLevelEditor

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

View page

// TOOL NAVIGATION

Continue through the catalogue.

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

Previous: LogLevelEditor Next: Performance Preset Wizard