deploy: 1ea88dc

modlist_author_documentation/Introduction.html

@@ -156,6 +156,8 @@ <h1 id="introduction"><a class="header" href="#introduction">Introduction</a></h
 <h2 id="requirements"><a class="header" href="#requirements">Requirements</a></h2>
 <p>Wabbajack requires that you create your Modlist using a <a href="Compilation%20Issues%20FAQ.html#portable-instances"><strong>portable</strong></a> instance of Mod Organizer 2. This is a <strong>hard requirement</strong>. Wabbajack won't work with Vortex, Kortex, Wyre Bash, Nexus Mod Manager, Oblivion Mod Manager or any other mod manager--not even Mod Organizer 1 (at least not without severe drawbacks and complications).</p>
 <p>There is an option for compiling free of any mod manager, but this has not been tested deeply and requires more manual setup on the user-end compared to the fully automated, default method for compiling a modlist. Documentation for this method can be found at <a href="Native-Game-Installer%20-%20(Installers%20not%20using%20MO2).html">Native-Game-Installer - (Installers not using MO2)</a>.</p>
+<p>Do note that your installed Mods folder needs to be inside of your MO2 installation, so Wabbajack can replicate it.
+Your Downloads can be anywhere else, but still recommended to be outside any <a href="../user_documentation/Installing%20a%20Modlist.html">Windows protected folders</a>.</p>
 <p>In addition to using a portable MO2 installation (or using the &quot;Native Game Installer&quot; method), mod authors are encouraged to use the recommended workflow for modlist development described in the following sections.</p>
 
                     </main>