Skip to content

Instructions

Jump to bottom
Christos Despotakis edited this page Apr 3, 2019 · 2 revisions

Instructions on the steps needed for the creation of the Community patch notes

Required Software

  • xEdit: Bethesda updates the .esm file structure quite often so the latest beta of xEdit is usually required to read the files correctly. The latest builds can be found on xEdit's Discord Server (in the #xedit-builds channel). Those builds are usually created by ElminsterAU if and as needed for FO76 a few hours after the patch. Make sure you download both the 32bit and the 64bit version of xEdit, since the 64bit version is required for the creation of the .esu file.
  • .ba2 extractor: If you have access to the FO4 CK, you can use Archive2, that comes bundled with it. If not, you can use any other .ba2 extractor available. Personally I prefer B.A.E but BSA Browser is also a good alternative.
  • Text editor: CPN are written as a markdown document. You can use any text editor, but an editor with .md syntax highlighting is preferred. Personally I use VS Code.

File preparation

To have the ability to compare two versions of the game, it goes with out saying that you will need the file of both version. While we compare Fallout 76\Data\SeventySix.esm for the majority of the CPN, we also run a diff script on all the .ba2 files as well. Personally, I keep a backup of the full Fallout 76 folder for each version (data deduplication works wonders for keeping the disk usage on check), but if you low on disk space, make sure that you at least keep a backup of Fallout 76\Data\SeventySix.esm and the strings files.

What is the string files? It is the localization files needed to display the correct text of the records. They are located inside Fallout 76\Data\SeventySix - Localization.ba2. The file you will need are SeventySix - Localization.ba2\strings\seventysix_##.dlstrings, SeventySix - Localization.ba2\strings\seventysix_##.ilstrings, and SeventySix - Localization.ba2\strings\seventysix_##.strings (where ## is your language, i.e.. en for English). Make sure you extract them in your Fallout 76\Data folder. You will need the strings files for each version you are going to compare.

Here is my folder. File names will become important later. strings

So, by now, you preferably have a full backup folder of your installation, with the strings files needed extracted in the the correct place., or at the very least a backup of Fallout 76\Data\SeventySix.esm and the strings files.

Time to wait for the next update.

Creation of the .esu file

(If you are part of a team, this step is only required to be performed by one member. You can then share the .esu to the other members)

What is the .esu file?

An .esu file (Elder Scrolls Update) is an extension that TES4Gecko introduced for delta patches. Bethesda does not use those files, but we can make our life easier with those. Consider an .esu file as a "cleaned" .esm file. All identical records are dropped and you are left with a file with which you can overload your original .esm and contains only the changes.

How to create an .esu file

ATTENTION: You will need the 64bit version of xEdit for this part. The 32bit one will give you an "Out of memory error".

Load your backed up version of your FO76 with xEdit. You should use the -D: command line option to point to your backup folder. In my case, I will start xEdit by typing .\xEdit -D:"L:\OneDrive\Archive\Fallout 76\1.1.0.8\Fallout 76\Data" -fo76 on a shell:

shell

Load xEdit with SeventySix.esm only.

module

When it finishes loading, right-click on [00]SeventySix.esm and click on Create delta patch using...

Navigate to your main installation directory (or the directory with the newer .esm file) and select it

file select

Keep the default name for now

name

Let the program finish it's job. Grab a cup of coffee, this will take some time. At some point it will ask for your permission to edit files. Press ... and continue your coffee.

warning

When you finally see [##:##]Done: Creating Delta Patch, Elapsed Time: ##:## and [##:##] Background Loader: finished you are finally done. Close xEdit and confirm for the .esu file to be saved.

save

Reopen xEdit using the same console commands and load with both SeventySix.esm and SeventySix.esu selected this time.

reopen

Right-click on [01]SeventySix.esu and click on Other > Localization > Delocalize plugin

delocalize

It will warm you and ask for permission to edit the file. Press Yes I'm absolutely sure

warning

It will ask you to save the file again.

save

Press OK. xEdit will save the file an close.

Rename to SeventySixDelta [old_game_version] to [new_game_version].esu

How to check for differences using the .esu

Load your backed up version of your FO76 with xEdit. You should use the -D: command line option to point to your backup folder. In my case, I will start xEdit by typing .\xEdit -D:"L:\OneDrive\Archive\Fallout 76\1.0.2.3\Fallout 76\Data" -fo76 on a shell:

shell 2

Load xEdit with SeventySix.esm and all the .esu you want to load. Make sure to load all the intermediate .esu files as well. So, if your base .esm is v1.0.6.0 and you want to see all the diffs up to v1.1.1.2, load the base .esm, the v1.0.6.0 to v1.1.0.8.esu, and the v1.1.0.8 to v1.1.1.2.esu

For example here I load all the delta patches from the first beta (1.0.0.2) onwards:

load order

To make your life easier, apply (Right click > Applu Filter) the following filter to highlight all the sub-records that are edited.

apply filter

filter

???

Profit

Clone this wiki locally