Deployment

Use this checklist before releasing your game to ensure a smooth deployment.

Pre-Build

React UI

• Run cd menus && yarn release successfully (NOT yarn build for production)

• No TypeScript errors in build output

• menus/build/ and menus/shared/types.js exist

• Test UI in development mode first using yarn build

Plugin & Overrides

• js/plugins/rpgreact/overrides.manifest.json is correct

• All override files listed in manifest exist

• Export function names match manifest entries

• Test overrides work in RPG Maker MZ playtest

Game Data

• All maps tested (especially battleback references)

• All battles tested

• Save/Load tested

• All menu screens accessible

• All plugin commands tested

Assets

• Remove unused default assets manually (before pruning)

• Optimize large images/audio if needed

• Test with -PurgeAssets flag on a copy first

• Verify critical assets aren't accidentally referenced

Build Process

Package Build

# Test without pruning first
./build-package.ps1 -Target windows -OutDir dist\test-build

# Test the build thoroughly

# Then build with pruning for release
./build-package.ps1 -Target windows -PurgeAssets -OutDir dist\release-build

• Build completes without errors

• Check console for pruning statistics

• Review asset-manifest.txt for important assets

• Verify package size is reasonable

Post-Build Validation

• Game.exe (or .app) exists in output

• index.html exists

• menus/build/ exists and contains assets

• js/plugins/RPGReact.js is minified

• js/plugins/rpgreact/RPGReact.overrides.min.js exists

• Individual override source files removed

Testing

Functional Testing

• Launch game from package directory

• New Game starts correctly

• Title screen Continue button disabled when no saves

• Save/Load works

• All maps load correctly

• All battles work (check battlebacks)

• Menu screens work

• Shop system works (buy/sell)

• Level-ups display correctly

• Victory screen shows rewards properly

• Game Over screen works

Asset Testing

• No missing images (check console for 404s)

• Battlebacks display in all battles

• Character sprites display

• Enemy sprites display

• Icons display in menus

• Audio plays correctly

• Effekseer effects work

Performance Testing

• Game runs smoothly (60 FPS)

• No memory leaks during extended play

• Battle transitions are smooth

• Menu transitions are smooth

• Load times are acceptable

Cross-Platform (if applicable)

• Test on Windows 10 and 11

• Test on Mac (if targeting macOS)

• Test web build in multiple browsers

• Test on minimum spec hardware

Final Steps

Documentation

• Update version number in package.json

• Update CHANGELOG or release notes

• Include README in distribution

• Include license file

Distribution Prep

• Compress package into .zip (if distributing as archive)

• Test extracted archive on clean machine

• Verify antivirus doesn't flag executable

• Upload to distribution platform (Steam, itch.io, etc.)

Platform-Specific

Steam:

• Depot configured correctly

• Launch options set

• Achievements tested (if applicable)

• Steam overlay works

itch.io:

• Correct build for platform selected

• Game page updated

• Screenshots/trailer current

Mobile (if applicable):

• Touch controls tested

• Orientation handled correctly

• Performance on low-end devices

Common Issues

Game doesn't launch

• Check package.json → main is index.html

• Verify runtime files copied correctly

• Check for missing DLLs (Windows)

Black screen on launch

• React assets not loaded (check manifest path)

• Plugin not enabled

• JavaScript error (check DevTools console)

Missing graphics

• Asset pruning removed needed files

• Review asset-manifest.txt

• Add missing references to data files

Performance issues

• Optimize large images

• Reduce particle effects

• Check for memory leaks in custom code

• Profile with DevTools

Save file corruption

• Test save compatibility after updates

• Provide save migration if data structure changed

• Warn players to backup saves

Post-Release

Monitoring

• Monitor crash reports

• Check player feedback for issues

• Track performance metrics (if available)

Support

• Provide clear bug report process

• Keep asset-manifest.txt and asset-mapping.json for debugging

• Document known issues

• Prepare hotfix process

Version Management

Track what changes between builds:

v1.0.0 - Initial release
v1.0.1 - Fixed shop selection bug, added level-up notifications
v1.0.2 - Asset pruning improvements, battleback fixes

Keep old builds archived in case rollback is needed.

See Also

• Packaging Guide

• Asset Pruning

• Debugging & Development

• Plugin Troubleshooting