Can Marketplace assets stop overwriting config and git files?

Distribution UE Marketplace
1

With some asset packs obtained from the marketplace, after adding them to an existing project, they would overwrite important files like configuration files, sometimes git files or other files that are important and shouldn’t be changed. With assets that I collected, few of them do overwrite config files and it’s annoying to revert the changes it made. Not particularly destructive, but annoying nonetheless.

Please, can marketplace assets stop overwriting config files, git files, or any other important files one would have in a project? I couldn’t care less if it’s a Complete Project making a new project by itself, but it’s annoying to have it happen with some assets that supposed to be added on existing project. On Epic’s side, there should be at least some prohibition against it for asset packs or option when adding into existing projects to not overwrite config files.

2 Likes
2

Wouldn’t you just do a git ignore for the items you don’t want overridden? Repo’s aren’t my thing per se, but I kinda remember that’s how to make sure certain files like configs and inis and such are ignored for example when pushing an asset update.

3

Except that developers will modify the files themselves via project settings or manually editing them in text editors from time to time. Blacklisting them in gitignore would prevent the intended changes to be staged at all.

4

Then temporarily unblacklist what needs updating? Idk, I’ve not worked in large teams where I can imagine there could be logical issues with that.