Hi, I’m going through these lectures but I’m doing it version-controlled. The repo is currently private, so no real worries there, but what if, some day, I decide to build upon this game, make something personal out of it and I want to share it with the world and make this repo public (so, not just sharing the finished game, but also the actual process, or for anyone who wants to fork and build upon it) … Repo public; means all history public; means art assets public
Obviously, first of all, I’m assuming these asset packs are available only for enrolled, paying students, right?
And secondly, just in general (but depending on the 1st answer, it will probably apply here as well): what’s the recommended approach when working with such not-for-share assets?
My current train of thought: have a single
.gitignore that one, and then inside that
AssetPacks folder I can again create a new repository which then remains private (or is only shared with whoever is allowed to have that content, e.g., within a team). Going more advanced (but then I’d have to learn some more advanced git that’s not available on gamedev.tv): I could probably even go with git submodules: if I check out an older version of the project, then the AssetPacks folder also reverts to its state at that point in time.
The main problem I see here: even though the repo is public, this makes the project unshareable, no? Even if the other person also has those assets … Without the
.meta files, importer settings such as the pixels-per-unit from this lesson are not shared. So, if another person checks out my project, adds his download of the asset pack, then everything would still look disproportionate …
Alternatively, I could have any kind of structure, and finegrained
.gitignore every single file that cannot be shared (the nice thing: the
.gitignore file would at least document which assets other people would need for everything to work; but then having an entire assets “library” folder with many unused assets is less interesting), but keep the
.meta files shared. I’m not sure if this works, though, the other person would have to manually copy every single asset over, which is tedious work, and I’m also not sure what happens if they open up the project without the assets in place, wouldn’t those
.meta files simply disappear? (well, version control in fact makes this a non-issue)
But … Maybe I’m overthinking this??