-
Notifications
You must be signed in to change notification settings - Fork 0
Installing ACH Addons
Installing ACH Addons is as simple as a drag-and-drop action.
For information on creating ACH Addons, please see [Creating ACH Addons] or its appropriate subsections.
"Simple" ACH Addons can be installed in the ACH Addons folder inside saves:
mods/saves/ACH Addons/.
This ACH Addons folder is generated automatically whenever the game is launched when ACH is installed, if the ACH Addons folder does not exist.
"Simple" ACH Addons require no code, and can be identified by a lack of a .lua or mod.txt file inside the folder. (The textures or other assets should also be inside the folder.) "Advanced" ACH Addons require Lua code, can perform more sophisticated functions (such as hit animations, or greater control over creation parameters such as size), and can be identified by the presence of both a .lua file, and either a mod.txt or a main.xml file, as well as the textures or other addon assets.
Addons must be unpacked and placed inside the appropriate folder inside ACH Addons.
Crosshair addon folders should go inside mods/saves/ACH Addons/Crosshairs/.
Hitmarker addon folders should go inside mods/saves/ACH Addons/Hitmarkers/.
Hitsound addon folders should go inside mods/saves/ACH Addons/Hitsounds/.
Make sure that there is no extra folder "layer" generated from unpacking the download. For example, downloading the Crosshairs Pack (Advanced Crosshairs) from modworkshop may give you a .zip called 29819_Crosshairs Pack (Advanced Crosshairs)_1.zip. Unzipping this may give you a folder called 29819_Crosshairs Pack (Advanced Crosshairs)_1; this is not the folder you should install. Instead, open this folder and find the "TF2 Shotgun" folder inside. The "TF2 Shotgun" folder contains the textures directly inside; that means that you should drag the "TF2 Shotgun" folder into your mods/saves/ACH Addons/Crosshairs/ folder.
You should then be able to see your new addon available for selection in ACH's mod options menu, and evidence of its loading (or an error, if it failed to load) should be visible in the BLT log/console.