Pre-Release Quality Checklist

Code Quality

Zero Compiler Warnings

Fix all compiler warnings - they may be errors on other platforms or configurations.

🚨 Critical: Many marketplace rejections come from warnings. Build in Development AND Shipping configs.

Remove Debug Code

Remove or conditionally compile debug prints, visual debug draws, and test functions.

💡 Tip: Use WITH_EDITOR, UE_BUILD_SHIPPING macros. Remove all "Print String" nodes from blueprints.

Validate Blueprint References

Fix all "None" references and ensure no broken blueprint connections.

💡 Tip: Use "Reference Viewer" to find broken references. Test after packaging - some references break only in packaged builds.

Documentation

Create Comprehensive Documentation

Write clear, detailed documentation covering installation, setup, and usage.

🚨 Critical: Poor documentation = negative reviews. Include getting started guide, API reference, and examples.

Add Tooltips to All Public Variables

Every blueprint property and function should have a clear tooltip.

💡 Tip: Explain what it does, valid value ranges, and when to use it. Users read tooltips before documentation.

Include Example Project/Map

Provide working examples showing how to use every feature.

💡 Tip: Users learn by example. Include simple and advanced use cases. Comment your example blueprints.

Testing

Test in Fresh Project

Import your plugin/assets into a completely fresh UE5 project and verify everything works.

🚨 Critical: Don't assume users have the same plugins you do. Test with ONLY your plugin enabled.

Test Packaged Build

Package and run the project - some issues only appear in packaged builds.

💡 Tip: Test in both Development AND Shipping builds. Check for missing assets, broken paths, and runtime errors.

Test on Multiple Platforms

If claiming multi-platform support, test on each platform.

💡 Tip: Windows, Mac, Linux all have differences. Mobile has strict memory constraints. Test on real hardware.

Perform Stress Testing

Test with extreme values, edge cases, and rapid inputs.

💡 Tip: Spawn 1000 actors, set variables to -999999, rapidly toggle features. If it can crash, users will find it.

Performance

Profile Performance Impact

Measure CPU and GPU cost of your plugin/assets.

💡 Tip: Use "stat unit", "stat game", "stat gpu". Document performance cost in your description.

Check Memory Usage

Verify your assets/plugin don't have excessive memory footprint.

💡 Tip: Use "memreport" and Size Map. Check for memory leaks with repeated spawn/destroy cycles.

Asset Quality

Optimize Texture Sizes

Ensure all textures use appropriate resolutions and compression.

💡 Tip: Don't use 4K for everything. Check compression settings. Enable mipmaps. Remove unused textures.

Validate All Assets Import Correctly

Check that meshes, materials, and textures all load without errors.

💡 Tip: Look for red/pink materials, missing textures, incorrect normal maps. Check asset validation log.

Naming & Organization

Follow UE Naming Conventions

Use proper prefixes (BP_, M_, T_, SM_) and clear, descriptive names.

💡 Tip: See UE style guide. Consistency is key. Users appreciate well-organized content.

Organize Into Logical Folders

Create clear folder structure: Blueprints/, Materials/, Meshes/, etc.

💡 Tip: Make it easy for users to find assets. Group by feature or type. Include folder descriptions.

Marketplace Requirements (if applicable)

Verify UE Marketplace Guidelines

Review and comply with all Fab marketplace submission requirements.

🚨 Critical: Check minimum requirements, forbidden content, technical standards. Guidelines change - review before each submission.

Prepare Marketing Materials

Create compelling screenshots, videos, and description.

💡 Tip: High-quality visuals = more sales. Show features in action. Include comparison shots. 4K screenshots preferred.

🚀 Pre-Release Quality Checklist