Issue Data
|
Issue #18826: Honningbrew Mead Barrels persist after Dampened Spirits
After Dampened Spirits all of the interior mead barrels are changed into black-briar mead variant, however the barrels outside the Meadery don't change upon completting the quest.
In 'HonningbrewMeaderyExterior01' Ref: (0007f83b) (0007f841) (0007f866) (0007f867) should be changed into Black-Briar variant upon completting Dampened Spirits (TG03). Further more, shouldn't the name of the map mark, the Meadery itself, the Basement and the Boilery change from "Honningbrew" to "Black-Briar West" like it is suggested in the dialogues with Mallus? |
Fixed for USKP 2.1.1.
1) Added Black Briar Mead barrels (0200284C, 0200284D, 0200284E, 0200284F) and added the correct enable parents to them and the Honningbrew Mead barrels like was done in the interior areas.
0007F866 and 0007F867 were mistakenly missing their "encounter zone" setting.
None of the barrels have their ownership set either; which was likely an error considering that the ones in the interior do.
2) The naming of the meadery and its other zones can't be fixed by the USKP; it would require using a SKSE script which is outside of the project's scope. (Reference - <a data-ipb='nomediaparse' href='http://www.afkmods.com/index.php?/tracdown/issue/18020-honningbrew-meadery-name-change-after-tg03/'>Bug #18020</a>
1) Added Black Briar Mead barrels (0200284C, 0200284D, 0200284E, 0200284F) and added the correct enable parents to them and the Honningbrew Mead barrels like was done in the interior areas.
0007F866 and 0007F867 were mistakenly missing their "encounter zone" setting.
None of the barrels have their ownership set either; which was likely an error considering that the ones in the interior do.
2) The naming of the meadery and its other zones can't be fixed by the USKP; it would require using a SKSE script which is outside of the project's scope. (Reference - <a data-ipb='nomediaparse' href='http://www.afkmods.com/index.php?/tracdown/issue/18020-honningbrew-meadery-name-change-after-tg03/'>Bug #18020</a>
Showing Comments 1 - 1 of 1