Mods menu tries to find mods in `$CWD/Mods/`

[fpiesche]

This is because the "Program Path" in TFE is set from the cwd on startup. However for mods that's not a sensible location ,as they want to live in $XDG_DATA_HOME. A patch should be added to hardcode the mod path to $XDG_DATA_HOME/Mods, and possibly one to make sure the Program Path is /app/bin as other parts of TFE may expect this to point at the main executable's directory.

[JakeSmarter]

A patch should be added to hardcode the mod path to $XDG_DATA_HOME/Mods

Are you sure this is the best way forward? Imho in the Flathub TFE release mods should be primarily managed by Flatpak extensions. In this scenario users should add custom mods (like those unavailable in the Flathub repo) via unmaintained Flatpak extensions. While at it, what do you think of searching $XDG_DATA_DIRS for TheForceEngine/Mods. This way we could have system mods and user mods. If anything, please make it at least $XDG_DATA_HOME/TheForceEngine/Mods. This would also mesh nicely with %LOCALAPPDATA%\TheForceEngine\Mods on Windows.