yumia fdata tools

Umia's Alchemy Atelier fdata module tool set and ktid decoder

This is a small collection of scripts for writing custom fdata files for Atelier Yumia and injecting them into root.rdb/root.rdx to replace existing files in the game. In addition, auxiliary tools are provided for finding textures (g1t files) used by models (g1m files) in "Atelier Yumia". Other platforms/Koei ​​Tecmo games using the fdata/rdb system have not been tested, and the effects vary from person to person.

Acknowledgments

This tool was written with reference to the fdata_dump of github.com/DeathChaos25 and the code of github.com/eterniti/eternity_common, so it benefited from the extensive research conducted during the development of these tools (these results are all free and open to the public). I deeply appreciate that, thank you. I would also like to thank jmedia7 for providing information about Koei Tecmo games and the fdata/rdb file module, and github.com/mlleemiles for answering some of my questions about the fdata file module. I would also like to thank AlexXsWx and eterniti whose tools gave me an in-depth understanding of the kidsobjdb format; and woofhat for the information on using CharacterEditor.kidssingletondb.kidsobjdb to find character model textures.

need:

• Python 3.9 or higher is required to run this script. Windows users can get it for free through the Microsoft Store. Linux users please consult your distribution.

FData Tool - How to use

*All scripts require yumia_mod_lib.py to be in the same folder to run. *

yumia_mod_find_metadata.py

In order to replace a file in the game, the fdata and rdb metadata of the file are required. Run this script in the `/Atelier Yumia/Motor/` folder and enter the 8-digit hex code of the file you want to replace. For example, if you want to modify Umia's costume `0xA34C62FC.g1m`, then enter `A34C62FC` (without `0x`) and it will output `a34c62fc.file_metadata.json`. (The script also accepts this if you enter 0x.)

yumia_mod_write_yumiamod_json.py

When you have all your mod files and file_metadata.json files ready, place them in a folder and run this script. The script will first ask you to enter an 8-digit hex code for the new .fdata file - for example enter `88888888` to create a `0x88888888.fdata` file. (The script will also accept it if you enter 0x.) Be sure to choose a file name that is not already in use!

It will then ask you to enter a filename for each 8-digit hexadecimal code corresponding to the file_metadata.json file. For example, following the above example, it will ask you to enter the file name corresponding to `0xA34C62FC`, which is `0xA34C62FC.g1m`. You can also directly drag `0xA34C62FC.g1m` into the window and press Enter. The script removes the path and leaves only the file name.

Once completed, it will output your .yumiamod.json file, in this case `0x88888888.yumiamod.json`.

yumia_mod_write_fdata_files.py

This script will read the mod file and the .yumiamod.json file and write a .fdata file containing the files listed in .yumiamod.json. Continuing from the above example, place `0x88888888.yumiamod.json` and `0xA34C62FC.g1m` in the folder where the script is located and run it. It will output your `0x88888888.fdata` file.

*Note:* When sharing the mod, please consider including your .yumiamod.json file. This will allow end users to merge multiple modules together using `yumia_mod_insert_into_rdb.py`.

yumia_mod_insert_into_rdb.py

This script will read all .yumiamod.json files and their corresponding .fdata files and insert them into `root.rdb` and `root.rdx`. This script is intended to be run within the `/Atelier Yumia/Motor/` folder. Place all .yumiamod.json and .fdata files along with this script into the `/Atelier Yumia/Motor/` folder and run it. It will create backups (`root.rdb.original` and `root.rdx.original`) if they do not exist. The script always operates from the original backup, so duplicate mods are not re-inserted on repeated runs. After ru …