Lukas Lichten
Registered
Packaging a Mod into a rfcmp file is quiet a tedious process: First you need to put the correct files into the correct mas file, then use MAS2.exe to package them.
There have been attempts in the past to automate this process (Noel Hibbard's Guide for ModMgr and his Component Builder), and while they still work, mostly.
But this is a attempt to package everything neatly into one program.
I present to you: The MASCompiler:
Download: MASCompiler 1.1.0
Tutorial/Wiki: Wiki
Source Code: Gitlab
Key features:
When you normally start the program you get the GUI, which is the easiest way to create the .rfbuild file, which are used in this program for saving the configurations. The Working Directory is the location where the rfbuild file will be stored, and I recommend the ModDev folder.
You can then build with this config using this format:
Currently the tool still uses the cmppack.exe, because of a strange issue with the UIAutomation (which I could talk about for ages), but I packaging from the command line works here but with cmppack it did not want to work. And you do not need to download cmppack.exe or even set it up, it comes packed into the MASCompiler.
Now I hope this is a helpful tool. If you have any ideas, then share them here (or directly contact me).
There have been attempts in the past to automate this process (Noel Hibbard's Guide for ModMgr and his Component Builder), and while they still work, mostly.
But this is a attempt to package everything neatly into one program.
I present to you: The MASCompiler:
Download: MASCompiler 1.1.0
Tutorial/Wiki: Wiki
Source Code: Gitlab
Key features:
- One rfbuild file for everyone, with relative pathing for everything!
- Command line building, but also a GUI if you want.
- Only updates files that have changed, reducing run time.
- Builds MAS out of files using rules, without you defining paths for every file
- Auto-Incrementation of version numbers
- Building Skinpacks
When you normally start the program you get the GUI, which is the easiest way to create the .rfbuild file, which are used in this program for saving the configurations. The Working Directory is the location where the rfbuild file will be stored, and I recommend the ModDev folder.
You can then build with this config using this format:
Code:
The format is: MASCompiler.exe [rfbuild file] <options...>
Options avaible:
-r Recompiling everything. Takes longer
-mas Only updates the mas files, but not the rfcmp
-cmp Only updates the rfcmp out of the preexisting mas files
-v=[number] Compiles the specific version number
-vno Compiles without an auto increase of the version number (usally 1.53 to 1.54,
if you build 1.53 prior. NOT needed when using -v=[number])
-open Opens the file in the graphical client
-rf2=[rf2Loc] Sets the default Rfactor 2 path (Usually this should be found automatically)
Currently the tool still uses the cmppack.exe, because of a strange issue with the UIAutomation (which I could talk about for ages), but I packaging from the command line works here but with cmppack it did not want to work. And you do not need to download cmppack.exe or even set it up, it comes packed into the MASCompiler.
Now I hope this is a helpful tool. If you have any ideas, then share them here (or directly contact me).
Last edited: