0.36.0-pr001

Mo2 Compatibility Improvements

• Better informational error display when Mo2 VFS is failing
• Improved build caching systems
• Setting to proactively block any build style operation when running within Mo2
• Running patchers now executes resulting exes directly rather than dotnet run
• Removed old "Mo2 Compatibility" test setting that wasn't helping much

This suite is meant to enable a "two phase" system. Run synthesis outside mo2 when you want to download new patchers or change their targets requiring a rebuild. Then open in mo2 to tweak settings and actually run the pipeline. The cached builds from earlier will be used when running the patchers, avoiding the need to build from within Mo2.

Master Overflow Handling

• Split Files if Max Masters Exceeded setting
  • Will detect and automatically split the patch mod into several files when the master limit is exceeded
  • Still somewhat experimental

General

• Specialized Error Panes for known error categories

  • Compilation Error — Patcher failed to compile, typically due to API changes in newer library versions
  • Library Version Mismatch — Detected when an older version of Mutagen is paired with a newer version of Synthesis (or vice versa), causing missing method/type errors at
    runtime
  • Compression Error — A mod file has corrupt or invalid compression data; suggests verifying game files or re-downloading the affected mod
  • Missing Mods — Mods listed in the load order could not be found in the data folder
  • Referenced Mod Missing — A record references a mod that isn't present in the load order being sorted against
  • Non-Adjacent Split Mods — Split mod files (e.g. base + DLC splits) are not consecutive in the load order
  • Too Many Masters — The output plugin exceeds the master reference limit
  • File Access Denied — A file is locked by another process during execution
  • Output File Locked — The output patch file is held open by another program (xEdit, Creation Kit, etc.)
  • MO2 Causing Build Errors — Mod Organizer 2's virtual file system is interfering with the build process
  • Ran Build In MO2 — Build was blocked because Synthesis is running inside MO2 with the block-builds setting enabled

• Fix for CLI runs not checking out desired git commit targets

• Removed old settings migration code to upgrade from ancient versions

0.35.5

• Reduced strictness of mutagen version that had to be paired (wasn't allowing upgrade from 0.53.0 -> 0.53.1)

0.35.4

• Mutagen nuget bump

0.35.3

• Mutagen version bump

0.35.2

• Logging output simplified to just current log + past runs that automatically clean up
• Net10 support added
• UI exe itself upgraded to target Net9

0.35.0

• Remove Mutagen.Bethesda as import from Synthesis.Bethesda.Execution. Specific mutagen games desired should be added
• Update mutagen versions to include fix for Language targets with _ in their name

0.34.0

• CETCompat is disabled for synthesis itself and all patchers
  • This should improve the "access denied" errors being experienced in Mo2 More info here and here
• Added AssetProvider to IPatcherState
• Top gear icon now navigates to profile settings, rather than advanced
• Some profile setting color tweaks
• Update to use Shouldly library

0.34.0-pre-release3

• Workspace moved from %temp% directory to current directory alongside exe

0.34.0-pre-release2

• CETCompat is disabled for synthesis itself and all patchers. More info here
• Added AssetProvider to IPatcherState
• Top gear icon now navigates to profile settings, rather than advanced
• Some profile setting color tweaks
• Update to use Shouldly library

0.34.0-pre-release

• CETCompat is disabled for synthesis itself and all patchers. More info here
• Added AssetProvider to IPatcherState
• Top gear icon now navigates to profile settings, rather than advanced
• Some profile setting color tweaks
• Update to use Shouldly library