We’re trying to understand Epic’s long-term direction for the UE Editor’s asset duplication tooling, specifically IAssetTools::AdvancedCopyPackages and IAssetTools::MigratePackages.
We reviewed UE 5.7 and noticed continued investment in both paths (e.g., optional header-patching support for Advanced Copy, and various robustness improvements in Migrate).
Could you share guidance on the following?
Are AdvancedCopyPackages and MigratePackages expected to remain the primary mechanisms for “copy/duplicate assets with dependencies” in the foreseeable future? Or are there any new editor solutions to supersede Advanced Copy / Migrate?
For Advanced Copy, what’s the trajectory for the header-patching approach? This appears to be opt-in and not the default solution for now, but is Epic converging towards header patching as the primary solution for asset copies?
For your questions - I spoke to a few teams involved and checked on current known roadmaps for the year:
AdvancedCopyPackages and MigratePackages are in active maintenance. We plan to continue to use those and support them in their current forms for the forseeable future. If you have specific support questions or issues, please feel free to open a support case.
For the header patching approach, the short answer to your question is yes. We believe it provides better throughput, performance, and is more flexible for customization to default serialization. We are testing it and working to make it more robust in future releases. Eventually the goal is to make this approach the default, but I don’t have a timeline to share on when it would be available. Please feel free to use the cvar and report any issues you find, but be aware it should be considered experimental at this time.
[Attachment Removed]