-
Notifications
You must be signed in to change notification settings - Fork 133
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1344 from SJuliez/user-dir
User files directory setting in MML
- Loading branch information
Showing
4 changed files
with
88 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
<HTML><H2>How to Use the User Data Directory</H2> | ||
|
||
<P>Use this directory for resources you want to share between different installs or versions of MegaMek, MegaMekLab and MekHQ. Fonts, units, camos, portraits and unit fluff images will also be loaded from this directory (in addition to what is loaded from MegaMek's own data). The directory should be an absolute path such as D:/MyBTStuff (in other words, not relative to your MegaMek directory).</P> | ||
|
||
<P>How to place files within the user data directory: | ||
<UL> | ||
<LI><B>Fonts</B> can be placed anywhere in the user data directory (i.e., in the directory itself or in any subfolder) | ||
|
||
<LI><B>Units</B> (.mtf and .blk files) can be placed anywhere in the user data directory | ||
|
||
<LI><B>Camo</B> images must be placed in <user data directory>/data/images/camo/. In this subfolder, further subfolders can be used (optional). | ||
|
||
<LI><B>Portrait</B> images must be placed in <user data directory>/data/images/portraits/. In this subfolder, further subfolders can be used (optional). | ||
|
||
<LI><B>Unit fluff</B> images must be placed in <user data directory>/data/images/fluff/<unit type>/. To find the exact subfolders to use, go to your megamek folder and open /data/images/fluff/. | ||
</UL> | ||
|
||
<P>This is an example of a suitable directory structure with a few example files: | ||
<BR><BR> | ||
D:/myBTStuff<BR> | ||
Oxanium.ttf<BR> | ||
Exo.ttf<BR> | ||
/campaign_units<BR> | ||
Atlas AS8-XT.mtf<BR> | ||
/data<BR> | ||
Jura.ttf<BR> | ||
/images<BR> | ||
/camo<BR> | ||
myForceCamo.png<BR> | ||
/oldcamo<BR> | ||
camo1.png<BR> | ||
camo2.png<BR> | ||
/portraits<BR> | ||
myPortrait1.png<BR> | ||
/fluff<BR> | ||
/Mech<BR> | ||
Atlas.png<BR> | ||
/DropShip<BR> | ||
Colossus.png<BR> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters