[= ;349406]
Thank you for the suggestion! I’ll talk to the dev team to see if we can find a more elegant solution to Blueprints than we currently have. I think could probably work with a mild limitation or two. More on that in a moment.
To explain a bit of how works, we’re very particular about file structure, because the back-end tools we have that processes Marketplace submissions, ‘chunks’ them, then delivers them to our content delivery network requires an extremely specific file and folder structure, and any files or folders outside of that structure is automatically removed from the submission as it’s being processed. That limits us a lot in what we can do. However, I think what you suggested could work with a tweak. Here’s the documentation we have on the file and folder structure we currently support:
So if the way you described is how you want to structure it, you could have Content -> EasyGame -> System, but you’d still need to have the .uproject and config file, and it couldn’t be simply EasyGame -> System.
I’ll talk to the team about . 
Thank you!
[/]
Hello , thanks for discussing with the team! As Kashaar mentions, the main thing is that there’s no references to the examples from the system dir. 'll be really easy for QA to test too, migrate the system dir, if anything from the examples folder shows up in the migration dialog then it’s a fail.
Cheers!