View source for Dreamcast Image Builder/Adding Mods

In addition to built-in mods, Dreamcast Image Builder can load mods from the <code>mods</code> folder located in the same folder as <code>DreamcastImageBuilder.exe</code> (if the <code>mods</code> folder doesn't exist, create it).
[[File:Dreamcast Image Builder Adding Mods 1760358141895.png|none|thumb|The <code>mods</code> folder]]
Each mod goes in a subfolder in the <code>mods</code> folder. For example, if you have a mod called <code>My Hack</code>, all of its files should be in <code>mods\My Hack\</code>.
[[File:Dreamcast Image Builder Adding Mods 1760358172725.png|none|thumb|A mod inside the <code>mods</code> folder]]
You can also categorize mods using additional subfolders, for example mods for Sonic Adventure could go in <code>mods\Sonic Adventure\Mod 1</code> and <code>mods\Sonic Adventure\Mod 2</code>.

You could also use subfolders for mods meant for different games. In the screenshot below, mods for Sonic Adventure and Sonic Adventure Autodemo are put in different subfolders.
[[File:Dreamcast Image Builder Adding Mods 1760358212427.png|none|thumb|Mods in subfolders]]
'''All mods must be placed in subfolders. Do not extract mods directly into the <code>mods</code> folder. Put each mod into a separate subfolder, do not extract multiple mods into the same subfolder.'''

== Overriding Built-In Mods ==
For games that have built-in mods, if there is a mod in the <code>mods</code> folder with the same name as the built-in mod, it will override the built-in mod. For example, if you have a mod for Sonic Adventure US 1.005 called <code>Bugfixes</code>, the built-in <code>Bugfixes</code> mod will not be loaded, and the one in the <code>mods</code> folder will be used instead.