kartoFlane wrote:@Weltall
Huh. It's working fine for me. What weapon are you trying to choose?
Any weapon on the list, it happens with all of them.
Edit: I just solved it; the path to my resources folder was wrong. This was because, before your last update, it made no difference whether it was right or wrong in regards to loading an existing, in-game ship. Now that I've corrected it, I've been able to load default ships with their graphics as well.
The one thing that makes it slightly confusing is the fact that for the data.dat unpacked folder, you have to select its /data subfolder, while in the resources case, you need to select the root folder. I think you should maybe perform a check that everything expected is in the selected folders, and pop up a dialog if it's not (if you could even point ot what was expected and not found, it'd be even better). The way I would do it is, first, asking for data.dat's root folder, not the /data subfolder (for orthogonality). Then, on selection, check that the /data subfolder (in data.dat's case), and /img, /fonts and /audio subfolders (for resources.dat) are in there.
kartoFlane wrote:Edit: starting power; not exactly sure what you mean by that. If you want to change a system's starting level or whether its preinstalled or not, you can do this by double-clicking on a room that has this system; a window will appear and you'll be able to change the values there.
Awesome, that's exactly it.

I stupidly missed it even though it's right there in the tooltip. Thanks a lot!
One thing, I've had a peek at your code, and I have a couple of suggestions. I hope this is not felt as rude; feel free to ignore them in any case.
1) You have a pretty elaborate piece of code for loading/saving settings from the .ini. I would point you towards the Preferences standard java class, which makes saving, loading, partial loading and default setting file creation really easy and robust.
2) There are quite a few uncaught null pointer exceptions in the program that make the entire thing crash and close, which is a bit unfriendly. One of this is the aforementioned weapon loading when there's no valid path to the weapon image file. The thing is that you already have exception handling for IOException and such, so I would recommend one of two things: ) Initialize all path string variables to "" rather than null; that way, they'll throw "file not found" exceptions when trying to address a file with them.
b) Simply capture NPE and treat it the same way you do with the others.
Again, amazing work, you don't know how much this means for me and the FTL community at large. I expect this editor to bring a big increase in the number of user-created ships in the future.
Edit: OK, there IS another issue I forgot. For some reason, the Cloak graphic is getting stretched, even though it is a perfect match of my hull graphic (same dimensions, etc.). Any clue why that might be?
Edit2: Actually, that a problem with the floor image as well. I made one using a capture from the editor as the basis, and it was actually stretched when I imported it on the editor. Interestingly, the stretch ratio seems to be the same as the cloak image.