What problem does it solve?
Bulk changes to Unreal Engine projects—migrating Blueprint interfaces, cleaning metadata, renaming assets, or preparing unused-asset cleanup—are risky when done ad hoc, with no rollback, no audit trail, and no way to resume after a failure.
Core Features & Use Cases
- Dry-run-first bulk operations: Every plan runs with apply=False first, returning per-target would-change results and refusals before any modification is made.
- Four operation types: Blueprint interface add/remove migration, variable metadata hygiene, asset move/rename with path-scope enforcement, and report-only unused-asset cleanup review.
- Transactional safety and resume: Each apply target gets a named transaction with rollback on compile/save failure, and reports under Saved/VibeUE/Bulk let you resume with the same resume_id without duplicating completed work.
- Use Case: Migrate 50 combat Blueprints to a new interface version by dry-running the plan, reviewing every result, applying in batches of 10, and resuming cleanly after a crash.
Quick Start
Ask the AI to dry-run a bulk maintenance plan that adds a new interface to a specific list of Blueprints under /Game/Combat, then apply it after reviewing the results.