OoliteStarter and Oolite AppImage

[mercster]

OoliteStarter wants lots of setup directories (this was supposed to simplify oolite) like "Home Directory", etc. I don't know what the Oolite home directory is, I'm using an AppImage. The AppImage creates a GameData directory in CWD when run, containing AddOns, SavedGames, etc so I can fill those out. But what is the home directory? I tried the CWD where the AppImage is, the GameData directory, etc. It probably wants Oolite.app or whatever, but that will not exist, either in AppImage or Flatpak (I will not use flatpak.)

I will build oolite if I have to (why is there not just a plain ol' tarball for those who want one?), but is there a way to get OoliteStarter to recognize an AppImage format?

(P.S. This isn't oolite's fault, but the "Scan" button on OoliteStarter hilariously just scans ~, and I mean eeeeeverything, starting with my webbrowser's .cache directory, which takes forever, it's useless, I just cancelled it. It also is scanning down into symlinks on other filesystems, helpfully scanning several terabytes of data, instead of just starting with $HOME, looking for non-dotfile directories, and not crossing FS boundaries like a sane program. Sorry I know I'm being a smartass, this is aggravating.)

[oocube]

The home directory is the one hosting the AppImage file.

If you click the Scan button OoliteStarter will detect your AppImage. Selecting that will prefill all the directories and it should work.
At that point OoliteStarter assumes the GameData directory to reside parallel to the AppImage.