fix-up-redirectors

Cleaning up Unreal Engine redirectors in Perforce safely requires heuristic-based reference scanning across source code and asset registries to prevent broken references, which this skill automates using atomic changelist operations.

Stale redirectors cause Unreal Engine editor stalls because they accumulate as dead pointers after asset moves or renames, creating broken references that the editor must resolve manually during load operations.

You can remove redirectors without breaking C++ or Blueprint references by implementing code-reference filtering and directory-sampled test slices, which categorize redirectors into safe-to-fix, orphaned, or broken sets before deletion.

Yes, automating redirector fix-up requires Perforce CLI integration and Unreal Engine Python API access to execute atomic changelist operations and perform heuristic-based scanning across your project's asset registries and source code.

The best way to purge dead pointers after an asset rename in Unreal Engine is to use an automated pipeline that categorizes redirectors by Perforce status and referencer existence, ensuring you only delete safe-to-fix pointers.

You should avoid automated redirector cleanup when your project lacks Perforce CLI integration or Unreal Engine Python API access, as the skill requires these dependencies to perform atomic changelist operations and validate references safely.