ShipMaker is giving me problems

[TheBuilder]

Yes the sprites are in my the correct folders.
No I'm not editing anyones sprites.
The odd thing is that the ShipMaker will display the sprites if I edit the ini's by hand.
Sorry for confusing you though.
It won't be too much longer and you'll fully understand what this is all about, so don't worry about it anymore, okay.

Hmmm, you might be right that it won't import a sprite with () in its name, but then why does it accept one that's already in the ini that way?

[Anna]

Yes the sprites are in my the correct folders.

Not in that screenshot of the errors you were getting they weren't...

Hmmm, you might be right that it won't import a sprite with () in its name, but then why does it accept one that's already in the ini that way?

Because the coding in Shipmaker is screwy? No idea, honestly.

[TheBuilder]

I found out the real reason why the import feature wouldn't work for me before. It seems that the name of the custom sprites folder has to be this exactly:

Custom sprites

For some reason, if you capitalize the first s in sprites, the shipmaker wigs out when importing from the file, have no clue why this would be, but since most people don't bother to capitalize it, there shouldn't be a problem.

Weird I know but I just wanted to make sure that this was written down in case it happens to someone else.

[Kaelis]

Not, its not weird. Capitalization matters in file paths. And you shouldnt be changing directory and file names anyway. Use whats given, there is no reason to mess with it, and it breaks dependencies.

[Arcalane]

Not, its not weird. Capitalization matters in file paths.

Not normally in Windows, but I'm guessing GM is picky like *nix systems, huh?