Version 2.5 changes the way the patches are applied and expands on Forger's capabilities.  No released mods require it yet, so many of you may choose to stick with 2.1.1 for now.  If you're a modder or would like to help test this version, please read on.


What's new?

The changes are all under the hood.  Previous versions kept a "clean" (.original) copy of each forge file to use for reference.  It was the best available idea at the time, but caused a lot of problems and confusion.  v2.5 appends changes to the end of the file so the second copy is no longer necessary.  I expect this will be less problematic, and it also expands its capabilities (it removes limitations 1 and 2 from the File formats and Forger article)


Upgrading to 2.5

The first time you point it at a game installation modified by an earlier version, you'll be prompted to go through the upgrade process.

• Forger will replace your .forge files with their .original backups
• You will be asked to verify the game installation using Steam or Uplay.  It's highly recommended you do this to start with a clean copy of the game.
• Forger will reapply your patches using the new method.  This should be much faster than older versions
• You will be asked to rename or delete older copies of Forger.  Combining the old and new methods of applying updates would cause confusing side effects.