diff --git a/Using-the-omni‐guides.sh-Automation-Script.md b/Using-the-omni‐guides.sh-Automation-Script.md
new file mode 100644
index 0000000..487bd96
--- /dev/null
+++ b/Using-the-omni‐guides.sh-Automation-Script.md
@@ -0,0 +1,199 @@
+
+
+## Introduction
+
+While the script is still in an alpha state, I've done my best to try and capture as many eventualities as I can - but there will always be some that slip through the net. Some Linux distro's keep things in different locations, have slight variations on command syntax, and so on, but I've done what I can to allow this to be as compatible as possible. I have mostly tested this on my Nobara(Fedora) laptop and Steam Deck, though technically it should work on any distro, keeping in mind the above potential for variations.
+
+For a list of what the Automation Script does and doesn't do, please see the [Additional Notes](https://github.com/Omni-guides/Wabbajack-Modlist-Linux/wiki/_new#additional-notes) at the end of this page.
+
+Please do let me know if all or part of the script doesn't work on your platform and I'll try to expand the compatibility - this will help us all.
+
+[](https://ko-fi.com/D1D8H8WBD)
+
+---
+
+## Steps Required *BEFORE* you run the script
+
+While the script can handle most of the process, there are a couple of things it cannot do; Copying the Modlist Directory from Windows to Linux, Creating the Non-Steam Game entry in Steam, and setting the Name and Proton version of that entry. You will have to create those yourself first.
+
+The script also assumes that you have *sudo* access for your user. There are only a couple of items the script performs that requires sudo, but you should have sudo access set up prior to running (most modern distro's have this set up by default anyway, but on Steam Deck, you will have to have set a password for the deck user.)
+
+I will use Anvil as an example Modlist for this guide.
+
+---
+
+### Step 1 - Create the directory
+
+Once Wabbajack has successfully completed the download and installation of the Modlist on your Windows system, create a new directory on the Steam Deck to house the required files - this can either be on the internal storage, or with the use of a specific launch parameter described below, can live on the SD Card. Open up Konsole terminal and run **only one** of the following, depending on where you want to store the Modlist:
+
+Create Directory on **Internal Storage**:
+```
+mkdir -p /home/deck/Games/Skyrim/Anvil
+```
+
+OR
+
+Create Directory on **SD Card**:
+```
+mkdir -p /run/media/mmcblk0p1/Games/Skyrim/Anvil
+```
+
+(Note: Valve plan to change the default mount point of SD Cards within SteamOS soon, I'll update this guide once that chance is in place)
+
+Technically you can use any path or naming convention you like, but for simplicity of following this guide it may be best just to copy the paths I use. **I recommend not including any spaces in the Directory Name** - it does not play well with the Proton/MO2 combination even with the spaces being escaped, for whatever reason..
+
+Copy the Modlist directory from Windows into this newly created directory. There are many ways to do this. I chose to enable ssh on my Deck, and then use rsync to transfer. There are too many options to discuss here, but it should be relatively easy to search for methods. I copied the Modlist Install directory contents from Windows to the newly created directory on the Deck: /home/deck/Games/Skyrim/Anvil/
+
+Finally for this step, it's best to make sure that the newly copied files have sufficient permissions for your user. Run **only one** of the following for each action (owner and permissions), depending on where you want to store the Modlist:
+
+Change the owner and permissions of the directory on **Internal Storage**:
+```
+sudo chown -R deck:deck /home/deck/Games/Skyrim/Anvil
+```
+```
+sudo chmod -R 755 /home/deck/Games/Skyrim/Anvil
+```
+
+OR
+
+Change the owner and permissions of the directory on **SD Card**:
+```
+sudo chown -R deck:deck /run/media/mmcblk0p1/Games/Skyrim/Anvil
+```
+```
+sudo chmod -R 755 /run/media/mmcblk0p1/Games/Skyrim/Anvil
+```
+
+---
+
+### Step 2 - Add ModOrganizer.exe as a Non-Steam Game
+
+The next step is to add ModOrganizer.exe to Steam as a non-steam game. In Steam, click Games, then "Add a Non-Steam Game to My Library":
+
+
+
+Click Browse:
+
+
+
+Browse to the path of your Modlist. e.g. /home/deck/Games/Skyrim/Anvil, select ModOrganizer.exe, and click Open.
+
+
+
+Ensure ModOrganizer.exe is present and ticked, and then click Add Selected Program.
+
+
+
+Once added, edit the properties of the new ModOrganizer.exe entry. You can give it a more sensible name - I used "Skyrim - Anvil":
+
+
+
+Then in the Compatibility tab tick the box for 'Force the use of a specific Steam Play compatibility tool', then select the Proton version - Personally I now use Proton 9.0 Beta which has recently been introduced by Valve. This some very useful fixes for Wabbajack Modlists and Bethesda game mods in general. The script will automatically handle any additional tasks required if you select Proton 8 for whatever reason.
+
+
+
+**IMPORTANT FOR SD CARD USERS** - You must add the following to the Launch Options for the ModOrganizer.exe Non-Steam game, otherwise the Proton environment won't have access to your SD Card contents:
+
+```
+STEAM_COMPAT_MOUNTS=/run/media/mmcblk0p1 %command%
+```
+Like so:
+
+
+
+---
+
+### Step 3 - Running the Script
+
+You can run the script directly from GitHub - this will ensure you are using the most up to date version. Run the following command in a terminal/konsole:
+
+```
+bash <(curl -s https://raw.githubusercontent.com/Omni-guides/Wabbajack-Modlist-Linux/main/binaries/omni-guides.sh)
+```
+
+
+
+A banner and a short note will be displayed, and a request to press any key to continue:
+
+
+
+The script will then attempt to detect all the Wabbajack Modlists you have installed and added to Steam. Press the corresponding number for the Modlist you with to configure:
+
+
+
+You will be asked to confirm you want to continue, and the script will move on to detecting the Modlist Install directory - if multiple possibilities are found, you'll be asked to select the right one. If nothing can be found automatically, you'll be asked to manually input the path.
+
+You will be prompted for your *sudo* password so that protontricks permissions can be set correctly, and the script will continue through more automated tasks:
+
+
+
+Lastly, you will be asked if you want to set the resolution. This is optional but I'm trying to reduce the manual steps as much as I can. If you're running this on a Steam Deck, it will assume the desired resolution is 1280x800 (If you are going to be played while docked, you will have to manually alter the resolution via MO2 for skyrimprefs.ini/fallou4prefs and SSEDisplayTweaks). Not on a Steam Deck, you will be asked to input your desired resolution.
+
+
+
+---
+
+### Post-script tasks
+
+And that's it! You should now be able to click Play on the Modlist entry in Steam. MO2 should start and now be pre-configured correctly. You may still have to/want to disable any features or mods you don't want or aren't compatible - things such as ENB. For the most part, any Modlist-specific steps will still be listed in my manual guide for that Modlist, but I will also soon be attempting to add Modlist-specific steps to the automation script, where required.
+
+**PLEASE NOTE** - I have also seen a number of Modlists hang on first launch - either before displaying the Main Menu options (New Game etc), or after clicking New Game. This only seems to happen the first time, and is fine every subsequent time - I believe at this time that it is related to Shader Cache building, but I haven't been able to pin it down or resolve it. This is not unique to this automation script, and is a minor annoyance more than anything.
+
+---
+
+### Conclusion
+
+As an addition to the disclaimer at the top of this guide, I have no visibility of longer term stability, so save often, and maybe even make backups of your save-games, just in case ;)
+
+If you need help with any of the above, or better yet have another fix, tweak or workaround to help get these Modlists running on Linux, then please do stop by the #unofficial-linux-help channel on the Wabbajack Discord, I should be around so just @ me (@omni) on there!
+
+Enjoy!
+
+---
+
+### Additional Notes
+
+What this script *does not* do:
+
+```
+* Create the Modlist directory on Linux and copy the Modlist from Windows.
+* Install Protontricks without flatpak - This is far too platform specific. The script will ask the user if they want to install the flatpak version of protontricks, but if not, it's down to the user to source and install.
+* Disabling any mods - such as ENB or mods that don't work via Proton - not sure if there's any way to influence the enabled mods in MO2 without doing so through the graphical application.
+```
+
+What this script *does* do:
+
+```
+* Detect installed Modlists and ask the user to select the Modlist to configure.
+* Detect if running on a Steam Deck.
+* Detect protontricks and install via flatpak if not found.
+* Detect which game the Modlist is for (or asks if unsure).
+* Detect the Steam Library Location (or asks if unsure).
+* Handle locations on disk or SDCard (for Steam Deck).
+* Detects the modlist directory location (or asks if unsure).
+* Set protontricks permissions appropriately.
+* Enables the visibility of (.)dotfiles in the proton prefix
+* Installs the required Wine components via protontricks
+* Checks the MO2 version for compatibility.
+* If MO2 2.5 and Proton 8 are detected, offer the option to automatically downgrade to MO2 2.4.
+* Chown/Chmod the Modlist directory.
+* Backup ModOrganizer.ini prior to making changes.
+* Handle the download_directory entry in ModOrganizer.ini.
+* Detect and replace the gamePath entry in ModOrganizer.ini appropriately.
+* Detect and replace the workingDirectory paths in ModOrganizer.ini appropriately.
+* Edit the Resolution based on user entry.
+* Any smaller additional tasks for compatibility.
+```
+
+---
+
+[](https://ko-fi.com/D1D8H8WBD)
+
+
+
+
+
+
+
+
+