https://www.reddit.com/r/skyrimmods/comments/qt2tsv/which_fixes_from_the_engine_fixes_mod_would_you/

Perhaps some of the known LE and SE bugs have been fixed?

This topic is to document bugs that are verifiably not fixed, and note priority to find and fix.

What constitutes Skyrim Special Edition Now?

This one is relatively simple. Skyrim Special Edition was updated to game version 1.6.318 (there was briefly a 1.6.317 but a hotfix came out a few hours after launch). This update included recompiling the .exe file with a newer version of Visual Studios, and this recompiling has resulted in a small boost in game performance due to the new optimizations that VS2019 offers. There are also now 4 additional DLCs which have become part of the package: Survival Mode, Saints & Seducers, Rare Curios, and Fishing. The first 3 are existing DLCs, the Fishing one is brand new with this update.

All of this has been provided to everyone on all platforms as a free content update, thus making version 1.6.318 the new "base game" that everyone gets.

As a bonus, there were also a number of other bugfixes made to some things.

What Constitutes Skyrim Anniversary Edition?

The Anniversary Edition upgrade of the game is a paid DLC package on each platform. Since I am obviously not familiar with how the XBox or Playstation storefronts work, I'll describe what is done in Steam.

On Steam, the Anniversary Edition Upgrade is a $20 paid DLC package that produces some sort of token which tells your game to unlock the other 70 DLCs which are part of this update. Nobody gets this unless they go out of their way to purchase and then download it. Nothing is forced.

So what is the Modpocalypse then?

There is no "Modpocalypse". In the run up to the release of the Anniversary Edition a number of nightmare scenarios were offered that in the end did not come to pass.

Rather than some kind of doom scenario where every mod stops working properly and we all have to fall off the grid to keep Steam from updating the game, it's turned out to be just like every other update to SSE that's ever been put out. There will be a short period of time where some inconvenience is present while stuff updates. Unfortunately, there are those out there who just want to see the world burn and they run with the first bit of information they see, never bothering to come back to see if it was true or not. This has led to a number of mod authors declaring they won't be making "AE versions" of their mods - without realizing there really isn't a distinction between AE and SE as far as their mod is concerned. There is only an update to SE.

SKSE64 has been updated already. Proper support for the plugin management system is in place, and 3rd party extension updates are now flowing again as they always do. It's been less than a full week since the game updated, so this should be considered a somewhat faster response than usual overall. This as at least partly because Bethesda gave the SKSE64 team pre-release access to the update, under an NDA.

What if I don't want to update?

Then don't?

But seriously, regardless of what measures are taken, Steam will eventually have its way and your game will update. Offline mode is not permanent, and the update on launch option will not allow you to ignore it indefinitely with any game, not just Skyrim.

If that bothers you too much, the sanest thing you can do is play something else until the dust settles on whatever is giving you pause. Since you aren't having to pay anything for the basic update, there's really no harm in letting it happen and coming back in a month or two. If you're like me, you have plenty of other games waiting to be played while you wait for things to get updated. As a mod author, I have some things that need it. As a player, I'm waiting on certain specific things before going forward with a new game. In the end though, it will be a new game grounded on the current officially released version on Steam.

It would be STRONGLY recommended to avoid hackish solutions like updating and then promptly installing executables from the previous update or running a program to downgrade your game. Solutions of this nature can come back to bite you in the ass. Things like this can lead to strange problems while playing with mismatched versions of files. Anything from poor performance, to CTDs, and possibly even save corruption. It's really not worth the risk. Plus if you should need technical support from Bethesda for some reason, they will not provide it if you've done this.

What about the CK?

There is currently no update to the CK, but it is largely unnecessary anyway. Unless you are specifically modding content from the Creation Club and need the source code to those scripts, you're fine. You can continue to use it without worry.

That said, it's a good idea to update when such an update is made available.

I've recently started importing my playable characters into CK and making them actual NPCs by adding them to the game world.

I use SPF CHARNAME to save their appearance and then just click IMPORT in CreationKit. But I have one problem though. 

For some reason, some characters don't get their hair ported in CK. For some, it works flawlessly, but for others, it adds some generic hair that they don't wear in the game.

I also noticed I can't find all the hairs from the game in CK when I scroll through available ones, for whatever reason. I do not use any hair mods, it is all vanilla.

Any help would be appreciated. Thanks in advance!

Here are a couple of links which lead me to this solution: Screen freezes but game keeps playing? [SOLVED] ; Game freezes but actually keeps running in the background (frozen screen, but playable and audio hearable)

Here are my specs, for the record:

Weapon racks have 2 main parts:

1. a visible part. It uses WeaponRackTriggerSCRIPT. Unlike most visible actuators (such as seats), it does not cause any action. Instead, it merely triggers as a weapon is passed near it. Usually, that trigger is something being added to the rack, or to another rack nearby, and must be ignored. Sometimes, that trigger is a player removing a weapon or armor item from the rack.
2. an invisible trigger marker placed directly in front of the visible part. It uses WeaponRackActivateSCRIPT, and has ACTIVATOR in its name. When triggered, the script places a weapon into the front of the visible part using MoveToNode(). The visible part has many such named attachment "nodes".

Because of the unusual design, there were many locations that simply had the wrong script on the objects. It became apparent that various designs were attempted, and some old designs with the wrong scripts or variables remained in the files. So a significant US*P change to the scripts was adding a CheckConfiguration() function to log places with bad setup so that they could be repaired later.

Although the design expects that the visible part has a pointer to the invisible part, and vice versa, there was no check. (A check was added.) Many locations have no invisible part. Others had/have the invisible part in front of the wrong rack, or even underground. Again, there is no easy check.

There are many flavors of racks. Most do not actually allow a player to add a weapon to the rack. But they use the same scripts, so the scripts have to account for all possibilities.

Some have PlayerHouse in the name, and allow a player to add a weapon to the rack. Others are specific to locations. A few OLD and Nor designs are unused.

Some are used as backing plaques, or as decorations, and their scripts were deleted from them. Others used another technique to disable the rack parts, such as pointing the rack to itself, or to the player object. There is not much implementation consistency.

Finally, the ACTIVATOR can point to a StartingWeapon. This can also be armor.

All of the item pointers are stored in the invisible WeaponRackActivateSCRIPT property PlayersDroppedWeapon, instead of the visible rack itself. Therefore, every rack with a starting item requires an invisible ACTIVATOR, even though most racks do not accept player weapons so the activator is otherwise unused. Inefficient and cumbersome, and not all Bethesda developers understood the design. Many racks were missing an ACTIVATOR. Many more have an unused ACTIVATOR that does nothing.

Unfortunately, there were originally two methods of pointing to the StartingWeapon: GetLinkedRef() or GetLinkedRef(WRackStartingWeapon). However, only the rare WeaponRackDaggerDisplayACTIVATORPlayerHouse specified the latter, and it was never used. So that complication was removed from the scripts.

The Actor Script shows it's a native function, so no help there.

The first principle of navmesh modding is: never delete or merge navmeshes! That way lies CtD (crash to desktop).

The second is like unto it: to reduce the number of conflicts, border triangles should not be renumbered!

Every adjacent cell navmesh has a link table with pointers into these border triangles. If a navmesh is deleted, or merged, or a border triangle is renumbered to be anyplace else, creatures/NPCs will "jump" into that triangle number as they cross the cell border. Sometimes they become stuck in place. Sometimes this also may make it impossible for the PC to move.

If possible, have the same number of triangles as the original. When you delete any triangle, the CK renumbers. This often changes border triangles.

Therefore, great care must be taken. It is usually better to first create a new triangle over the old, then delete the old triangle so that the new triangle is renumbered with the old triangle number, then join/merge the final vertice in place. (This technique is also used to repair border triangles.)

When you "Find Cover" for a cell, sometimes the CK renumbers triangles. Up to 2 sides of cover are saved (the 3rd side is assumed to be flat to the adjacent triangle), so triangle vertices sometimes need to be rotated to allow the cover data to be in side "0-1" and/or side "1-2" (as shown in xEdit). Apparently, the CK deletes the triangle (causing renumbering), then adds a new one in the proper orientation. Yet the CK already has a user tool for rotating a triangle without renumbering; it fails to use it internally.

When you Finalize a navmesh, the CK doesn't just touch the one you are changing. It also saves adjacent cell navmesh. In the outdoors, this results in 4 cells around the square. Presumably, this is to update border links caused by deletion or renumbering -- even when there have been no changes.

The CK works reasonably well only having Update.esm, but is a disaster waiting to happen with multiple modders updating adjacent cells. Each changes 5 cell navmesh, so the conflicting border link tables cause massive confusion.

(Following posts have more detailed information.)

See also:

• https://www.afkmods.com/index.php?/topic/3337-skyrim-fixing-navmesh-deletion-using-tes5edit/
• https://www.afkmods.com/index.php?/topic/4072-navmesh-audits/

Important: For information on how to install Bodyslide in MO2 see the Nexus Bodyslide page instructions.

In other mod managers, all the output files after doing a Batch Build in Bodyslide typically overwrite the existing mesh files. However, in MO2, the files are separated into the "Overwrite" folder first. These must be moved into their own new mod for changes to take effect.

There's an automated way to do this and a manual way. The automated process only needs to be done once. The manual process needs to be done after every build in Bodyslide.

Automated - Recommended BEFORE running Bodyslide

1. In MO2, create an empty mod
   - Right click anywhere in the left pane -> Create Empty Mod

   - Name it Bodyslide Output (or something easy to remember)

   - Make sure it's at the bottom of the mod list and activate it

2. In MO2, edit the executables list and highlight Bodyslide
   - Tick the box beside "Create files in mod instead of overwrite" then select the Bodyslide output folder in the dropdown list

   - Apply the change

3. Generate Bodyslide batch build per normal.
 

The files will be directed to your new mod and will not need to be moved from Overwrite into it every time you run Bodyslide.

If you happen to have run Bodyslide first before setting up MO2, follow this manual process to clean up.

Manual - If Bodyslide was done first

1. In MO2, create an empty mod (see Step 1 above for pictures)
   - Right click anywhere in the left pane -> Create Empty Mod
   - Name it Bodyslide Output
   - Make sure it's at the bottom of the mod list and activate it

2. Generate Bodyslide batch build per normal.

3. Open the Overwrite folder
   - Right click -> Move content to Mod to move the contents (Meshes folder only) to the new Bodyslide Output mod or right click -> Open in Explorer to drag the contents (Meshes folder only) to the new Bodyslide Output mod

After every time Bodyslide is run ensure the output from the Overwrite folder is added to the Bodyslide Output folder (allowing for any actual overwrites in there), or follow the Automated process to set it up now and not worry about it any more.

(Thank you to Peter.nn for the pictures)

You'll need to have access to the current SSE CK and a copy of xEdit 4.0.1 or higher at minimum. If you have meshes, you'll need a copy of the SSE Nif Optimizer program.

BSA Files
 
If your mod uses a BSA file (and pretty much any decent one ought to be if it has assets to provide), you can't simply use that file with SSE. The game will either hang or crash at the opening menu.

This step should be done before trying to load your mod into the CK as well since the same problems will occur with the CK - it'll either hang or crash.

Meshes (.nif files)

Unpack your files to a temporary location somewhere. Grab Nif Optimizer and follow its instructions to convert your files. If you have any files that use decal flags (the SLSF1_Decal or SLSF1_Dynamic_Decal flags) these flags may need to be removed. If you some across one of your files that has translucent parts that shouldn't, this is probably why. SSE seems to handle those flags differently and plenty of vanilla stuff had to have this done as well.

Textures

.tga files are no longer supported. If you have assets using these, they need to be converted into proper DDS files.

Textures originally saved in either the A1R5G5B5 format or the B5G6R5 format must be resaved in A8R8G8B8, R8G8B8, or an equivalent compressed format like DXT5 or DXT1. If this is not done, some installations of DirectX 11 will not be able to process it and SSE will crash. This seems to be most common for folks using Windows 7. SSE Nif Optimizer should be able to detect these issues with the "Scan Textures" option.

Some landscape textures will need to be fixed manually. If your landscape texture loads into SSE and looks like it's wet when it's not supposed to be, you found one that needs to be fixed.

Animations

Animation files for 32 bit will not work out of the box. Depending on what they are, you may end up with NPCs or the player stuck in a default pose unable to move, or perhaps even being unable to move the camera at all. Fortunately Bethesda has supplied a tool with the new CK that will allow you to update your .hkx files to the new format. This is necessary due to Havok being upgraded to 64 bits.

The ESP/ESM File + Facegen

Your plugin file needs to be loaded into the new CK for SSE and saved so that all of the form versions on the records can be properly updated.

If it's an .esm file then you need to remove that flag to be able to load it properly to be resaved.

You should make sure you include Update.esm, Dawnguard.esm, Hearthfires.esm, and Dragonborn.esm as masters to your file. There should be no exceptions to this as all SSE users will be playing with these files active. The game will not even launch if one is missing.

If your mod has NPCs, this process will also generate updated Facegen files. Be aware that if you have made facegen changes to vanilla NPCs those new facegen files will have been saved in the folder for your mod and you'll either need to separate them to the correct folders or delete what the CK generated when it saved and use the manual process with CTRL+F4 to generate them again. The manual process will assign them to the correct folders.

You can safely delete the .tga files generated by the CK. The game will never use them and they just waste space in your mod's archive for distribution.

DO NOT attempt to circumvent the need to load your mod into the CK by using scripts or other tools to shortcut the process by faking the new form versions. You WILL end up corrupting the saves of anyone who uses your mod if you do this.

Fixing Up the ESP/ESM

Once your file has been saved you'll need to do some minor fixing to make sure it's fully ready.

River Flow/Water Data

Mods which edit exterior CELL records will need to be checked cell by cell to update the water data to fit with the new shader based water flow mechanics introduced with SSE. This is best accomplished by using xEdit to compare your CELL data with the CELL data from Update.esm. In nearly all cases you should forward the changes from Update.esm because Bethesda themselves didn't do so in their own DLCs which overwrite that. Guess who had to fix that You can also use USSEP as a guide for the proper value since we've already gone through and corrected them all for the base setup.

Failing to account for this information will lead to people complaining about water seams on the cell borders between your work and the base game and will also show up with water flowing the wrong way as well.

New Ground Clutter

There was a lot of new foliage and other ground clutter added to places all over the game. Especially in more populated areas like the towns and villages. You will need to check to be sure you have no conflicting placements with these new objects. Assuming you know your mod well (and who doesn't) it shouldn't take more than a couple of minutes to poke around any work you've done and make sure no new stuff is in your way.

Failing to address this will result in some unsightly clipping in many places.

Landscape Data

In several instances, landscape was also edited to add more ground details such as grass and those tiny rocks. Old mods will not have this underlying data if they've edited the landscape as well and it will probably be worth redoing much of that in order to preserve continuity with any surrounding cells that have not been edited. It may be possible to use xEdit to copy the Vertex Normals and Alpha Layer data so long as the land height itself hasn't been edited, but in doing so the mod will need to be rechecked to make sure no grass is poking through in places it isn't wanted.

Worldspace and CELL Editor IDs

If you have worldspace or CELL records with underscores in their editor IDs, you will need to manually change those to remove the underscore. If you do not, it will cause SSE's save sorting to be unable to handle the situation when you save your game in one of these places. This results in a player's saves no longer being listed under their character names which will make them harder to locate and could lead to corruption as well.

Weather Data

All of the default weather now supports Volumetric Lighting and has a new set of records to facilitate this. If your mod changes weather data it will need to account for this.

Other Changes To Be Aware Of

All of the game's grass records (GRAS) have been updated to push higher grass density.

Most of the game's Image Space Adapters (IMAD) have been updated with new alpha and blur values.

Most of the game's Image Spaces (IMGS) relating to weather have been updated with new HDR values.

A few Landscape Textures (LTEX) picked up an unknown INAM value, along with a couple having specular values modified.

Many snow and ice related statics (STAT) have been updated with new texture sets and material shader settings.

5 new landscape texture sets were added. Referenced by many of the other edits.

Pretty much every type of water (WATR) was updated for the new water shaders.

Books can no longer use the hidden Note/Scroll flag. Any changes to this will be automatically reverted by the CK every time. The game no longer uses them either.

ESLify Me?

If your mod happens to be small enough to qualify, you may wish to consider marking it with the ESL flag. Doing so can help extend the number of slots a user has available for other mods.

Consider the points raised in this topic before you decide: https://www.afkmods.com/index.php?/topic/5079-plugin-files-and-you-esmeslesp/

LOD Files

LOD files for objects will need to be regenerated as they are using a different texture atlas layout than the one supplied by LE.

LOD files for trees should be useable as-is, and this is recommended since the SSE CK cannot generate trees. In my experience, xLODGen doesn't do the job correctly either and results in tree LOD that doesn't match the actual trees.

Scripts

Scripts do not need to be recompiled. Despite rumors that they will break, this is not the case even for things that relied on SKSE. All vanilla and DLC Papyrus .pex files work out of the box, as do all SKSE script when being used with SKSE64. You should have no reason to need to recompile any of your own .pex files when porting to SSE.

That doesn't mean you're home free though - you may have a special situation with a Papyrus script written to work with a specialty SKSE64 plugin that needs to be recompiled to work. You'll have to check with that plugin's author to find out if that needs to be done.

In my personal experience, all of my scripts for all of my mods worked right out of the box. This includes all of the MCM related scripts that began working as though nothing was wrong when SKSE64 finally came out.

One thing you do need to keep in mind though is that the CK's default folder for scripts has changed. Instead of being stored under Data\Scripts, they will now show up under Data\Source. There are 2 solutions to this issue:

1. Leave this as it is and copy all of your own scripts to match the new path names.

2. Change the location in your CreationKitCustom.ini file to point to the old one. The line should look like this: sScriptSourceFolder = ".\Data\Scripts\Source"

Whichever solution you choose you need to be sure that all vanilla and DLC scripts are in that location or the CK will not be able to find them.

Sound/Voice/Video Files

Sound effect files do not require conversion. They can be used as-is.

The same is true of any recorded dialogue. Those work as-is.

Video files do not need to be converted either. They should all run as-is.

SKSE DLL Files

These must be recompiled to use SKSE64 or the plugins will simply not function. If your mod depends on one of these, the plugin's author needs to do the work and release an update.

I experimented a lot with the implementation of custom music, which is added via the add() command, during the development of my Spectral Music Player mod. Recently, I wanted that the playback of the custom music won't get interrupted by any default music of the game. So I set the priority of the custom music types to 1 but this conflicted with the special music (like level up music) which also has a priority of 1. I believed that giving the special music a priority of 0 would prevent the special music from playing when the situation requests it. The effect was quite the opposite - the special music always played. I removed the changes from the special music and gave the custom music types a priority of 0 instead. When my character made a level up, the playback of the custom music was finally no longer interrupted by the level up music.

I can't see any reason that an empty idle marker could not have a script to start a quest that just has a scene, or maybe just an alias package, that makes the NPC activating the marker go do the whole sequence. I would assume that the sandbox package would get interrupted, and resumed after the mini-quest finishes. But if so, why didn't it get done before?

If anyone knows, stop me before I attempt the impossible.

This is my load order:

  0  0     Skyrim.esm
  1  1     Update.esm
  2  2     Dawnguard.esm
  3  3     HearthFires.esm
  4  4     Dragonborn.esm
  5  5     ccBGSSSE001-Fish.esm
254 FE   0 ccQDRSSE001-SurvivalMode.esl
254 FE   1 ccBGSSSE037-Curios.esl
  6  6     ccBGSSSE025-AdvDSGS.esm
  7  7     Unofficial Skyrim Special Edition Patch.esp
  8  8     FloraRespawnFix.esp
  9  9     Weapons Armor Clothing & Clutter Fixes.esp
 10  a     Cutting Room Floor.esp
254 FE   2 Qw_WACCF_CRF Patch.esp
 11  b     Run For Your Lives.esp
 12  c     Bring Out Your Dead.esp
Also can anyone tell me why the mod "Bring Out Your Dead" is no longer on the Nexus?

That is, more than one type of item is made, as multiples of a single item already exists, e.g. leather strips. It would have at least two uses: bonus items and deconstruction. My initial implementation wants to allow grain milling to result in both flour and straw, but I want to create a generic method. The idea is to borrow from hearthfire’s token system to run a script on the combo result that splits out the components when it enters the player’s inventory. It’s obvious enough that I expect it already exists, but can’t find it.

The tl;dr is this: A quest unique to your mod with new dialogue lines in it will not run the dialogue unless you save/reload the game. Even quicksave/quickload works. The solution was to generate a .seq file to distribute with the mod and all was well.

Somewhere along the way this solution has stopped working. Mods with generated .seq files are (at least for some of us) not firing off their dialogue anymore despite the use of these files. Only this time the problem is not limited to us. In SSE, even the base game files now have this same problem. This can be quickly checked by starting a new game, going to Windhelm, finding Sofie over by the gate and trying to talk to her. If everything works as expected, she'll try to sell you flowers. If not though, all she'll do is give you generic "hmm?" style responses with no other dialogue. If you then save and reload the game, all is well.

Bethesda will have to fix their own broken stuff at this point as fixing these in the USSEP is simply not viable (nor would it work anyway).

For the rest of us, as long as there are not too many quests flagged as "start game enabled", there's a solid workaround. You can either set a trigger box up somewhere the player can't avoid walking through, or set up a control quest with an OnInit() event that then calls startup on everything else you need to have done. So long as the quests with your dialogue have those startup calls issued *after* the game starts, this should work fine. It's a shitty workaround to an even shittier problem, but there's no way to know if BGS can or will fix this on their end even though it affects both the base game and all of the CC DLCs that have these kinds of quests running.

The weird part about this is, reports of this behavior go back as far as March of 2019 yet are not widespread or even consistently reproducible. For instance, until I finished my system upgrade tonight, I was unable to verify this problem because all of my game dialogue worked in all cases. Now, after a fresh Windows install and restoration of my game files, it is broken unless I do the save/reload thing. Go figure on why that might be, but there it is.

Oh, and just in case someone was thinking it, no, deleting the .seq file doesn't help. I tried

Flag Types

Plugins can have 3 different flag types: ESP, ESM, and ESL. This causes them to load in different ways, and in some cases handle their form IDs different from the old ways.
ESP files are standard every day mods. There will be no type flag set on these and they have the .esp file extension. Mod managers all know how these work and various modding tools consider these to be the basics of modding.
Files flagged with ESM are commonly referred to as "masters". They load early, immediately following the 5 hardcoded official files and any Creation Club content you may have.
Files flagged with ESL are known as "light plugins" or "light masters". How these load is determined by their file extension. The exception being any Creation Club content you may have downloaded. Those files load immediately following the 5 official files, according to the order they're listed in the Skyrim.ccc file.

File Extensions

The engine treats files in a certain way based on their file extensions:

A .esm file extension will always be treated as a master file. The ESM flag will automatically set in memory.
A .esl file extension will always be treated as a light master. The ESM and ESL flags are automatically set in memory.
A .esp file can function as either type of file depending on which flags are set in its file header. If the ESM flag is set, then the .esp is treated as a master file. If the ESL flag is set, it will be treated as a light plugin. If BOTH flags are set, then it is treated as a light master.
It is important to note that as far as the game is concerned, a .esp file with no ESM flag will load as a normal .esp file would. All standard load order procedures apply to them, and any properly functioning mod manager should handle them the same way it does regular .esp files.

The Golden Goose

Files with the ESL flag are given special treatment with their form IDs. Upon loading into the game, the form IDs are remapped into the FE mod index. This is now considered a special slot in SSE and should not be occupied by any mods in your load order. Not even the Bashed Patch or any other form of merged data.

As a result of this new support, the engine can allow you to bypass the previously hard limit of 255 plugin files. The theoretical limit now should be 4096 ESL flagged mods. Individual files flagged as ESL can in theory hold up to 4096 form ID records. In practice this ends up actually being 2048 form ID records because the engine reserves everything from $0x0000 to $0x07FF. All files using ESL flags must therefore contain their internal form IDs between xx000800 and xx000FFF. Anything exceeding this range is invalid and the game will either crash or you'll have severely corrupted data due to overruns.

The reason for this is how the mapping works. We're all familiar with the normal 8 digit form ID. The first 2 digits are only used to handle load order, the other 6 are internal to their plugin file. What the ESL flag system does is it break this down even further. The First 3 digits get mapped into an internal table for the FE slot. The remaining 3 belong to the actual records in the plugin. You'll end up with something like this:

FE000800 - FE000FFF ModFile1
FE001800 - FE001FFF ModFile2
FE002800 - FE002FFF ModFile3

FExxxyyy and so forth up until you reach FEFFFFFF and run out of IDs and mappings. This is where the 4096 files and 2048 form IDs per file comes from.

The benefits of all of this should be fairly clear. No more need to merge the 20 weapon mods with 5 records each. Just flag them with ESL and you're good to go. This is much safer than merging and is fully supported by the game engine so it works the same way for everyone.

Other Information

Using ESL flagged files come with some important issues to consider:

• You must be playing on a copy of SSE version 1.5.3 or newer in order to use ESL flagged files.
• You must be using a copy of the SSE CK version 1.5.3 or higher in order to properly recognize these files for editing.
• The file cannot contain more than 2048 records in it or the form IDs will overflow into another FE slot and corrupt the save.
• Form IDs need to be compacted for the file to be considered valid. The CK has an option called "Compact Active File Form IDs" in the file menu. xEdit also has a function for this. When using either of these, PAY ATTENTION TO THE WARNINGS.
• You cannot compact IDs on a file you intend to continue using in an existing save or you WILL corrupt it due to the form IDs contained within it being rewritten. Only do this on files you have not yet begun using, and which do not yet exist as public releases.
• Other mods which reference form IDs in the mod you are compacting (compatiblity patches, script calls, etc) will break if you compact the form IDs on a mod that's been released to the public.
• NMM does not work with files that have the .esl extension or carry an ESL flag. It has been reported to completely lock up if even one of these is present in your Data folder. Use a functional mod manager such as Wrye Bash to manage these types of mods.
• If by some wierd twist of fate you end up with a ESL flagged file that's also ESM flagged and someone uses a standard .esp file as a master to it for some reason, that file will be forced to load into the wrong part of your setup. Normally a standard .esp file will never load before anything ESM flagged, this is the one exception to that now and it should be considered a bug to report to any mod's author who has done this.
• DO NOT attempt to patch anything inside of a CELL record that originates with a file flagged as ESL. Doing so will cause the cell to break and not load most of its contents when you enter it. This includes any official Creation Club content you may have. It doesn't matter who made the file, it will break.
• Mods that use the GetFormFromFile() function in their scripts to reference things within them cannot be compacted unless the scripts are also recompiled with the new form ID.
• Mods using recorded voice lines or that include NPC facegen data cannot be compacted because all of those asset files will need to be manually renamed to match the new dialogue and NPC form IDs.
  

This post will be updated again as needed to reflect new information that may be uncovered.

I'm just cleaning all the master esm's from Update through to my CC content. I was just curious when I saw that you had to manually remove a conflict in Dawnguard which flags up orange/yellow. My question is, is it safe to remove all conflicts that are flagged up orange/yellow in xEdit?

Default Object Manager

DOBJ - DNAM [Objects]: ElminsterAU has confirmed that this record merges its data at runtime, therefore conflict management on this record if it exists in a mod is unnecessary.

Dialogue Subrecords

DIAL - TIFC [info Count]: These will appear as conflicts whenever the counts don't match. So far as I have been able to determine, the game will keep track of the highest count and will run with that. It's also possible this subrecord doesn't matter in the end and is only for internal information purposes as this count value is never seen in the CK.

INFO - PNAM [Previous INFO]: These will be sorted at runtime based on the actual order of the final list of INFOs attached to a DIAL record.

Story Manager Records

SMQN - SNAM [Child] subrecord: The children specified in these subrecords will process correctly even if the display appears to indicate they won't. This can be pretty clearly demonstrated by the vanilla game and the Dawnguard DLC. There are SNAM conflicts there suggesting that Dawnguard would block the connections but the game operates them properly anyway.

SMBN - SNAM [Child] subrecord: As with the equivalent in the SMQN subrecord, these also sort themselves out at runtime.

Location Records

LCTN - Location record: As displayed in TES5Edit, everything from ACPR all the way down to LCEP will merge with each other at runtime. Conflict resolution for these subrecords is not necessary.

All LCTN Subrecords from FULL [Name] to the bottom of the list DO require conflict resolition, as well as everything from EDID [Editor ID] up to the top of the record.

Idle Animation Records

IDLE - ANAM [Related Idle Animations] subrecord: This data is sorted out at runtime. ALL OTHER DATA in the IDLE record must be conflict resolved.

Worldspace Records

NAM0, NAM9 subrecords: Used to determine the in-game cell dimension of a worldspace. These have been confirmed to be exempt from the Rule of One. *ANY* mod making changes to these sets of values will have those changes propagated into the game WITHOUT conflict management. Be aware of this if you are running two mods together which intentionally change these values for a worldspace. The outcome will not be predictable and you may end up with a worldspace size much larger than you're expecting. This can lead to huge amounts of stuttering in the game that have no other identifiable cause. If you have mods which are altering vanilla worldspaces, chances are these edits were NOT intentional unless the author specifically states they have done so. They can appear in a mod unintentionally and the author may not be aware it has happened.

Navigation Mesh Info Map

NAVI - This is a special case record that will exist in any mod which has navmesh edits. Each mod will have this record listed as form ID 00012FB4. All of the data in each mod that has a NAVI entry will be merged at runtime. Conflict management is therefore not necessary, and likely wouldn't be possible anyway due to the complexity of the record.

NOTE: This information is identical to the original post for Skyrim Classic/LE except for the QNAM subrecord data in the Story Manager. At some point those records stopped merging at runtime and therefore WILL require conflict resolution of some sort.

Papyrus.2.log

1. Does anyone know how this is done with these books?

2. Does anyone know how I can stop the animations on an object reference?

So how do I make the weapon twohanded?

Chesko Array Resources
General-purpose Array Functions
Beyond 128: "Extended" Array Functions to go to 512 and up
[]
[]
[]

;=============================================================================================================
                                               ;ARRAY FUNCTIONS
;=============================================================================================================

Int function TestSortCount( Int i = 0)
;Author: Dragonblood

int len = QuestBooks.Length
bool IsFound
int EmptyPosition
int c
while i < len
If QuestBooks[i]  
  If IsFound
    QuestBooks[EmptyPosition] = QuestBooks[i]
    QuestBooks[i] = none
    EmptyPosition = EmptyPosition + 1
    i = i + 1
    c = c + 1
  Else
    i = i + 1
    c = c + 1
  EndIf
Else
  If IsFound 
    i = i + 1
  Else
    IsFound = true
    EmptyPosition = i
    i = i + 1
  EndIf
EndIf
EndWhile
Return c
EndFunction

Here is a function for sorting reference aliases.  It should work as is but I did not test it as I am not going to be using it now. It does compile.

    Int function SortandCountRefAliases( Int i = 0)
        ;Author: Dragonblood
        
    
        bool IsFound
        int EmptyPosition
        int c
        while i < BAL ; The length of the array or the filled positions.
        ObjectReference B = BooksAlias[i].GetReference()
        If B
          If IsFound 
            BooksAlias[EmptyPosition].ForceRefTo(B)
            BooksAlias[i].Clear()
            EmptyPosition = EmptyPosition + 1
            i = i + 1
            c = c + 1
          Else
            i = i + 1
            c = c + 1
          EndIf
        Else
          If IsFound 
            i = i + 1
          Else
            IsFound = true
            EmptyPosition = i
            i = i + 1
          EndIf
        EndIf
        EndWhile
        Return c
        EndFunction

Here is an array function for filling reference aliases. 

bool function FillRefAlias(ObjectReference BK)
          
    int i = 0

    while i < 100

    ReferenceAlias r = BooksAlias[i]
     ObjectReference ba = r.GetReference()
        If ba
            If ba == BK
               Return false
            EndIf   
        Else
            If r.ForceRefIfEmpty(BK)
                Return true
            EndIf
        EndIf

        i = i + 1

    EndWhile
          
          Return false
            
      endFunction