Code: { "assetSources" : [ "../../../assets" ], "storageDirectory" : "../../../" }

Code: { "assetSources" : [ "../../../assets", "../../../mods/glowing" ], "storageDirectory" : "../../../" }

Ok, I got the modding to work no problem, took a screen shot of the mod in use as well.How to mod your files on a Mac.It's basically very similar to the Linux and Windows versions, but the directory structure is a bit different, and the location of the mods folder relative to the application itself is different.So, what I wrote above still holds true. To load mods on a Mac:Navigate to your Starbound folder:(Go > Go to Folder from the finder, paste in: ~/Library/Application\ Support/Steam/SteamApps/common/StarboundThis will bring you to your Starbouhd directory. In this directory, create a folder called "mods" (see image 1) View attachment 63021 All of your future mods will go into this folder. Because of OS X's path structure, I tend to remove space names from the mods I load.For my example I used the Glowing lamp mod, which I renamed to "glowing" View attachment 63022 Once I made the proper mod folder and added the mod, you need to edit the bootstrap.config file.For Mac users, this is located inside the actual Starbound.app file. Right click (or ctrl click for laptop users) and select "Show Package Contents" View attachment 63023 From here, just edit the file in Text Edit (although I used the terminal and nano just to be safe, it appeared to work either way. The exact text to get this mod to work means you change your bootstrap config as follows.From:TO:NOTE: You must add the comma after the "assets" line or it won't load anything past that line. (the last asset line loaded is the only one w/o a comma.)Also note, unlike the Linux and Win mods, there are an extra set of ../ 's included in the address. This is because of the app/directory structure for the Mac OS, so adjust the mod location accordingly. I've seen the wrong recommended path in a few mods for Mac users.Hopefully this helps!Lanterns!