I'm currently in consideration of how I should implement user interaction:
- Additional Paz v3 and v3U setting, where you will be able to write files extensions for exclusion.
This sounds like the way to go, and was what I initially envisioned after figuring out what was causing the problem, but now that I think about it - there is additional check that can be done, as those files have something in common, so things can quickly get out of hands, especially if devs will add something else to it.
- Adding it to external FEX
As of now I think that this is the best way to go, even though that I have no plans on implementing it for Paz v2 as of now.
- Separate file for this setting
Sounds like an unnecessary complication.
Exclusion will work similarly to how other FEX functionality works, and you'll be able to exclude specific file, files in some folder, by extension, or even something more complicated. In this way if devs will suddenly figure out that they don't encrypt those files and will start to - you can quickly remove the rule and there will be no need to update Launcher, or if they'll start removing encryption from the other files to improve loading speed - you'll be able to add additional rules.
This^ is moving to the top priority at the moment, and I plan to release the update as soon as I'll be done with it. Not sure right now if I'll release new update with new setting working for both RAW extraction and repacking, or separately (RAW extraction is first on the line).
Other than that - new update will feature some minor improvements and new BDO Patcher scheme Data_v3 layout - "PABR_Simple12SEND" (only XML implementation at the moment) along with "PABR ExpToSkillExpRate" BSS Converter scheme, that uses it.