#Requiem boss load order mod#
#Requiem boss load order update#

It therefore became evident that we should split it into several smaller records that can be handled more easily. While this whole setup did its job very reliably over the last years, this record has been the source of several almost merge-failures that could have had serious consequences.

#Requiem boss load order update#

This вЂњquestвЂќ is really the control center for all our core scripts and manages the ingame installation as well as update processes. Those who dared looking into Requiem.esp might have already met this gargantuan quest record called REQ_Quest_Playerscripts. How will the installation process change in the new version?ДЄn important tech debt weвЂ™re tackling in 4.0.0 is the core scripts suite. These changes will be the main topic of the next developer diary.

#Requiem boss load order mod#

Requiem 4.0.0 will also bring a variety of changes and improvements that are intended to make the lifes of mod authors building patches and extensions on top of Requiem easier. Various assets are removed from Requiem вЂ“ the question вЂњwhy?!вЂќ will be answered in detail in this blog post. The ingame installation of Requiem is simplified.ДЄ variety of smaller bug fixes and improvements that have been reported by the community. Tweaks to creature resistances вЂ“ Draugr and Dragon Priests have less inherent blunt damage reduction, Dwemer Centurions and Enchanted Spheres less inherent slash damage reduction. Melee guards will use armors from Varied Guard Armor instead of the steel plate armors they used so far. As such, it will not bring any new game mechanics for players, but there are nevertheless some noteworthy changes: Requiem 4.0.0 is mostly a cleanup release to finally bring us into the position of being able to port the mod to SSE in a way we are confident with. They can first update their content to be compatible with 4.0.0 on Oldrim and then later port their own work to SSE to work with Requiem 5.0 without having to adjust the logic again. This release strategy will also make it easier for mod authors building patches and extensions on top of Requiem to bring their work to SSE.

To not postpone some necessary internal changes by several months, we therefore deciced to first publish a new major version on Oldrim with all the changes we need and then use it as a starting point for our port. Obviously, releasing another breaking release shortly after migrating to SSE would cause a lot of frustration when people who just started the new version on SSE cannot update without starting yet another new game. The migration to SSE will anyway be a savegame-breaking release, but we donвЂ™t want to make the transition more complicated than necessary by mixing up actual changes and migration efforts in one release. Requiem 5.0.0 on Skyrim Special Edition вЂ“ contentwise identical to 4.0.0, this will be our initial release on SSE Requiem 4.0.0 on Oldrim вЂ“ a preparatory release for our SSE port, itвЂ™s content and purpose are the topic of this blog post

Requiem 3.4.0 is the last content release we have planned for Oldrim and was released on the 29th of December 2019. Why will Requiem 4.0.0 be released on Oldrim? I want to take this opportunity to explain why we decided to have a last Skyrim Legendary Edition (henceforth вЂњOldrimвЂќ) release that will of all things be a major, save-game breaking release. This is certainly something we will consider once we have accumulated enough feedback from different users.Д«ut for todayвЂ™s developer diary, we have a different topic: Requiem on the way to SSE and the detours weвЂ™re taking. On the other hand, weвЂ™re also seeing comments that may indicate that weвЂ™ll have to fine-tune the balance a bit in future releases. From what weвЂ™ve seen so far at the forums, it seems that most of you like the new design and behavior of these endgame encounters a lot more than the old version. ItвЂ™s been a bit more than three weeks since we released Requiem 3.4.0 and with it the Slighted, the successors of the dreaded Invisible Entities.