BBTAG is incredibly similar to BBCF + one extra step before decompiling/after recompiling. Obviously there are different processes for different games, (gg, dbfz), but once decompiled, the process is generally the same. Feel free to play around with whatever devious creation you made. pac that isn't a copy in HIPSter, and replace the existing. If you had to close and reopen your command prompt, execute the cd command in the "decompiling" section before doing this, otherwise it won't work. Python bbcf_script_rebuilder.py myfolder\scr_xx.py otherfolder\scr_xx.bin Once you're done, take out your trusty command prompt and type in the final command that'll look like this: To recompile, the entire file has to be 100% valid python.
If you have any python programming-related questions, should have a wonderful reference on how to format things/what basic things do in python and what's valid and what's not valid. The latter means we know how much space the function takes, just not how it's formatted, so strings often extend beyond the 32-character limit there. GFX_0 happens on frame 1, while SFX_0 and Unknown7009 happen on frame 7.Īlso, strings (state and subroutine names, strings like 004_swing_grap_1_2 in the above snippet, etc.) have a general cap of 32 characters, provided they aren't entirely consisted of the characters 0-9 and a-f. Sprite( 'kk202_00', 2) #frames 1-2, these comments don't exist in the real thing GFX_0( 'efkk_202_hole', - 1)
Then start up your cmd again (if it's not still open) and type in these two lines: To decompile a script file, it's recommended you put the bin in a new folder inside the bbtools folder with bbcf_bbtag_script_parser.py in it. Scr_xxea.bin is called upon by scr_xx.bin when a projectile/visual effect needs to be spawned, and the sprite/collision durations and other properties of said projectiles are found there. Scr_xx.bin is the main script file, and controls anything that's directly attached to the character (what sprite and attached collision boxes come out when, where they come out), among other things, including health, OD durations, inputs, as well as many other qualities of the character and their moves. Their names are scr_xx.bin scr_xxea.bin respectively. pac of your choice (not one with boss in it if you're looking to see results). pacs we're looking at look like char_xx_scr.pac. pac files that are openable with HIPster. In the (folder where BBCF.exe is)\data\char\ folder there are a bunch of.
If all went well, you are good to go! Decompiling
If it didn't present you with the option to install pip, run Parser/Rebuilder Installation InstructionsĪny Python 2.7 (3+ will fail at the moment) added to your PATH (installer option) with pip (get here if the installer doesn't present you with the option to install it, right click -> save link)Īfter that, open a command prompt as administrator to install our one dependency.
Might as well make the code for these tools flexible enough to dump information and sprites for those games too.
Also, we wish to provide a mechanism to track character changes over major and minor patches to discover "secret" patch notes and provide clarity to some of the more general changes. The goal here is analyze the game files of several games made by Arc System Works and produce a set of tools that produce useful information to players of the game, as well as document changes Arc System works has made to their engines over time for educational purposes.
Tools for parsing files for Blazblue's engine (P4A PS3/360, P4AU PS3, Blazblue Chronophantasma PC) The Goal