Your launcher is put in the root folder:
../Starmade/launcher files
and it puts your game in:
../Starmade/StarMade/game files
This is confusing when explaining someone to find a specific file, they often search around in the launcher files instead.
I would suggest you put both game files and launcher files in their own folder of the root one:
../StarMade/launcher/launcher files
../StarMade/game/game files
<replace this line with the file content>
<replace this line with the file content>
Merged tasks, original issue is fixed but shows a slight improvement could do wonders.
-QA Testing-
For initial setup of clean launcher install
Default path is now
../launcher files (folder for the launcher itself)
../launcher files/StarMade/ (default folder for gamefiles inside launcher )
../launcher files/.cache (launcher config etc. files - T1704 )
on browse to a folder a /starmade is added if the folder isnt containing a Starmade install already
(same behaviour is seen when changing the path later in the options)
as far as i do understand ... fixed for Win 7 and Linux
@SmilingDemon asked me to check this on OSX. Here's what I see with an install of Launcher v.158
This path is a departure from previous versions. Previously, the default/suggested path was
~/Library/Application Support/StarMade/
That ~/Library/... path is a generally-expected location on the OSX platform, for this type of data.
Storing game data in the .app structure itself will be very problematic, as anytime a player updates the launcher by installing a new .app file, they'll now overwrite their StarMade install, including previous worlds/BPs/configs/etc...and then probably cry a lot.
A side-note: while you evaluate where to place this folder, please consider creating unique structures for "dev", "release" and "pre"...as it's quite annoying for someone that frequently switches amongst differing builds, to frequently re-download a half-TB of data. I'm not suggesting a unique folder for each version, just the major builds, that'd be quite nice.
The launcher will auto-update, removing the need for the user to update it manually; however, I can see this being a problem in the unlikely event something breaks (from user error or otherwise), necessitating a reinstall. I very much prefer having the entire game self-contained, however.
I'm also unsure what the best path would be for this -- i'm simply not familiar enough with OSX. I'll do some research into it, and may end up reverting the suggested path to ~/Library/ for OSX.
Re: side-note: yes, that's one of the most annoying remaining issues. I will address it when I add official support for concurrent installs. It will take a considerable amount of work, though, so it'll be in a future update (: