Search the Community

This is a question we get on a fairly regular basis, so I think the time has come to consider our options for the future. First off, yes, I know I've been staunchly opposed to unifying the Unofficial Patch under a single all-in-one file to cover everything. Recent events have begun to strain the current model we're operating under though. Some fixes, like certain perks, can't currently be handled by our existing setup without generating a small fix file to cover these. Currently, the perk fixes are being handled here: http://www.afkmods.com/index.php?/files/file/1212-dg-and-db-axe-perk-compatibility-fix/ Another issue just reported involves incorrect dragon skeletons when a dragon dies: http://www.afkmods.com/index.php?/tracdown/issue/16721-dragonborn-serpentine-dragons-inappropriate-mesh-when-dying/ - In order to address this, the DragonActorScript would need editing, and such an edit can't currently deal with DG dragons while preserving the DB dragons and the Miraak support code. A third issue is one that's been brought up before, but so far hasn't been formally reported - It's not possible currently to support adoptions on Solstheim because it would necessitate code that alters two DLCs. Technically it can be considered a bug that you can't even move your spouse to Raven Rock. It's pretty easy to see why Bethesda didn't even try. In general, any inter-DLC issues that come up can't currently be managed. Then there's the general difficulty in maintaining the separate packages as they are now. Each one requires a clean environment from which to work, which right now is only truly possible by having multiple Skyrim install folders that get switched between as each patch runs its cycle. Conflict resolution with this setup is made difficult because such conflicts can only be checked with every file in the same folder, and it's not wise to dirty up each folder with stuff from another. One major downside to all this is that removing the existing DLC patches from a running game could very well break things. There would be no other good way to go about this though (thank God we're using BSAs!) that wouldn't potentially cause some problems. Something that will need to be kept in mind. This changeover would mean the end of continued development on the current separate files. It is not feasible to manage the project in two entirely different branches. This would not affect the High Resolution patch. That would remain separate since it isn't dependent on certain DLCs existing or not and the content isn't something everyone can run. So briefly: Pros: No more need for multiple development folders. No more unresolvable conflicts. One unified patch that only takes up one ESP slot. Cons: Not everyone has every DLC yet. A significant amount of work to properly merge everything into one unified ESP. Support on the existing separate patches would be frozen except for hotfix issues. Extremely likely that the game could get confused when ripping out the unsupported DLC patches when a change like this is made. Again, as I once said, "hell no, never" - well. It's starting to become enough of a hassle to consider it. But, as these patches are largely for the sake of the community, I think it should be put to a poll. So please cast your vote, and post your thoughts on why we should or should not do this.