In order to deal with this, we have to use the. This is because GMM would take your modded file and replace the original with it.
#Superluminal ftl mod
Same thing goes for files - however, if your mod were to include a blank file named blueprints.xml you'd break the game. dat archives - that's why the directories have to have specific names, that way GMM knows where to put their contents. ftl files simply mirror the structure of the. Now look at the diagram again - see that it also has two folders named data and img? That's because. The img directory contains every graphic used in the game. The fonts directory contains fonts used by the game. The audio directory contains all of the sounds used in the game. The data directory contains all of the text files, which describe every element of the game and its statistics. dat archives that come with FTL - you'll need them anyway if you want to mod anything. In order to understand which files belong where, it might be a good idea to unpack the. zip file - contains two directories: data and img. The diagram below shows the structure of a simple ship mod. Other than that, the only thing that differs between ordinary zip and ftl is the directory structure - fancy name, but it only means that the archive has to have several appropriately named directories, so that GMM knows where to put stuff. (you can also change it from ".ftl" to ".zip" and unpack the archives to get to the mod's contents) Then, you simply change the ".zip" to ".ftl", and you're done - any warnings about the file becoming unusable can be safely ignored. You can change extensions exactly the same way you rename files - however, in order to do this, you need to have extensions shown - here's how. THIS THREAD PERTAINS TO PRE-AE VERSION OF SUPERLUMINAL AND IS NOT BEING MAINTAINED.įirst of all, read the "For Developers" description in GMM's thread.
#Superluminal ftl update
Should there be an issue that requires explanation, I'll update the topic with a new post. So, included herein will be several guides regarding topics that are not covered by the documentation. Figured that I'd finally get around to compiling some sort of guide, as to not spam the development topic with questions and replies.
0 kommentar(er)
