Pages

155 posts / 0 new
Last post
llde
llde's picture
Contributor
Offline
Last seen: 2 weeks 3 days ago
Joined: 09/17/2013 - 07:04
Karma: 378
This is definitly a VERY

This is definitly a VERY strange bug.

It's the character you are experiencing this  issues the same character you used to played the bloodmoondebug.esp? Do you played as a werewolf in the last play?

Have you tryed to deactivate that .esp(making a clean save) before updating to v64?

Also you have some other mods that handles combat?

Have you experienced the bug with a new PC? (Try to create a new test pc and play the bloodmoon questline)

The two werewolf quest shouldn't be running when you cured yourself from lycantropy , and belonging to  the werewolf faction doesn't modify combat at all. BUT if you were a werewolf before updating, you should manually start both quests.

Brainslasher
Brainslasher's picture
Contributor
Offline
Last seen: 6 years 3 months ago
Joined: 05/19/2013 - 11:46
Karma: 725
Thanks for answering :)

Thanks for answering :)

The bug only affects this old character. Other characters which started in newer versions and hadn't been through Bloodmoon are unaffected. This character never had Bloodmoondebug.esp activated. Starting with 0.64 also doesn't cause it.  Yes the character was a werewolf in the previous version but got cured with the scroll that I had written which got merged in version 0.60. This leads me to believe I played the questlines in 0.59.

I played with it through the Bloodmoon questline choosing the werewolf path. I had to use a few console commands at times. It's very likely that because of script and quest changes this character is entirely incompatible with this version. However even calling the script functions in the Wolfender scroll as it is now (resetting the quest variables and stopping the quests) from the console doesn't fix the bug. The strangest thing for me is that entering interior cells fixed it temporarily.

I don't have any combat enhancing mods running and the bug even happens with only Morrowind_ob.esm and .esp activated. I'll check if the bug also affects newly created characters after they get cured. I'll also try starting both quests manually to see what happens. I know that this bug is probably extremely rare and the chance of fixing it is low but I'd really like to know what causes it :)

llde
llde's picture
Contributor
Offline
Last seen: 2 weeks 3 days ago
Joined: 09/17/2013 - 07:04
Karma: 378
I changed many variables on

I changed many variables on the scripts. As you also I want to understand what cause this issue.

Maybe your game didn't register correctly all new variables, or there are index clashes. Something that affected the savegame. I changed so many variables. Probably some other scripts are reading a bad variable. Or maybe a variable still has 1 when it should be 0(I'm making hipotesis).

I'm sorry, this is so unlucky. I don't know if this is fixable or not.

If you load your save without Morroblivion activated, the bug is still here?

If not try to make a new save, (don't overwrite, make a easly recognisable name) and reactivate morroblivion. The bug return again?

Please report everythingh you  can.

Brainslasher
Brainslasher's picture
Contributor
Offline
Last seen: 6 years 3 months ago
Joined: 05/19/2013 - 11:46
Karma: 725
Okay, I managed to fix it by

Okay, I managed to fix it by doing the following:

Loaded up a savegame from 0.63a but with the 0.64 .esm with the player in an interior cell. Also loaded a plugin with all questscripts removed from the fbmwBM quests. It also called thesese functions once:

With this the first NPC to attack me in the night just ran up to me without attacking and just kept running into me but after a few seconds he initiated combat as normal. All other enemies after that also attacked normally and setting GameHour to 0 doesn't stop enemies anymore.

The exact reasons are a mystery but one other thing was that the WolfGiver questscript continuously sets these variables to 0 and then stops the werewolf quests again with an FQuestDelayTime of 0.5 even after the quest is finished. This stopped me from trying out certain thhings with those quests.  I also noticed a few of the other quest scripts don't have a doonce check when it would be better to have one.

Maybe I'll check what in particular fixes it but I'm too tired for that now.

Pages