Minor docs update

agc93 · Aug 25, 2020 · e4e7415 · e4e7415
1 parent e7fa71a
commit e4e7415
Show file tree

Hide file tree

Showing 6 changed files with 13 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -24,7 +24,7 @@ The short version is that ACMI will scan through the mod root (defaults to the c
 
 ### What file types does it support?
 
-At current, ACMI will fully detect and specifically handle skins, radio portraits, weapons, crosshairs and visual effects. Any PAK files that can't be detected properly will still be included in the installer files in a separate "Extra Files" step.
+At current, ACMI will fully detect and specifically handle skins, radio portraits, weapons, crosshairs, canopies and visual effects. Any PAK files that can't be detected properly will still be included in the installer files in a separate "Extra Files" step.
 
 ### What else can I do?
 

diff --git a/docs/content/changelog/_index.md b/docs/content/changelog/_index.md
@@ -6,6 +6,10 @@ anchor: "changelog"
 
 This is a brief summary only of major changes in each version.
 
+- **0.2.1**
+  - Updated to support canopy files
+  - Will now add missing file name suffix if required
+  - Improved XML generation (under the covers)
 - **0.2.0**
   - Major update to add support for new object types: portraits, crosshairs, visual effects and weapons
   - Improvements to skin detection to handle more files

diff --git a/docs/content/faq/_index.md b/docs/content/faq/_index.md
@@ -22,7 +22,7 @@ The short version is that ACMI will scan through the mod root (defaults to the c
 
 ### What file types does it support?
 
-At current, ACMI will fully detect and specifically handle skins, radio portraits, weapons, crosshairs and visual effects. Any PAK files that can't be detected properly will still be included in the installer files in a separate "Extra Files" step.
+At current, ACMI will fully detect and specifically handle skins, radio portraits, weapons, crosshairs, canopies and visual effects. Any PAK files that can't be detected properly will still be included in the installer files in a separate "Extra Files" step.
 
 ### What else can I do?
 

diff --git a/docs/content/introduction/_index.md b/docs/content/introduction/_index.md
@@ -6,7 +6,7 @@ anchor: "introduction"
 
 ACMI is a simple command-line app that will automatically generate the XML files required for mod installers (like Vortex) to show a nice guided installer rather than users having to pick the right mod files on their own.
 
-Including these files will simplify installing mod packs when using compatible mod installers, showing users which files will affect which aircraft and which slot and interactively prompting them for which files to install. As of 0.2.0, ACMI supports aircraft skins, radio portraits, weapon skins, crosshairs and visual effects.
+Including these files will simplify installing mod packs when using compatible mod installers, showing users which files will affect which aircraft and which slot and interactively prompting them for which files to install. As of 0.2.1, ACMI supports aircraft skins, radio portraits, weapon skins, crosshairs, canopies and visual effects.
 
 {{< block note >}}
 Many mod installers support the Mod Installer/FOMOD standard, but it's my understanding that Vortex is the only one to support AC7

diff --git a/docs/content/usage/download.md b/docs/content/usage/download.md
@@ -4,4 +4,8 @@ weight: 11
 anchor: "download"
 ---
 
-Download the [latest release](https://github.com/agc93/acmi/releases) to somewhere convenient on your computer (put it with your packing scripts if you're using them).
+Download the [latest release](https://github.com/agc93/acmi/releases) to somewhere convenient on your computer (put it with your packing scripts if you're using them).
+
+{{< block tip >}}
+ACMI won't update itself at this time. Make sure to check [releases](https://github.com/agc93/acmi/releases) regularly for new updates.
+{{< /block >}}
diff --git a/docs/content/usage/usage.md b/docs/content/usage/usage.md
@@ -8,6 +8,6 @@ If your mods are in your current directory, just run `acmi.exe build` to build t
 
 If it completes successfully, you should see a new `fomod` directory in your mod files. Just include that folder when you ZIP up your archive (to upload to Nexus/ModDB/wherever) then anyone who installs your archive with a mod manager will get the nice guided installer. Users who want to install manually can just ignore the fomod folder and it will not affect your other files in any way.
 
-{{< block tip >}}
+{{< block note >}}
 You can also just run <code>acmi.exe --help</code> to see some basic help and usage info
 {{< /block >}}