Tool collection [REDELBE, rdbtool, g1mtools, doa6decsave]

REDELBE (current version 0.5)

This tool allows you to modify files in rdbs... without touching the rdb at all.

It also now allows new clothing and hair mods (Modders: Please read the file "Readme (for modders).txt" and download "Layer2 sample mods" to learn how to make new clothing/hair.

(I forgot to say it in the modme's readme, but don't put any non-ascii characters in your mod folder or it won't work properly).

If you are on game version 1.04a or higher, please download version 0.5. If you are using game version 1.03b or lower, please download version 0.4.

Installation: Copy the dinput8.dll file and REDELBE directory to the location where the game is installed.

Known issues:

• Currently there is an issue if player 1 and player 2 both use variants of the same gear (this only works when using layer2 mods). This usually happens when player1 and player2 are using the same character, same gear, in which case player 2 gear may not update and in battle it will use the same variant as player 1.

g1mtools (current version 0.6)

This is a set of several tools: g1m_export, g1m_import, g1m_hide, g1m2fbx and g1m_bonetool.

g1m_export: It's exactly the "g1m_test" I posted a few days ago, but renamed. It will export the .g1m file to the ib.vb format used by 3DMigoto. Load these files into blender using ausgeek's blender import script here. (Note: The current version of the python script can load multiple files at once, which is a feature you may want to use).

Usage: Drag and drop the g1m file, it will generate a folder containing each mesh in .vb.ib format. Instead, drag and drop the folder and it will search for all .g1m files there and export them into subfolders (very useful for exporting all game meshes at once).

g1m_import: This tool allows to do the opposite of the above, import a .vb.ib file into a .g1m file. (Note: Currently the tool ignores .fmt files and assumes the vertex and index formats are the same as in .g1m, I will fix this in the future).

Usage: Place your vb/ib file in a folder with the same name as the g1m file but without the extension. Name your ib/vb files: "0.vb", "0.ib", "1.vb", "1.ib", etc., where the number is the index of the mesh you want to modify. Drag and drop the .g1m file into the program and it will update the grid with the matching .vb.ib file.

g1m_hide: This tool allows you to hide meshes from g1m files (only affects the game, it does not affect g1m_export).

Usage: Drag and drop .g1m files. Now the program will ask you to enter the index of the grid you want to delete. You can separate multiple indexes by commas.

g1m2fbx: As you can deduce from the name it exports g1m to an fbx file. Just for visualization, don't expect me to create the opposite tool (fbx2g1m) as this is unlikely to happen.

Usage: 

• Drag and drop the g1m file and it will generate a .fbx file.
• Drag and drop the folder instead and it will scan the folder for .g1m files and create a subfolder called "FBX" where it will put all the .fbx.

g1m_bonetool: This tool allows copying bones from one g1m to another.

usage:

• Launch the program without any dragging
• Follow the on-screen instructions (drag and drop the target g1m first, then the source g1m, and finally enter the bone name or numeric bone ID).
• The program will continue with bone copying. If a bone has any parents/ancestors that do not exist in the target file, these parent bones/ancestors will be copied recursively (any bones copied will be printed on the screen).

Alternatively, if you start the program by dragging a g1m file into the program, that file will be assumed as the target and the program will only ask for the source file and bone name/ID.

suggestion:

• This is obvious, but if possible, try a copy of another costume with the same letter. If this is not possible because there is no costume for that charcoal with the required bones, then go ahead and use a costume for a character with similar characteristics. You probably don't want to copy bon …