portmaster

wiki-rtd/docs/wiki_rd_versions/version_0.9.0b/0.9.0b.md

@@ -56,6 +56,9 @@ In doing so we have:
 - RetroDECK now is migrated to an organization on GitHub that is hosting the new modular structure.
 - Rebuilt the `pre_build_automation` script was reworked with additional features.
 - Improved logging.
+- implemented tons of changes for the future Godot version of the Configurator. 
+
+<img src="../scott.jpg" width="500"> 
 
 ---
 
@@ -114,11 +117,11 @@ RetroDECK is now shipping with [Steam Rom Manager](https://steamgriddb.github.io
 We have not added support yet for the Flatpak version of Steam.
 
 
-### What is Steam Rom Manager?*
+### What is Steam Rom Manager?
 
 Steam ROM Manager a bulk game importer and artwork manager for Steam.
 
-It adds seperate games to Steam, adds artwork and configures the steam input profiles. 
+It adds separate games to Steam, adds artwork and configures the steam input profiles. 
 
 ### How does it work in RetroDECK?
 
@@ -179,6 +182,14 @@ This contains the auto generated launch scripts for ES-DE as `.sh` files.
 
 ---
 
+## New Feature - Ruffle
+
+<img src="../../../wiki_images/logos/ruffle-logo.svg" width="200">
+
+Ruffle is a Flash Player emulator written in Rust.
+
+
+---
 
 ## New RetroDECK ES-DE Theme
 
@@ -234,7 +245,7 @@ Change: Favorites collection is now enabled by default on ES-DE as it is an requ
 Change: The ES-DE settings are under a submenu in the ES-DE interface as our tools where making the menu to crowed.
 Added: Support for the Panda3DS - RetroArch core in ES-DE.
 Added: Support for the LRPS2 - RetroArch core in ES-DE.
-Known Issue: The new ES-DE submenu don't work with all translations. We hope to have better translation the future.
+Known Issue: RetroDECK's ES-DE submenu don't work with all translations. We hope to implement all translations in the future.
 
 ```
 
@@ -268,13 +279,15 @@ Known Issue: The new ES-DE submenu don't work with all translations. We hope to
 <img src="../../../wiki_images/logos/duckstation-logo.png" width="100">
 
 ```
-Change: Marked as (Legacy) because of licensing changes and respecting the developer wishes. 
+Change: Marked as (Legacy) because of licensing changes. 
 Update: Updated to the last version before the licensing change.
 ```
 
 
 ### Ryujinx:
 
+<img src="../../../wiki_images/logos/ryujinx-logo.svg" width="100">
+
 ```
 Change: Marked as (Legacy) as the emulator has stopped it's development. 
 ```
@@ -301,11 +314,10 @@ Change: Marked as (Legacy) as the emulator has stopped it's development.
 
 <img src="../../../wiki_images/logos/retroarch-logo.png" width="100">
 
-[RetroArch](https://github.com/libretro/RetroArch/blob/master/CHANGES.md)
+[RetroArch Changelog](https://github.com/libretro/RetroArch/blob/master/CHANGES.md)
 
 ```
-Change: Marked as (Legacy) because of licensing changes and respecting the developer wishes. 
+Update: Updated to 1.20.0, check the changelog for more details (above).
-Update: Updated to the last version before the licensing change.
 Added: Experimental N3DS core: Panda3DS.
 Added: Experimental Playstation 2 core: LRPS2.
 ```

wiki-rtd/docs/wiki_system_guides/portmaster/portmaster-guide.md

@@ -0,0 +1,51 @@
+# PortMaster - General Guide
+
+<img src="../../../wiki_images/logos/portmaster-logo.png" width="150">
+
+PortMaster is a simple GUI tool designed to facilitate the downloading and installation of game ports for Linux devices and is self contained.
+
+One of the goals of PortMaster is to not install or upgrade any existing OS libraries for any ports. Any of the ports that need a particular non-standard library are maintained within the ports' folder and made available specifically to that port during execution. 
+
+**Note:** 
+
+That not all 800+ ports are available for the X86_64 system, but the list keeps growing all the time.
+
+
+### PortMaster Links:
+
+[PortMaster Github](https://github.com/PortsMaster)
+
+[PortMaster Gamelist](https://portmaster.games/games.html)
+
+[PortMaster Webpage](https://portmaster.games/index.html)
+
+[PortMaster FAQ](https://portmaster.games/faq.html)
+
+### Does PortMaster require BIOS / Firmware / Other files?
+
+PortMaster does not require BIOS or Firmware but depending on the game you might need to supply the official game files from purchased titles to get them to run.
+
+Check the [PortMaster Games List](https://portmaster.games/games.html) for details.
+
+## Where are the files located?
+
+There are two main directories:
+
+`retrodeck/PortMaster/ports/` 
+
+This contains the game files, savefiles and directories. This is also where you add any required game files.
+
+`retrodeck/roms/portmaster/` 
+
+This contains the auto generated launch scripts for ES-DE as `.sh` files. 
+
+## How to use PortMaster?
+
+You go into the PortMaster menu in ES-DE and Open `PortMaster`. 
+
+The application will auto update to the latest version and from there a library of ports will be shown. You go to a port and press the download button and it will downloaded and added to the ES-DE interface under the PortMaster menu.
+
+
+
+
+

wiki-rtd/docs/wiki_system_guides/srm/srm-guide.md

@@ -0,0 +1,95 @@
+# OpenBOR - General Guide
+
+<img src="../../../wiki_images/logos//openbor-logo.svg" width="150">
+
+Open Beats of Rage or `OpenBOR` is a beat 'em up game engine and Chronocrash is the main community of OpenBOR.
+
+## Notice: OPENBOR IS BROKEN
+
+The current standard OpenBOR solution is not working as well as we hoped. We are going redesign the implementation and ship it in a upcomming update.
+
+Sorry Beat 'em up fans, you will have to wait for the fix.
+
+### OpenBOR Links:
+
+[OpenBOR Github](https://github.com/DCurrent/openbor)
+
+[OpenBOR Wiki](https://github.com/DCurrent/openbor/wiki)
+
+[Chronocrash Community](https://www.chronocrash.com/)
+
+[Chronocrash Wiki](https://chronocrash.com/obor/wiki/)
+
+[Chronocrash Forum](https://www.chronocrash.com/forum/)
+
+
+
+## Where to put the games
+OpenBOR games should be put under the `retrodeck/roms/openbor/` directory.
+
+## Does OpenBOR require BIOS or Firmware?
+No
+
+## What file formats are supported?
+
+`.AppImage `
+
+### Information
+
+- The games need to be uncompressed to a folder.
+- Each game is its own self-contained game, and no overarching settings exist.
+
+### Example folder structure of a OpenBOR game
+
+A fake fan game called `Heroes of Phandalin`
+
+```
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/Logs/
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/Paks/
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/Saves/
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/ScreenShots/
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/Heroes of Phandalin.AppImage
+```
+
+## OpenBOR How-to add a game
+
+- Extract the game if it is compressed into a new folder under `roms/openbor/`.
+- Rename the folder so it is called `<gamename>.AppImage` in the end of it.
+- Open the game folder and see if the `OpenBOR-Linux-x64-<versionnumber>.AppImage` file is there in the root of the folder.
+- If the file is there rename it to `<gamename>.AppImage`.
+
+The game should now be detected and runnable from RetroDECK.
+
+### Example on renaming:
+
+If the game is called Heroes of Phandalin rename the `OpenBOR-Linux-x64-<versionnumber>.AppImage` file & the games folder to `Heroes of Phandalin.AppImage`
+
+```
+~/retrodeck/roms/openbor/Heroes of Phandalin.AppImage/Heroes of Phandalin.AppImage
+```
+
+The `Heroes of Phandalin.AppImage` file exists within the `Heroes of Phandalin.AppImage` folder.
+
+### OpenBOR.AppImage is missing:
+
+If the `OpenBOR-Linux-x64-<versionnumber>.AppImage` is missing from the games folder you will need to download it from [OpenBOR Github](https://github.com/DCurrent/openbor) releases page and add it to the game folder.
+
+Copy the file the games folder and rename it as stated above then make it executable.
+
+**NOTE: On compatibly** <br>
+Some games might only be compatible with certain version of OpenBOR. Try the latest version first and if that does not work check the games folder for clues on what version it was made for and download the correct .AppImage version from [OpenBOR Github](https://github.com/DCurrent/openbor) releases page.
+
+#### Make the file executable
+
+**Using the terminal:**
+
+```
+chmod +x OpenBOR-Linux-x64-<versionnumber>.AppImage
+```
+
+**Using the Systems GUI**
+
+This example is from KDE:
+
+Right Click on `OpenBOR-Linux-x64-<versionnumber>.AppImage` -> Properties -> Permissions -> Check the `Is executable` checkbox.