If anything is broken/not Just Working™/made things even worse, let me know. I've tested this as extensively as I could, but I'm still a novice at scripting and it's entirely possible I've missed something. Still, I'll do my best to fix any issues that may arise.
IMPORTANT IF UPDATING FROM AN OLDER VERSION TO 1.1.0 OR 1.2.0
In case you've downloaded an older version and are updating, there is a chance the script did not get shut down correctly. Use ReSaver to verify if dunFolgunthurBossBattle is still active in your save. If you don't see it, then everything is fine and you don't need to do anything else. But if it is still active, do this: Uninstall the old version -> Load your save -> Make a new one -> (Recommended) Clean the save you just made with ReSaver -> Install the latest version -> Load the save you just made.
Nexus ate the changelog, so I'm posting it here: - Safe to update mid game from 1.1.0 to 1.2.0. If updating from an earlier version, read the sticky. - Fixed some leftover Papyrus errors in the logs. - Removed the need for an ESP, main file is now only the fixed script. The ESP used until now has been relegated to the optional files to reduce bloat and is used only for stopping the script on running saves. If you have installed a previous version of this mod, you will get a warning about a missing ESP, but it should be fine to continue without it. If you're not feeling sure, just install the optional file as well which is basically the same as the main 1.1.0 file.
Having noticed that the script is in fact stuck on my save, I've installed the script fixer yet it does not appear to be working. I've even gone back to Folgunthur directly and waited for ten or so minutes without success. Is there any idea of what could be going wrong?
I did some more optimizations to bring it in line with the rest of my mods now that I have more knowledge of how scripting works. Functionality, you won't notice a difference.
i installed the latest 1.20 overtop 1.10 and i'm seeing this in paplogs... Line 294: [05/02/2023 - 03:17:22PM] warning: Property MikrulObj on script dunFolgunthurBossBattle attached to alias Mikrul on quest dunFolgunthurQST (0004CEDE) cannot be initialized because the script no longer contains that propertyLine 767: [05/02/2023 - 03:17:24PM] warning: Property MikrulObj on script dunFolgunthurBossBattle attached to alias Mikrul on quest dunFolgunthurQST (0004CEDE) cannot be initialized because the script no longer contains that propertyLine 971: [05/02/2023 - 03:17:47PM] warning: Variable ::MikrulObj_var on script dunFolgunthurBossBattle loaded from save not found within the actual object. This variable will be skipped.
================= they weren't there before. is it an issue or will they disappear after awhile? it's been a few save sessions
That's a side effect of me removing the ESP in the latest version. If you're updating from an earlier version the game is expecting a property that was there before with the ESP, but can't find it anymore in the script and is telling you that it's being skipped.
If the game is still complaining about that it means you most likely still have the ESP from the previous versions in your load order. Make sure you updated by removing the previous version and then adding the new one. Don't do a merge operation in your mod manager, as the lack of ESP in 1.2.0 is intentional - always update mods by either deleting the old version and then add the new one, or let your mod manager replace the entire mod folder. Even if you don't do that, these warnings are completely harmless in this case and you can safely ignore them.
would it be safe to update mid-game if i've never gone near the area or started the amulet quest? First time updating a mod without starting a new game, so i want to make sure I don't bork it ahah
Yes, should be safe. If you want to be 100% sure, download both the main and optional file and install them separately. This will bring the mod to the same state as 1.1.0 which is what the game is expecting.
It was a joke. This mod will unstuck the script by killing all leftover draugr one by one in the background. If you happen to be in the Folgunthur boss fight arena when that happens, you will see the thralls bursting out of the coffins and then dying. But if you install Sharpest Draugr In The Shed, this experience will be greatly enhanced. :)
This mod will unstuck the script by killing all leftover draugr one by one in the background. If you happen to be in the Folgunthur boss fight arena when that happens, you will see the thralls bursting out of the coffins and then dying.
For some reasons, It’s not happens in my game, if anybody have same situation, uses the Controls kill all the thralls on the inside the coffins, get off the stuck script s*** in your savedata, and thanks ferrari365.
i had checked yesterday w/ resaver and i did not have this script stuck in my save, but i installed ver1.0.1 anyway for a new game later. can i just overwrite ver1.01 script w/ this latest? or do i need to do the clean save, resaver thing?
36 comments
In case you've downloaded an older version and are updating, there is a chance the script did not get shut down correctly. Use ReSaver to verify if dunFolgunthurBossBattle is still active in your save. If you don't see it, then everything is fine and you don't need to do anything else. But if it is still active, do this:
Uninstall the old version -> Load your save -> Make a new one -> (Recommended) Clean the save you just made with ReSaver -> Install the latest version -> Load the save you just made.
Nexus ate the changelog, so I'm posting it here:
- Safe to update mid game from 1.1.0 to 1.2.0. If updating from an earlier version, read the sticky.
- Fixed some leftover Papyrus errors in the logs.
- Removed the need for an ESP, main file is now only the fixed script. The ESP used until now has been relegated to the optional files to reduce bloat and is used only for stopping the script on running saves. If you have installed a previous version of this mod, you will get a warning about a missing ESP, but it should be fine to continue without it. If you're not feeling sure, just install the optional file as well which is basically the same as the main 1.1.0 file.
Line 294: [05/02/2023 - 03:17:22PM] warning: Property MikrulObj on script dunFolgunthurBossBattle attached to alias Mikrul on quest dunFolgunthurQST (0004CEDE) cannot be initialized because the script no longer contains that propertyLine 767: [05/02/2023 - 03:17:24PM] warning: Property MikrulObj on script dunFolgunthurBossBattle attached to alias Mikrul on quest dunFolgunthurQST (0004CEDE) cannot be initialized because the script no longer contains that propertyLine 971: [05/02/2023 - 03:17:47PM] warning: Variable ::MikrulObj_var on script dunFolgunthurBossBattle loaded from save not found within the actual object. This variable will be skipped.
=================
they weren't there before. is it an issue or will they disappear after awhile? it's been a few save sessions
If the game is still complaining about that it means you most likely still have the ESP from the previous versions in your load order. Make sure you updated by removing the previous version and then adding the new one. Don't do a merge operation in your mod manager, as the lack of ESP in 1.2.0 is intentional - always update mods by either deleting the old version and then add the new one, or let your mod manager replace the entire mod folder. Even if you don't do that, these warnings are completely harmless in this case and you can safely ignore them.
So I really need "install Sharpest Draugr In The Shed"? This is not a joke?
For some reasons, It’s not happens in my game, if anybody have same situation, uses the Controls kill all the thralls on the inside the coffins, get off the stuck script s*** in your savedata, and thanks ferrari365.