kyonkoyuuki / yabacorganizer Goto Github PK

Error message when loading:
struct.error: unpack requires a buffer of 16 bytes

When changing Skill type in the Projectile BAC SubEntry and saving, it changes the value from U_2C instead of SKILL_TYPE in the BAC

in GOK_PLAYER.BAC, copy BAC entry 300 and paste over 301
this error message appears

You cannot edit an Animation Speed value to have decimals, like 1.1, 1.5, 1.74, 2.6, etc, despite all of those numbers being valid and recognized by Xenoverse if you manually XML edit

If you edit to a number with a decimal, move to another bac index, and then come back to the one you edited, it will have reverted back to it's original value (including if it's original value already used a decimal in the first place, like transition compression values)

using the replace function, as well, brings a straight up Invalid Value error at the bottom

using XV2 XML Serializer v2.5 on 1111_TE1_ALC.bac (Android 21's Appetizing Rush)
the tool reads and saves the floating point number correctly

the same BAC also has an integer value as Speed, which also is read and saved correctly

there is a critical bug in YaBAC, camera entry
where the X and Y rotation values are swapped, as, the X value goes in Y, and the Y value goes in X (reads and saves it that way)

In the recent 1.15.0 game update a new BAC entry was added "BACType27". It's still unknown what it does but there is a BAC file in the attachment

In the image above is the 1st instance of that BACType in the BAC.

As for the homing movement not saving properly here is what Unleashed said in The Citadel:

"New versions of YaBAC have a bug where it would set all HomingMovement values to 0 after saving
HomingMovement is used for the dashes and stuff
To Fix:
load broken moveset in the YaMov (use an old version, like 0.2.4), then load any other moveset (preferably choose the character that is closest to your modded character)
copy and paste BAC entries 440-446 and save the moveset"

And according to Unleashed it seems happen randomly.

1121_EL0_GCC.zip

the skill type in the projectile entry always shows as "CMN"

in GOK_PLAYER.BAC, copy BAC entry 300 and paste over 301
this error message appears

Would it be possible to add a dark mode to the tools or make the whole UI adhere to windows theming?
As is only a part of the UI adheres to the Windows theming and it looks quite weird.
Example:

BAC files have a SIZE_SMALL tag (boolean) meant for BacType17, it's used in older BAC files to
compensate for the missing VICTIM_DISPLACEMENT property found in new BAC files

YaBAC does read ThrowHandler correctly, but it seems it always sets SIZE_SMALL to "True" regardless if it was true or not, and also removes any VICTIM_DISPLACEMENT properties found in the BAC file

Apologies, posted on wrong tool.

for example, Super Kamehameha should have its Projectile Skill Type as 0x6 (Ultimate)
but it reads as CMN.

although it does save as 0x6

You better fix it ASAP, or else...

in HomeingMovement, "Speed" can be an integer value (frame)
or a decimal value (actual speed)
The logic of HM will change accordingly. but YaBAC doesn't accept decimal values in the text field.

and if a skill did have a decimal value, YaBAC will read the value (and save it) as 65535

well, i have always problem with the BAC tool verion 2.0 which edit by Unleashed. I noticed Everytime i use that tool it tooks really long if you e.g copy some entries or add subentries by using right click etc.. I hope this bug can be fixed to let the tool run smoothly.

Thanks.

the Skill / Moveset manual has been recently updated with new information.

most notable ones:
complete list of Bone Names for Camera, ThrowHandler, Projectile, and Effect entries.
complete list of EyeMovement Direction type flag names
expanded list of ON_OFF_SWITCH flags for Effect

in a BAC file, the HasDummy entries can disable a BacType ID
for example, HasDummy11 will disable BacType11 (Sound)
and so the sound entry won't work at all. and because YaBAC doesn't show the HasDummy entries (unlike in xml) it can be quite confusing when the Sound entry is setup correctly, but doesn't work.

so maybe if YaBAC can just auto-delete those entries when saving BAC

Traceback (most recent call last):
File "yabac\panels\main.py", line 483, in on_copy
_pickle.PicklingError: Can't pickle <class 'pyxenoverse.bac.types.physics.Physics'>: it's not the same object as pyxenoverse.bac.types.physics.Physics

to reproduce : copy any entry from any BAC file

YaBAC v0.2.2 sometimes reads "Bone User Connects to Victim From" as out-of-range values, such as 0x79 or 0x85. but the max bone flag is 0x18

also, YaBAC still doesn't read Victim_Displacement values properly.