All plain text files in:
- Data\Mods\<your_mod>
- Data\Projects\<your_mod>
- Data\Public\<your_mod>
- Data\Editor\Mods\<your_mod>
Setting up a Git repo with symbolic links or hardlinks is kind of a pain, but it can be done. But to make this easy, you just want to move those folders to your repo outside the game directory, and then create
junction points where they should be in the game directory. The game and editor won't know the difference, and you'll have everything in one place for your repo.
If you're working with binary assets, you must use
Git LFS for binary assets. GitHub offers
1 GB of free LFS space and bandwidth. Never ever commit binary assets to a non-LFS repo unless you want to end up with massive Git performance issues down the road.
If you're not working with binary assets, use
.gitignore to force Git to not track files with these extensions:
*.bik
*.bnk
*.bshd
*.bullet
*.cur
*.dat
*.data
*.dds
*.fnt
*.gr2
*.iggy
*.iggytex
*.lsb
*.lsf
*.lsfx
*.osi
*.patch
*.png
*.swf
*.tga
*.tmpl
*.ttf
That list is itself the
.gitignore file you need to commit to your non-LFS repo. (Note: There is a single .lsfx file that should be an .lsmg file in the editor data, but you'll never see that file in your project data, so #trivia.)
You can otherwise use that list to set up the binary files you want to track with LFS.
