If a wrong structure should be kept the way it is just to have consistency with the previously released projects then communication shouldn’t improve either since it’s been semi broken since the beginning. Rejecting improvements so we’d have consistency? What you’re saying doesn’t make any sense. There’s no need to have consistency with something that has not been acceptable by industry professionals in the first place.
I have not proposed any methods on my own, mind you. All of what you’re calling “standard” is -NOT- standard outside this UE4 Marketplace platform. These -standards- are not even adhered to by Epic itself all across the content examples and other projects. I can bring you at least 10 example projects right off the Learn Tab and none of them follow what we’re required to follow. Actual artists and designers tend to keep everything organized while maintaining high efficiency and it hurts to have to follow a set of guidelines designed by people who have no idea about production, I’d be really interested if any of them had a single finished project on their resume (in this case the few buyers that have contacted mike years ago).
Buyers reading this might assume we’re suggesting something in our own favor, that is not true. If localizing the assets (like Epic does for their own projects) makes it easier for the developer to work with the content, it’d be even much easier for the end user since they’re not familiar with where each asset is and where it’s dependencies are.