Tiny Tool Development

// Scene Tools / Design / emerging target architecture

Game Featured Classes

A lightweight runtime shell for featured gameplay classes and GameFeature workflows.

Target architecture for a premium GameFeature Workbench with feature-class data assets, world-scoped actions, runtime registry resolution, discovery graph visualization, descriptor governance, guided repair, audit reports, sample fixtures, and optional Tiny Tools automation.

Game Featured Classes system overview
system artCanonical schematic media; status, proof, and roadmap remain data-driven in the page.
// THE PAIN

Before the plugin enters the chat.

Featured gameplay classes can become hard to track when the runtime shell, package docs, and feature rules drift apart.

PAIN

Game Featured Classes keeps the shell narrow so teams can register and reason about featured classes without turning the package into a full workbench. The public landing page explains the target architecture and routes buyers to the shipped docs instead of overpromising missing tooling.

What that feels like

  • Runtime shell behavior is easy to misunderstand without a clear landing page.
  • Feature-class documentation gets scattered across package files and ad hoc notes.
  • Target architecture can be mistaken for already-shipped workbench tooling.
// WHAT YOU GET

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

Give buyers one clear place to understand the shell, the docs, and the current package boundary.

GAIN

The landing page describes the module shell, the descriptor boundary, the shipped documentation set, and the optional future workbench direction without turning those targets into requirements.

  • Runtime module shell for featured gameplay classes.
  • Clear package boundary between shipped shell behavior and future workbench targets.
  • Online docs plus the six packaged buyer-doc files inside the plugin folder.
  • A concise routing surface for buyers who need the current state before they install.

// FIT

Who actually reaches for this.

Teams that need a small, explicit featured-class shell and want the current package boundary explained before they install.

GFC keeps Unreal GameFeatures and Experience systems as the activation/orchestration authority while adding a premium workbench around them. Feature authors declare classes and requirements; consumers resolve by feature id, role, interface, or fallback policy; maintainers scan a graph of descriptors, Experiences, actions, classes, consumers, blockers, and build decisions; validators inspect descriptors, action data, soft references, and build-target compatibility; repair services preview, stage, apply approved fixes, verify, audit, rollback/undo supported changes, and write local proof artifacts.

// SURFACE

Where it lives in Unreal.

Runtime module boundary, descriptor metadata, packaged docs, and the online overview surface.

// CAPABILITY MAP

Feature groups with the value of each part made explicit.

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

Keeps the shell deliberately narrow instead of masquerading as a full workbench.

Explains the current package boundary and the target architecture separately.

Points directly to the online docs and shipped buyer-doc files.

// TYPICAL FLOW

From inspection to use without losing the product boundary.

01

Read the online landing page to understand what is shipped now.

02

Use the packaged docs inside the plugin folder for setup and troubleshooting.

03

Treat workbench-style features as target architecture until they are explicitly shipped.

// 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 Design / emerging target architecture
Category Scene Tools
Unreal Engine 5.4.0
Source state Current package shell implemented; premium GameFeature Workbench target specified only.
Primary surface Runtime module boundary, descriptor metadata, packaged docs, and the online overview surface.
Marketplace No product checkout linked
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 13 functions / 9 settings / 6 failure modes / 4 bridges
Boundary GFC is a premium GameFeature Workbench that makes Unreal GameFeatures discoverable, authorable, validatable, visualizable, repairable, automatable, and safe to consume through declarative featured class contracts.
Primary workflow Scan the feature graph, inspect descriptor/action/class findings, validate definitions and feature sets, author or repair featured class definitions through guided UI, register classes through standard GameFeature actions, resolve them through the runtime registry, and export graph/validation/repair proof.
Publication boundary Internal architecture projection; not buyer-facing until runtime, tests, and curated package docs exist.
Proof state Current package shell implemented; premium GameFeature Workbench target specified only.

// NOTES

Practical boundaries.

The public page is an overview and routing surface, not a verbatim copy of shipped docs.

The package docs remain inside Documentation/ in the plugin folder.

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

// RESOURCES

Open the channel that matches the next question.

Fab seller profile

No product-specific Fab listing is linked yet. The public seller profile remains available.

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.

// TOOL NAVIGATION

Continue through the catalogue.

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