0. If you don't already have it installed, follow the instructions at the
Python for Beginners Download Page to install Python 3.
1. Download the DF-BAMM code from github as a zip file.
2. Extract the zip to where-ever you like.
3. Open resources/run.config with a text editor.
4. Edit 'source' to point to the directory holding the graphics you want to use. Edit 'target' to point to the directory holding the raws you want the graphics applied to. Edit 'output' to point to the directory you want your new, modified raws written to.
This directory must not be the same as the target directory. The program doesn't check, so if you do it, it's going to turn your target raws into a hot mess.
Files in the output directory will be overwritten.For this example, I'm going to apply the Obsidian tileset to the new mini-release of the Modest Mod.
Relative paths are fine too.
5. Save run.config and go back to the DF-BAMM-master directory.
6. Queue up
some music and get ready to run run_default.py .
3, 2, 1 let's bamm
7. When it's done the console will automatically exit, and your raw files will be waiting for you in the output directory
.
You'll also see two new files in the BAMM directory.
bamm.log is a general log. It's what you saw on the console, and it's pretty much just for curiosity and/or debugging.
missing.log tells you what objects in the target raws weren't found in the graphics raws. BAMM doesn't know what to do if it finds graphics information in your target raws that doesn't have an equivalent in your graphics raws, so it copies the target raws over, logs the discrepancy in missing.log, and writes a comment at the point of failure in the output raws. You can find the exact problem points by searching for the string 'BAMM' in your raw files.