Fab Blueprint Product Submission Checklist

🎬 Demo & Preview Requirements

Blueprint products MUST demonstrate functionality. This is a critical requirement that will reject your submission if missed.

Demo Project OR Video URL Required

Blueprint-based products MUST include a downloadable demo project OR a video URL in the Long Description.

🚨 Critical: This is a hard requirement. Without demonstration, your submission WILL be rejected.

Video Shows All Major Features

If using video, demonstrate all advertised functionality in action.

💡 Tip: Show Blueprint nodes in use, runtime behavior, and setup process. 2-5 minutes is ideal.

Demo Project is Standalone

Demo projects should work immediately without requiring additional setup or plugins.

💡 Tip: Include all dependencies. Test download and open from scratch.

📐 Blueprint Quality

Clean, readable Blueprints are essential for user satisfaction and support reduction.

No Errors or Consequential Warnings

Blueprints must generate no errors or significant warnings when compiled.

🚨 Critical: Check the Compiler Results panel. Fix all red and yellow issues.

No Loose/Disconnected Nodes

Blueprints must have no loose nodes unless commented for example/tutorial purposes.

🚨 Critical: Delete unused nodes. If keeping for documentation, add clear comments explaining why.

Neat Layout

Blueprints must be neatly laid out with organized node placement.

🚨 Critical: Use alignment tools. Keep related logic grouped. Avoid spaghetti connections.

Use Functions to Organize Logic

Make reasonable use of functions to structure complex logic.

💡 Tip: If an Event Graph is scrolling for pages, break it into functions. Makes reading and debugging easier.

Descriptive Names for Everything

Functions, variables, and events must have names reflecting their purpose.

💡 Tip: "UpdateHealthBar" not "Function1". "PlayerHealth" not "Variable2". Be explicit.

Comments on Complex Sections

Add comment boxes explaining non-obvious logic flows.

💡 Tip: Comment why, not what. "// Delay for network sync" is better than "// Wait 0.1 seconds".

Category Organization for Exposed Variables

Group related variables using Category metadata.

💡 Tip: "Movement|Speed", "Combat|Damage" - helps users find settings in Details panel.

Tooltips on Public Variables

Every exposed Blueprint property should have a clear tooltip.

💡 Tip: Explain what it does, valid ranges, and effects. Users read tooltips before documentation.

📁 Project Structure

Content-only projects (including Blueprint packs) have specific folder requirements.

No Local Folders in Submission

Remove Binaries, Build, Intermediate, Saved, and Plugins folders before zipping.

MyBlueprintPack/ ├── Config/ ├── Content/ │ └── MyBlueprintPack/ │ ├── Blueprints/ │ ├── UI/ │ ├── Data/ │ └── Maps/ └── MyBlueprintPack.uproject

🚨 Critical: Content-only projects must not have a Plugins folder.

Single Top-Level Content Folder

All assets in ONE folder under Content. No other files directly under Content.

🚨 Critical: This prevents migration conflicts when users import to their projects.

No Level Blueprints for Asset Packs

Asset Packs (Distribution Method) must not include Level Blueprints.

🚨 Critical: Level Blueprints can't migrate to other projects. Use Actor Blueprints or GameMode instead.

No Mandatory Config Files for Asset Packs

Asset Packs must not require custom .ini configuration files.

💡 Tip: If your system needs configuration, make it Blueprint-editable on an Actor or GameMode.

File Paths Under 140 Characters

All asset paths (from Content folder) must be 140 characters or less.

💡 Tip: Keep folder and file names concise. Deep nesting adds up quickly.

English Alphanumeric Names Only

Folder and file names must use only English letters, numbers, and underscores.

💡 Tip: No spaces, special characters, or non-ASCII characters in asset names.

Redirectors Cleaned Up

Fix all asset redirectors before submission.

💡 Tip: Right-click Content folder → Fix Up Redirectors in Folder.

🔗 Dependencies

Blueprint products must work without unexpected dependencies.

Dependencies Clearly Documented

All required dependencies must be stated in the product description.

🚨 Critical: If you use Enhanced Input, Paper2D, or any plugin - list it explicitly.

Dependencies Available on Fab

Required external dependencies must be available through Fab.

🚨 Critical: Don't depend on other marketplace plugins users need to purchase separately.

Unused Plugin Dependencies Disabled

Unused engine plugin dependencies in .uproject must have "Enabled": false.

💡 Tip: Check .uproject file. Remove or disable plugins you don't actually need.

Experimental/Beta Features Documented

If using experimental or beta engine features, clearly state this in the description.

💡 Tip: Warn users about potential instability or future breaking changes.

🗺️ Demo Map

Every Blueprint product needs a working demonstration.

Demonstration Map Included

Include a map that demonstrates all major functionality.

🚨 Critical: Users need to see it working immediately, not figure out setup on their own.

No Errors on Map Load

Map must load and run PIE without errors or consequential warnings.

🚨 Critical: Test in fresh project after import. Check Output Log for any red/yellow messages.

Lighting Built

Demo maps must have lighting built (no "Preview" watermarks).

💡 Tip: Build → Build Lighting Only. Professional appearance matters.

Clear Usage Instructions in Map

Include on-screen text or widgets explaining how to use/test the system.

💡 Tip: "Press E to interact" type prompts. Make it obvious what to do.

📚 Documentation

Blueprint products require setup knowledge. Documentation is essential.

Documentation Provided or Linked

Products requiring setup must have or link to free documentation.

🚨 Critical: Web guide, PDF, video, or in-editor tutorial. Must be in English.

Getting Started Guide

Include step-by-step instructions for initial setup.

💡 Tip: From import to working feature in clear numbered steps.

API/Interface Documentation

Document all public functions, events, and variables users can interact with.

💡 Tip: What it does, expected parameters, return values, example usage.

Example Use Cases

Show common implementation patterns and integrations.

💡 Tip: Users learn by example. Cover basic AND advanced scenarios.

🎮 Engine Version Support

Content-only projects have simpler version management than code plugins.

Latest Engine Version on Initial Submit

New products must support the latest version of Unreal Engine.

🚨 Critical: Check current UE version before submission.

Support at Least One of Latest Three Versions

Published products must maintain support for one of the three latest engine versions.

💡 Tip: For content-only, you can add new engine versions to existing Project Version.

Works in Binary Engine Builds

Content must function in standard launcher-installed Unreal Engine.

💡 Tip: Don't rely on source-build-only features.

📝 Product Page

Marketing and metadata requirements.

English with Proper Grammar

All text must be in English with correct spelling and grammar.

💡 Tip: First impressions matter. Proofread everything.

Technical Info Complete

Fill all relevant Technical Information fields including dependencies.

💡 Tip: Network Replicated? Input required? List all technical specifics.

Accurate Tags and Category

Use relevant tags. Category must match product functionality.

💡 Tip: "Blueprints", "Systems", appropriate genre/type tags.

Accurate Screenshots

Show Blueprint graphs, editor setup, and runtime behavior.

💡 Tip: Include both in-editor and in-game screenshots. Show the Blueprints themselves.

AI Usage Disclosed

Disclose if generative AI was used during creation.

💡 Tip: Check "Created with AI" field if AI assisted with code, assets, or documentation.

🧪 Testing

Thorough testing prevents negative reviews and support burden.

Test in Fresh Project

Import to a completely new UE5 project and verify everything works.

🚨 Critical: Your dev project has context. Fresh project reveals missing dependencies.

Test Packaged Build

Package the project and verify functionality in standalone build.

💡 Tip: Editor-only features won't work in packaged games. Test both Development and Shipping.

📘 Fab Blueprint Product Checklist