[=NegInfinity;432448]
Also, I don’t see a reason behind defending 5-step complicated process, when references should be handled automatically without any chance of them breaking in the first place.
[/]
Like I said, in order for those references to be updated the files have to be checked out and checked back in, which you can’t always do. Even if you can, you just end up resubmitting a changed file that only has a reference change. If you do it too often, you end up just filling up your source control repro with endless copies/revisions of assets that don’t have any real changes - nightmare if you ever need to revert for whatever reason.
Perhaps I’ve not experienced the same issues as you guys, but all I’m saying is I’ve worked across multiple UE4 projects in varying team sizes and not had too many issues with redirectors. I’m not saying they’re ideal, but I can see why they’re needed. If Epic come up with a nicer system then I’m all for it (though, I’d rather not have twice as many files in each folder purely to get around this) - but for the meantime my suggestion is to maintain a well organized folder structure and if you really have to move something, follow the process I listed.
EDIT: Oh, also:
Asset Redirectors in Unreal Engine | Unreal Engine 5.1 Documentation - This page pretty much mirrors what I said. If the “dangling redirector” issue is what effects you and Fixing them up doesn’t solve it, then it’s probably a bug.