Deploying to gh-pages from @ 447213c1dd47f91a774450ce25a614efdedc1a01 🚀

articles/branches.html

@@ -139,16 +139,16 @@ <h1 id="branch-overview">Branch Overview</h1>
 <p>Here you will get a overview of the available branches:</p>
 <h2 id="release">Release</h2>
 <img src="https://cdn.alt-mp.com/static/images/updates/branch_release.png" width="100px">
-This branch is for production, it is consider as stable. This is the only branch, where the masterlist is available. If you run a public server, this server should run this branch. The icon is colored green.
+<p>This branch is for production, it is consider as stable. This is the only branch, where the masterlist is available. If you run a public server, this server should run this branch. The icon is colored green.</p>
 <h2 id="rc-release-candidate">RC (Release Candidate)</h2>
 <img src="https://cdn.alt-mp.com/static/images/updates/branch_rc.png" width="100px">
-This branch is for the next update, every update that will come to release will be at least 1-2 weeks before in this branch. It can be considered as mostly stable, here the last bugs will be fixed before they are merged to release. If you run a public server, you should use this branch before updates to update your server code to a new version of alt:V. The icon is colored orange.
+<p>This branch is for the next update, every update that will come to release will be at least 1-2 weeks before in this branch. It can be considered as mostly stable, here the last bugs will be fixed before they are merged to release. If you run a public server, you should use this branch before updates to update your server code to a new version of alt:V. The icon is colored orange.</p>
 <h2 id="dev-development">Dev (Development)</h2>
 <img src="https://cdn.alt-mp.com/static/images/updates/branch_dev.png" width="100px">
-This branch contains the newest features, not all features will be moved to RC. This branch can contain bugs and unfinished features, the features also can change. If you want the newest features you can test them on this branch and help us finding bugs. The icon is colored blue.
+<p>This branch contains the newest features, not all features will be moved to RC. This branch can contain bugs and unfinished features, the features also can change. If you want the newest features you can test them on this branch and help us finding bugs. The icon is colored blue.</p>
 <h2 id="internal">Internal</h2>
 <img src="https://cdn.alt-mp.com/static/images/updates/branch_internal.png" width="100px">
-This branch isn't public and can only be used by developers of alt:V. This icon is colored violet.
+<p>This branch isn't public and can only be used by developers of alt:V. This icon is colored violet.</p>
 <h1 id="how-to-change-the-branch">How to change the Branch?</h1>
 <p>Changing the branch is easy, for the client you need to open the altv.toml and change the branch to the value you want to use (release, rc, dev). For the server you need to download the new files for the branch you want again from the alt:V Website or using <a href="https://github.com/altmp/altv-pkg">altv-pkg</a>.</p>
 </article>

articles/troubleshooting/client-mods.html

@@ -154,7 +154,8 @@ <h2 id="remarks">Remarks</h2>
 </ul>
 <h2 id="guide">Guide</h2>
 <h3 id="enabling-mod-support">Enabling mod support</h3>
-<p>As first step we have to enable the mod directory support in our <a href="../configs/client.html">altv.toml</a>:</p>
+<p>As first step we have to enable the mod directory support in our <a href="../configs/client.html">altv.toml</a>, which can be enabled by clicking <a href="altv://action/setcfg?enableModDirectory=true">here</a>.
+If the automatic activation doesn't work, follow the those steps to manually enable it:</p>
 <ol>
 <li>Navigate to your alt:V directory</li>
 <li>Open the altv.toml file with a text editor</li>
@@ -167,21 +168,19 @@ <h3 id="enabling-mod-support">Enabling mod support</h3>
 <li>Save the changes to the altv.toml file</li>
 </ol>
 <h3 id="adding-mods">Adding mods</h3>
-<p>To add new mods simply put their files into the mods folder:</p>
-<ol>
-<li>Navigate to your alt:V directory</li>
-<li>If the directory <code>mods</code> doesn't exist there, create it</li>
-<li>Place the mod and it's related files (e.g. *.dll, *.ini, *.fx and other relevant files) into the mods folder
-<ul>
-<li>Remember that RPF files don't belong into this directory, see next step</li>
-</ul>
-</li>
-</ol>
+<p>To add new mods simply put their files into the mods folder.
+You can open this by clicking <a href="altv://action/open?dir=mods">here</a> or navigating to your alt:V directory and then the <code>mods</code> directory.
+If the directory doesn't exist, create it yourself.</p>
+<div class="IMPORTANT">
+<h5>Important</h5>
+<p>Place the mod and it's related files (e.g. *.dll, *.ini, *.fx and other relevant files) into the mods folder.<br>
+Remind that RPF files don't belong into this directory, see next step.</p>
+</div>
 <h3 id="modifying-game-files">Modifying game files</h3>
 <div class="IMPORTANT">
 <h5>Important</h5>
 <p>Always take a backup of the files you replace.<br>
-If the mod is outdated after a GTA update it is very likely that it will crash on start.</p>
+If the mod is outdated after a GTA update it is very likely that the game will crash on start.</p>
 </div>
 <p>If your mod comes with modified game files (usually in the form of *.rpf files), these need to be changed in the GTA directory.<br>
 RPF files in the mods folder are ignored and won't be processed further.</p>

articles/troubleshooting/client.html

@@ -347,30 +347,45 @@ <h2 id="quick-links">Quick Links</h2>
 </thead>
 <tbody>
 <tr>
-<td><a href="altv://action/game">Open game directory</a></td>
-<td><code>altv://action/game</code></td>
+<td><a href="altv://action/open?dir=game">Open game directory</a></td>
+<td><code>altv://action/open?dir=game</code></td>
 <td>Opens the game directory</td>
 </tr>
 <tr>
-<td><a href="altv://action/altv">Open alt:V directory</a></td>
-<td><code>altv://action/altv</code></td>
+<td><a href="altv://action/open?dir=altv">Open alt:V directory</a></td>
+<td><code>altv://action/open?dir=altv</code></td>
 <td>Opens the alt:V directory</td>
 </tr>
 <tr>
-<td><a href="altv://action/logs">Open logs directory</a></td>
-<td><code>altv://action/logs</code></td>
+<td><a href="altv://action/open?dir=logs">Open logs directory</a></td>
+<td><code>altv://action/open?dir=logs</code></td>
 <td>Opens the logs directory</td>
 </tr>
 <tr>
-<td><a href="altv://action/cfg">Open configuration file</a></td>
-<td><code>altv://action/cfg</code></td>
+<td><a href="altv://action/open?dir=crashdumps">Open crashdump directory</a></td>
+<td><code>altv://action/open?dir=crashdumps</code></td>
+<td>Opens the crashdumps directory</td>
+</tr>
+<tr>
+<td><a href="altv://action/open?dir=mods">Open mods directory</a></td>
+<td><code>altv://action/open?dir=mods</code></td>
+<td>Opens the mods directory</td>
+</tr>
+<tr>
+<td><a href="altv://action/open?file=config">Open configuration file</a></td>
+<td><code>altv://action/open?file=config</code></td>
 <td>Opens the altv.toml</td>
 </tr>
 <tr>
-<td><a href="altv://action/rep">Create report</a></td>
-<td><code>altv://action/rep</code></td>
+<td><a href="altv://action/report">Create report</a></td>
+<td><code>altv://action/report</code></td>
 <td>Creates a report zip (containing log files) and saves it to desktop</td>
 </tr>
+<tr>
+<td><a href="altv://action/crashdumpid">Copy latest crashdump id</a></td>
+<td><code>altv://action/crashdumpid</code></td>
+<td>Copies the latest crashdump id to clipboard</td>
+</tr>
 </tbody>
 </table>
 <h3 id="configuration-settings">Configuration settings</h3>