![]() The mono framework will be installed in /Library/Frameworks, but it won't add the mono command to your path, so you'll need to give the fully qualified path to run it.Note: some places also tell you to use homebrew to install mono - that might work too. So go to the mono project and d/l and install the mac package for mono. For that, you're going to need to install mono, since ModTek is a C# programme. Finally, you're going to need to run the ModTek injection - this is the software that will patch the right libraries to enable all the mods.Unzip the mods into the steamapps/common/BATTLETECH/BattleTech.app/Contents/Resources/Mods/ directory. Note - the location that the BEX install instructions give seems to be incorrect - see above for the correct install location. Now you can go and grab the BEX installer.You want to download and pre-cache all the assets, and the Target will be Z:/Users//Library/Application Support/Steam/steamapps/common/BATTLETECH/BattleTech.app/Contents/Resources/Mods/ Now you see why you need wine - it lets you run windows binaries. I downloaded to ~/Downloads/CAB and ran the installer from there (wine64 CommunityAssetInstaller.exe). This is all the mech models, maps, tons of extra stuff that all the main mods rely on. Download and install the Community Assets Bundle (CAB).Note - some places will tell you that its at steamapps/common/BATTLETECH/Mods - THIS IS WRONG! (at least, it didn't work for me). If the Mods directory in ~/Library/Application Support/Steam/steamapps/common/BATTLETECH/BattleTech.app/Contents/Resources/Mods/ doesn't exist, then create it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |