Lone Wolf Development Forums - Preparing for a New Release

Hey everybody,

If the rest of my testing goes well, you might be seeing version 2.3 of the 5e Community Pack very soon. This is a long time coming, and the major new content includes Mordenkainen's Tome of Foes, the player options from Guildmaster's Guide to Ravnica, and the player options from Eberron: Rising from the Last War (except for the Artificer).

For the standard user, who doesn't do any work in the editor and who hasn't downloaded any pre-release versions of stuff from the GitHub, this release will be pretty straightforward. You'll get the update, pick whatever new sources you want from the Configure Hero screen, and you're off to the (new!) races.

If you have edited the Community Pack files yourself, you might need to take precautions. The update will automatically overwrite any community pack files you have, regardless of if you've made changes. So if you went into the PHB Equipment .user file and programmed a new item, it's going to be overwritten when you update. You can get around this by copying the item (or whatever Thing) to your own unique .user file, one that doesn't share a filename with one of the standard Community Files.

If you have downloaded pre-release material from the Github, this stuff will likewise be overwritten. The one thing to pay attention to is the Eberron stuff. In the official 2.3 update, the pre-release Wayfinder's Guide to Eberron/2018 Eberron content will be converted to the official release. So that Warforged you have with the Envoy subrace selected? You're going to get some errors about a missing subrace.

But don't worry; the pre-release stuff was renamed under a source called Unearthed Arcana - Eberron (2018). If you want to switch over to this to avoid errors when you update, go to the "What about the Pre-Release Versions?" section on this post and follow the instructions.

Once the update is released, we could really use your help hunting down any bugs, errors, or issues missed during pre-release. Post whatever you find to the Github issues board so it can be addressed in the next release which, hopefully, will come a lot sooner.