Suggestions

[Kilkenni]

1. Since for now Multibound lacks any docs, it could benefit from more transparent and responsive UX:
   a) grey out "Launch Instance" if no instances are created
   b) Or, better yet, inform the user that the program needs at least 1 instance (set of mods) to launch via Multibound - and suggest to create one if there are none
   c) option to create "empty instance" for launching vanilla Sb or adding mods manually (for example, in development or debug stages)
2. Add info on where Multibound settings are kept on different systems (for Lin, they are in /home/.local/share/multibound)
3. Backup and restore of storage

I assume that Multibound keeps a separate storage folder for each instance. Which is nice. Having an option to backup player/universe (for example, by zipping it with a timestamp and optional "comment" string in the name) in one click and restore it (by looking through saved zips and listing them in date/alphabet order starting from the most recent) would be even more cool.

[HALLEYSHURA]

a way to change where multibound stores downloaded files would be nice, too. also a way for multibound to use an existing OpenStarbound install instead of downloading its own.