Fixed wrong paths and improved explanations a bit

The paths how they were mentioned were incorrect. They are based on an older implementation that didn't persist the config.
This commit is contained in:
Eonfge 2019-10-02 21:29:04 +02:00 committed by GitHub
parent 0ec73a40ad
commit 3e33a75a48
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,23 +1,25 @@
# GZDoom Flatpak edition #
## Installation of gamedata ##
* Copy any commercial iwad into the folder `~/.config/gzdoom/`
* Optionally, configure the `~/.config/gzdoom/gzdoom.ini` file to load other directories
* Copy any commercial iwad into the folder `~/.var/app/org.zdoom.GZDoom/.config/gzdoom/`
* Optionally, configure the `~/.var/app/org.zdoom.GZDoom/.config/gzdoom/gzdoom.ini` file to load other directories
## Run with custom wads
Just as with the standalone GZDoom, you can pass commands through
Just as with the standalone GZDoom, you can pass commands through using the command line. If you want to play custom wads, you can add them to a sub-directory of `/gzdoom/` and then you can directly access then from the terminal:
```
flatpak run org.zdoom.GZDoom -file ~/.config/gzdoom/pwads/PL2.WAD
cd ~/.config/gzdoom/pwads/
flatpak run org.zdoom.GZDoom -file ~/.var/app/org.zdoom.GZDoom/.config/gzdoom/pwads/PL2.WAD
```
```
cd ~/.var/app/org.zdoom.GZDoom/.config/gzdoom/pwads/
flatpak run org.zdoom.GZDoom -file ./PL2.WAD
```
For more info, see
For more info, see:
* https://zdoom.org/wiki/Command_line_parameters
* https://zdoom.org/wiki/Installation_and_execution_of_ZDoom
## Accessing files on unconventional spots ##
If you want to access wads in different locations, you might have to adjust the [Flatpak sandboxing permissions](http://docs.flatpak.org/en/latest/sandbox-permissions.html). You can easily do that like this:
```
flatpak override org.zdoom.GZDoom --filesystem=/OTHER/LOCATION/WITH/WADS --user
```