Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

When something is loaded via Loaders to Unreal, data is imported and converted to UAsset. It can take some time, it will definitely use some project space. If you have Unreal Content plugin added to the project, you can use uassets there to "link" content to the project without actually adding it there directly. So when loader is loading data, it could check if one of the content plugin associated with project contains already existing uasset (with the same name and/or metadata) and if so, then just create instance to track the loaded asset with correct path but not really importing it again.

How would you imagine the implementation of the feature?

You can query content plugins with API, they behave basically just as additional paths within the project. For implementing the feature, we need to be sure that our naming is consistent across the asset types we are loading. Conflicts could be easily solved by simple question to the artist (do you want to use existing one or load new)

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response