Editing Pikmin 2 instructions
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | Helpful instructions for editing and handling ''Pikmin 2'''s files. This guide assumes you have some basic knowledge on navigating folders, opening files, using | + | Helpful instructions for editing and handling ''Pikmin 2'''s files. This guide assumes you have some basic knowledge on navigating folders, opening files, using the command line, etc. |
| − | |||
| − | + | ==Obtaining the game's files== | |
| − | + | See [[General instructions#Obtaining a game's files|obtaining a game's files]]. | |
| − | == | + | ==Editing== |
| − | + | You can view and edit a lot of the game's files. You can read them without any worry, but if you want to change them and have those changes apply in-game, see [[General instructions#Saving changes]]. | |
| + | {{todo|Sound files.}} | ||
| − | + | ===Text files=== | |
| − | < | + | To read and edit a plain text file (<code>.txt</code>), you can use any text editor, like Notepad, although [https://notepad-plus-plus.org/download/ Notepad++] is highly recommended. If the type of file you're editing has any comment (text written in English or Japanese that comes after a #), then it's safe to say that any text that comes after a # will be ignored. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | ===SZS files=== | |
| − | + | SZS files (<code>.szs</code>) are a bit like zip files. If you want to read a SZS file's contents, you need to unpack it, and if you want to make changes to the contents, you need to repack it after you're done. | |
| − | |||
| − | |||
| − | |||
| − | == | + | ====Windows==== |
| − | SZS | + | To unpack an SZS file on Windows, use [https://www.romhacking.net/utilities/1024/ Lunaboy's RARC Tools]. Unpacking is done through <code>ArcExtract.exe</code> by drag and dropping your szs file onto it. A folder containing the SZS files' contents will then be created in the directory that the SZS was in, and now you can modify it! |
| − | + | To repack an SZS file, you will need to continue using Lunaboy's RARC Tools in addition to [https://egaddsworkshop.com/forums/showthread.php?tid=27 yaz0fast]. First, once you've modified the SZS' contents, drag the folder that <code>ArcExtract.exe</code> gave you onto <code>ArcPack.exe</code> and it will create an <code>.arc</code> file. Technically, you can rename the file extension to SZS right now and it will work, but following the next step instead will save space. Drag the newly created ARC file onto <code>yaz0fast.exe</code> and it will create an SZS file. Now rename it to the filename that the original SZS had (you need to do this if you chose to rename the file extension instead as well) and yous should be good to go! | |
| − | To | ||
| − | + | ====Mac==== | |
| + | Unfortunately, Lunaboy's RARC Tools and yaz0fast cannot be used on Mac computers. Instead, you must use a different tool called [http://szs.wiimm.de/ Wiimms SZS Toolset]. First, install it using the instructions on the website. Unpacking and repacking is done through the command line. These tools can be used with Windows as well, but it is not practical. Under Windows, there are scripts you can create to make Wiimm's process of packing and repacking easier. | ||
| − | + | Anyway, the command to unpack a file is <code>wszst extract <SZS file path></code>. This will create a folder with the same name as the SZS file, but ending in ".d". Inside this folder will be the contents of the SZS file, plus an additional data file, which is used by Wiimms SZS Toolset, so that it knows how to repack. To repack, use <code>wszst update <SZS file path></code>. | |
| − | |||
| − | + | =====Scripts===== | |
| + | If you for some reason want to use Wiimms SZS Toolset on Windows, you can create scripts to automatically unpack and repack a SZS file, so that you don't have to write commands all the time. Open a text editor, and type | ||
| + | <pre>wszst extract %1</pre> | ||
| + | Save it as <code>SZS extract.bat</code> on some folder you can remember. Create a new file with | ||
| + | <pre>wszst update %1</pre> | ||
| + | And save it as <code>SZS update.bat</code>. | ||
| − | + | After this, you can simply grab the SZS file you want and drag it onto the BAT file you need. | |
| − | === | + | ===BMD files=== |
| − | + | BMD files (<code>.bmd</code>) are 3D model files. If you simply want to view them, you can do so with [http://www.mediafire.com/?uy2nmmjmkmj BMDView2]. Editing them is a different matter. | |
| − | |||
| − | |||
| − | + | If you want to make your own BMD, you will need three things: a) [https://www.autodesk.com/education/free-software/3ds-max 3ds Max 2015] (preferably the student version, as it's free), b) [https://github.com/Avatarus-one/MaxBMD MaxBMD], a bmd importer for 3ds Max, and c) [https://github.com/Sage-of-Mirrors/BMDCubed/releases BMDCubed], a custom BMD converter that can convert <code>.DAE</code> files made by 3ds Max into .bmds. | |
| + | Once you have 3ds Max set up, you're going to want to install MaxBMD. It should come with an executable named <code>bmdview.exe</code>, which you should drop in C:\Autodesk\Autodesk_3ds_Max_2015_EFGJKS_Win_64bit_R2_wi_en-US. Once you've done that, all you have to do is open 3ds Max and drag MaxBMD's script onto its tool bar. Congratulations! You can now use MaxBMD. | ||
| + | There are multiple types of BMDs you can create now. For custom levels, check out [[Custom Models]]. For static objects such as treasures, follow the instructions on the Custom Models page but ignore any steps related to custom collision. Finally, for making custom models that have bones, watch [https://www.youtube.com/watch?v=pzUhokFHUrk this video tutorial]. All three of these model types will require you to use BMDCubed later, so keep it in a safe place! | ||
| − | + | If you just want to change the textures, you will need [https://github.com/blank63/j3dview/releases j3dview]. Open the bmd in j3dview and you can change the textures by replacing the vanilla ones with custom bti files (more on that later). To note is that a) Some textures will get a corrupted UV Map when replaced and b) j3dview is not compatible with custom BMDs or BMDs from ''Pikmin 2'' that contain bones or the like. That is, j3dview can edit the models for the first three areas and possibly the test levels & most treasures. | |
| − | |||
| − | + | ===BMG files=== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==BMG files== | ||
BMG files (<code>.bmg</code>) contain the game's text strings. [https://www.youtube.com/watch?v=ve9cgdIQbSo Yoshi2's custom Pikmin 2 BMG Tool] is highly recommended for this, as it allows you to change any text without worrying about the character count. To use it, simply drag the BMG onto <code>packBMG.bat</code>, edit the outputted text file in Notepad++, make sure it's encoded in UTF-8, save, and drag the saved text file onto <code>packBMG.bat</code>. That's all you need to do! (Keep in mind that any version of Python 3 (newer = better) is needed for this tool to work.) | BMG files (<code>.bmg</code>) contain the game's text strings. [https://www.youtube.com/watch?v=ve9cgdIQbSo Yoshi2's custom Pikmin 2 BMG Tool] is highly recommended for this, as it allows you to change any text without worrying about the character count. To use it, simply drag the BMG onto <code>packBMG.bat</code>, edit the outputted text file in Notepad++, make sure it's encoded in UTF-8, save, and drag the saved text file onto <code>packBMG.bat</code>. That's all you need to do! (Keep in mind that any version of Python 3 (newer = better) is needed for this tool to work.) | ||
| − | |||
| − | |||
Any text editor can also edit these, but once again, [https://notepad-plus-plus.org/download/ Notepad++] is highly recommended. You can find the strings after you scroll past the initial control data. If you want to edit the strings using a text editor, remember to keep their length the same. i.e. You can replace "Floor" with "Level", but not with "Step" or "Sublevel". | Any text editor can also edit these, but once again, [https://notepad-plus-plus.org/download/ Notepad++] is highly recommended. You can find the strings after you scroll past the initial control data. If you want to edit the strings using a text editor, remember to keep their length the same. i.e. You can replace "Floor" with "Level", but not with "Step" or "Sublevel". | ||
| − | == | + | ===BTI files=== |
| − | |||
| − | |||
| − | |||
BTI files (<code>.bti</code>) are image files. You'll need [http://szs.wiimm.de/ Wiimms SZS Toolset] to view these. As with [[#SZS files|SZS files]], you convert a BTI to PNG with the command line, though you can make a script to skip the command line part. The command to convert a BTI file is <code>wimgt DECODE <BTI file path></code>. | BTI files (<code>.bti</code>) are image files. You'll need [http://szs.wiimm.de/ Wiimms SZS Toolset] to view these. As with [[#SZS files|SZS files]], you convert a BTI to PNG with the command line, though you can make a script to skip the command line part. The command to convert a BTI file is <code>wimgt DECODE <BTI file path></code>. | ||
| − | To save the converted PNG files back into a BTI format | + | To save the converted PNG files back into a BTI format use the command <code>wimgt ENCODE <PNG file path></code>. |
| − | ===Scripts=== | + | ====Scripts==== |
As with [[#SZS files|SZS files]], you can write a script so that you don't have to write commands all the time. Open up a text editor, write | As with [[#SZS files|SZS files]], you can write a script so that you don't have to write commands all the time. Open up a text editor, write | ||
<pre>wimgt DECODE %1</pre> | <pre>wimgt DECODE %1</pre> | ||
