DoTA

As of v0.7b13 I've released External FEX. You can find Default FEX in "Launcher\BDO\Default.fex" and tweak it to your liking (simply open it with any text editor), or copy paste it to "Launcher\BDO\FEX" as Launcher will list all FEXs from that folder in a form of a list and then simply select it and click "Apply selected", or copy paste it to any location and then use "Change FEX" button to select your FEX. You can save it in any format, but I'd recommend to keep it in Unicode.
If you'll mess up the Default FEX to the point that it will stop working - simply press "Reset default FEX" button.
If at any point you'll feel like you don't want to use your custom FEX set by "Change FEX" or "Apply selected" button - simply press "Use default FEX" button to start using default FEX, or alternatively you can always set it by using "Change FEX" button ("Launcher\BDO\Default.fex").

Press "Get files list" button to get list of files that can be forcepatched and repacked. The resulted list "Server FEX Files List.txt" can be found in "Launcher\BDO\out" folder (e.g. "Launcher\BDO\out\JP FEX Files List.txt").

External FEX that is currently in use will be displayed above Server selection as a "Current FEX: FEX".

---

Understanding FEX code. Let's take a look on this scheme for example:

• JP - server name.
• JP Watermark - /whatever name that will appear in advanced tab, and will be used via Projects, so make sure that all of those are unique.
• PackedFileName - destination used by the game client.
• RAWDestinationFileName - where the file will be extracted (it starts from Launcher\BDO\RAW\ServerName"Here goes your path").
• SupportedStyles - supported patching methods.
  
  • None - Doesn't support any patching styles. Can be used to flag files that are allowed for extraction only.
  • Safe - Supports safe patching style.
  • Force - Supports force patching style.
  • Repack - Supports repacking style (it is not implemented as of v0.7b15).
  • All - Can be used to flag the support for Safe, Force and Repack styles, instead of specifying 1 by 1.
• Action - modifies the condition of performing actions.
  
  • None - Performs actions with a single file specified in PackedFileName. RAWDestinationFileName defines the path and name of extracted file.
  • StartsWith - Performs actions with all files that start with a specified string in PackedFileName. When extracting, all of the files will be extracted to the folder specified in RAWDestinationFileName.
  • EndsWith - Performs actions with all files that end with a specified string in PackedFileName. When extracting, all of the files will be extracted to the folder specified in RAWDestinationFileName.
  • RegexMatch - Performs actions with all files that match a specified regex pattern in PackedFileName. When extracting, all of the files will be extracted to the folder specified in RAWDestinationFileName.
  • RegexNoMatch - Performs actions with all files that doesn't match a specified regex pattern in PackedFileName. When extracting, all of the files will be extracted to the folder specified in RAWDestinationFileName.

---

Let's take a look on implementation of non-default Action, in this case "EndsWith" that will allow extracting and/or forcepatching all of the ".dds" files:

---

If you're using older Launcher version and don't understand how to update FEX yourself, here is my latest FEX (I'll update it from time to time):

Latest Default External FEX as of 09.09.2023.

Ok so had a bit of a test before heading to bed

First after install for b13 was finished for some reason it tried contacting internet (this might be something windows did, i just simply denied with comodo firewall).

Now about fex functionality.
If changing FEX file launcher need to be restarted for changes to take effect.
tried extracting one of default files (from your list) and a file from extracted list. In both cases cant find files neither in Launcher folder nor BDO live folder. Will play with it a bit more after i get some sleep.

LithStud wrote:Ok so had a bit of a test before heading to bed

First after install for b13 was finished for some reason it tried contacting internet (this might be something windows did, i just simply denied with comodo firewall).

Now about fex functionality.
If changing FEX file launcher need to be restarted for changes to take effect.
tried extracting one of default files (from your list) and a file from extracted list. In both cases cant find files neither in Launcher folder nor BDO live folder. Will play with it a bit more after i get some sleep.

If you haven't checked "Auto-check Launcher updates" then Launcher shouldn't send or receive anything from the network. It might be Windows or smth else (maybe even some virus), so check your created firewall rule, it should give you some clues.

When you change FEX it should automatically apply changes.

Regarding where you can find the extracted file I've explained THERE, basically it depends on the FEX.

KAMIKADzE wrote:

LithStud wrote:Ok so had a bit of a test before heading to bed

First after install for b13 was finished for some reason it tried contacting internet (this might be something windows did, i just simply denied with comodo firewall).

Now about fex functionality.
If changing FEX file launcher need to be restarted for changes to take effect.
tried extracting one of default files (from your list) and a file from extracted list. In both cases cant find files neither in Launcher folder nor BDO live folder. Will play with it a bit more after i get some sleep.

If you haven't checked "Auto-check Launcher updates" then Launcher shouldn't send or receive anything from the network. It might be Windows or smth else (maybe even some virus), so check your created firewall rule, it should give you some clues.

When you change FEX it should automatically apply changes.

Regarding where you can find the extracted file I've explained THERE, basically it depends on the FEX.

It was install itself that tried going to internet not the launcher exe file, i believe it might be windows defender with its stupid hidden rules as it tried to terminate install before it began.

About extraction path, as i mentioned it wasnt there, only stringtable folder nothing more. I will see if it changes with b14 version.

EDIT: Installed b14. There is something windows doesnt like in install
and the trying to contact internet thing: i traced its ip to Microsoft (probably trying to send something for analysis)

Extraction of defaults works in b14 but still doesnt detect other FEX files and refuses to use them, only editing default.fex works. Here is screenshot:


Not sure how well its seen but i had to use Change FEX button to load it (it changed the Current FEX line but otherwise nothing changed in interface - no additional sellection in selection box) - FEX file is in FEX folder, doesnt matter if launcher is restarted or not it doesnt work. Pressing Use default FEX it restores to default.fex file but needs launcher restart for changes to take effect (and show additional selection i added for crit. icon).

Thats about it for now let me know what you need else to be tested

LithStud wrote:Installed b14. There is something windows doesnt like in install
and the trying to contact internet thing: i traced its ip to Microsoft (probably trying to send something for analysis)

There are a lot of things in Launcher that it can think of as a threat. Functionality that you can use is just a small portion of what is packed into it, some of that unimplemented functionality will appear over time. That said, I have no idea what would be so different between v0.7b14 and older ones that could trigger it, I don't recall adding anything that could potentially trigger any AV, most likely it's a new Defender update (AFAIK there's Windows 10 S which prevents execution of any app that doesn't come from Windows store, maybe they added something similar to the standard Windows 10 as well, like the warning on Android if you install any apk that's not from Play Store).

Need more info on that one to say anything definitely.

LithStud wrote:Extraction of defaults works in b14 but still doesnt detect other FEX files and refuses to use them, only editing default.fex works.

Thanks for notifying, I've spotted the issue, should be fixed in b15.

LithStud wrote:Thats about it for now let me know what you need else to be tested

While I'm working on v0.7b15, check out new functionality added to External FEX (which I mentioned earlier in PM) in the main post.

made my first FEX file with custom ReGex rule and it all works
Tho by trial and error had to find out:

• Force patching sets live folder as root and not the RAW folder.
• Regex rule doesnt need opening and closing symbols (aka / /g)

So now planing next update to english patch make one selection in the force list (as i can include languagedata txt file into regex rule as well). Gonna need to write new instructions for people with screenshots just in case.