Difference between revisions of "Unpacking/packing packs"
Line 8: | Line 8: | ||
Each pack file results in either an story or fastsex element in the [[story menu]] and [[fastsex menu]].<br> | Each pack file results in either an story or fastsex element in the [[story menu]] and [[fastsex menu]].<br> | ||
We can also use pack directories. A pack directory is an unpacked pack file. It contains all the files from the pack file.<br> | We can also use pack directories. A pack directory is an unpacked pack file. It contains all the files from the pack file.<br> | ||
− | If a pack directory is placed in the ./pack location of XStoryPlayer it works the same as a pack file. But now you can easily edit all files. | + | If a pack directory is placed in the ./pack location of XStoryPlayer it works the same as a pack file. But now you can easily edit all the files it contains. |
==Unpacking== | ==Unpacking== | ||
− | + | <lo> | |
− | + | <li>Goto the ./filemaker directory and open the 'start.ini' file. The start.ini file contains the script code that is parsed when running the filemaker.exe</li> | |
− | + | <li>Uncomment the unpack script part like this: | |
− | + | ||
− | + | ||
<syntaxhighlight lang="cpp"> | <syntaxhighlight lang="cpp"> | ||
Pack pack1 | Pack pack1 | ||
Line 26: | Line 24: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
− | + | </li> | |
− | + | <li>Now run the filemaker.exe, the dungeon pack will automatically be unpacked to the ./pack location | |
− | + | When it is finished you will hear a whistle blowing (Useful for parsing long taking script to get coffee).<li> | |
− | When it is finished you will hear a whistle blowing (Useful for parsing long taking script to get coffee). | + | <li>You should now see ./pack/pack_dungeon directory with in it all files that are in the ./pack/pack_dungeon.bin pack file.</li> |
− | + | <li>Start XStoryPlayer and open the [[fastsex menu]]. Here you should now see two dungeon elements instead of one.</li> | |
− | + | <li>Open the ./pack/pack_dungeon/story.txt file and change the names like this: | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
<syntaxhighlight lang="cpp"> | <syntaxhighlight lang="cpp"> | ||
episode saiko | episode saiko | ||
Line 50: | Line 43: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
− | + | </li> | |
− | + | <li>Start XStoryPlayer again and you should now see that your pack is renamed to "Dungeon Mod".</li> | |
− | + | <li>Press F3 to stop XStoryPlayer directly and proceed with [[basic code scripting]].</li> | |
− | + | </lo> |
Revision as of 10:53, 6 January 2015
Most modding can be done using the Filemaker.
It is a script parser that allows you to: Unpack/pack files, Convert Maya files to Game files, Automatically create dds textures, Make font textures etc.
It has a very simple gui, because the scripts it uses contain all relevant information.
For now we will use it to unpack a pack file.
Pack files
As you may have noticed the pack directory contains several pack files.
Each pack file results in either an story or fastsex element in the story menu and fastsex menu.
We can also use pack directories. A pack directory is an unpacked pack file. It contains all the files from the pack file.
If a pack directory is placed in the ./pack location of XStoryPlayer it works the same as a pack file. But now you can easily edit all the files it contains.
Unpacking
<lo>
Pack pack1 { unpack = true; file = "[RUNTIME]pack/pack_dungeon.bin"; outpath = "[RUNTIME]pack/"; }
episode saiko { name = "Dungeon Mod"; // <<-- Change ... } episode monica { name = "Dungeon Mod"; // <<-- Change ... }