Tiny Tool Development

// Editor Tools / Available on Fab

Code Copyright Editor

Project-wide source header and copyright notice maintenance for Unreal Engine codebases.

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

Make source-header compliance a scan, preview, report, and apply workflow instead of a release-week manual hunt.

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 Controlled source notice workflow for Unreal Editor projects

Scan first, rewrite selected, report for CI.

// THE PAIN

Before the plugin enters the chat.

Release week finds headers that never matched the template.

PAIN

The legal notice in Project Settings says one thing. Half the plugin headers say another. A third-party subtree was never supposed to be touched — but nobody flagged it before the scan.

Reviewing hundreds of files by hand does not survive crunch. One wrong header in a shipping module is enough to pause a compliance pass and send everyone back to diff view.

What that feels like

  • Copyright blocks drift file by file with no single source of truth.
  • Manual review cannot keep pace once the source tree grows past a few modules.
  • Release hygiene depends on whoever remembers to open the right folders.
// WHAT YOU GET

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

Scan the tree, preview every diff, and rewrite only the files you approve — including from CI.

GAIN

Code Copyright Editor starts with a project-wide scan and a readable report — then applies template-driven updates only where you explicitly allow it, including as a headless commandlet.

  • Project Settings notice and per-file headers driven from one template.
  • Scan results that separate OK, missing, and hands-off third-party files.
  • A commandlet so release hygiene runs before humans open the tree.

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

The codebase is classified against the configured notice.

The scanner separates OK, missing, outdated, skipped, third-party, and candidate files using settings-driven rules.

02 / Preview

Operators review changes before they touch source.

Reports and selected apply operations make file-level updates explicit instead of silently rewriting the tree.

03 / Apply

Approved changes update headers and project notice state.

Editor UI and commandlet paths support source-header maintenance in manual review and CI workflows.

// FIT

Who actually reaches for this.

Teams that want source notices, project settings metadata, release checks, and CI validation to stay consistent.

For teams that do not want to maintain source notices manually or miss them during releases.

// SURFACE

Where it lives in Unreal.

Editor UI, template configuration, source scanning, selected rewrite operations, reports, and commandlet checks.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

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

Header governance

The plugin makes legal text consistency a project workflow.

  • Scan C++ and source-like files across the project.
  • Compare current headers with the configured template.
  • Preserve exclusion rules for generated or third-party areas.
  • Update Project Settings notice from the same source of truth.

Controlled apply

Teams get a reviewable step before source files change.

  • Apply to selected files or the full codebase.
  • Write reports for review and release evidence.
  • Run headless checks through a commandlet.
  • Keep template behavior configurable instead of script-only.

Release hygiene

The product is strongest when used before packaging and publishing.

  • Detect drift before a marketplace or client delivery pass.
  • Make compliance work repeatable across plugin modules.
  • Catch files that never received the current notice.
  • Produce artifacts that a reviewer can read outside the editor.

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

Why it matters
Inspects the project tree for header status.
Operator result
A compliance inventory for review.
Change surface
Read-only scan.
// ACTION

apply_files

Why it matters
Updates approved files only.
Operator result
Selected headers match the configured template.
Change surface
Rewrites selected source files.
// ACTION

update_project_notice

Why it matters
Synchronizes the Project Settings notice.
Operator result
Project metadata and source headers can share language.
Change surface
Updates project notice settings.
// ACTION

write_reports

Why it matters
Exports the scan/apply evidence.
Operator result
Release reviewers get an external artifact.
Change surface
Writes report files.
// ACTION

apply_codebase

Why it matters
Applies the approved template broadly after scan review.
Operator result
Large source trees can be normalized without file-by-file editing.
Change surface
Rewrites matching source files across the configured codebase scope.
// ACTION

Commandlet check

Why it matters
Runs header validation outside the interactive editor.
Operator result
CI can fail release hygiene before a person opens the project.
Change surface
Read/check mode unless configured apply behavior is used.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Define the notice template and review project metadata.

02

Scan the source tree and inspect affected files before rewriting.

03

Apply selected changes or run commandlet checks in CI.

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

Surface Editor UI plus commandlet path
Operations Scan, apply selected, apply codebase, update notice, write reports
Scope Project source and plugin source hygiene
Control Template and exclusion settings
Release value Detects missing, outdated, skipped, and third-party-sensitive header states
Review model Scan/report can happen before any source rewrite

Outputs

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

  • Scan report

    File-level status for compliance review.

  • Updated headers

    Approved source files with the current notice block.

  • Project notice

    Project metadata aligned to the configured copyright text.

  • CI signal

    Commandlet-friendly status for release hygiene automation.

  • Apply report

    Evidence of which files were changed or left untouched.

Inspection basis

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

  • Tool surface

    scan_codebase, apply_codebase, apply_files, update_project_notice, and write_reports are exposed as explicit operations.

  • Editor settings

    Template, exclusion, and notice behavior are configurable instead of being hardcoded into a one-off script.

  • Commandlet

    The codebase includes headless execution so the value extends to CI and release workflows.

  • Notice service

    Project Settings metadata and per-file source headers are treated as related compliance surfaces.

Integrations

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

  • CI

    The commandlet path supports release checks outside a manual editor session.

  • Unreal Capability Mesh

    Scan and report routes can be exposed as declared editor jobs.

  • Marketplace release flow

    Reports support publish-readiness evidence.

  • Source review

    Reports give reviewers a narrow artifact instead of asking them to inspect every file manually.

Safety model

The boundaries that make the tool understandable before automation enters.

  • Previewable changes

    The workflow separates scan/report from apply.

  • Exclusions

    Third-party and generated areas can remain hands-off.

  • Selected apply

    Operators can update approved files without rewriting everything.

  • Template source of truth

    The applied notice is driven from settings rather than improvised per module.

Not for

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

  • Teams seeking legal advice instead of a maintenance tool.

  • Projects where source files should never be modified by editor utilities.

  • Repositories that cannot define trustworthy third-party and generated-code exclusions.

// 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 CodeCopyrightEditor.uplugin VersionName 1.0.3 / Version 3
Primary surface Editor UI, template configuration, source scanning, selected rewrite operations, reports, and commandlet checks.
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 Scan-first Unreal editor, commandlet, and optional route surface for controlled source notice review, selected rewrites, project notice updates, and evidence reports.
Primary workflow Configure owner, license, templates, and scan scope; scan without mutation; review classifications; apply selected safe changes; and write reports when needed.

// NOTES

Practical boundaries.

The tool assists with consistent metadata, but it is not legal advice.

Fab handles purchase, license, account, payment, and download context.

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

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
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: Async Spline Builder Next: Lightweight Editor Mode