Welcome to the AFK Mods bug tracker. In order to report an issue, you need to have a VALIDATED account to post one. Once you have followed the link the registration email sent you, please select a project from the drop down menu below. Select “Open New Issue” and fill out the form with as many details as possible.

Please also consider sending your bug report to Bethesda if you are reporting on an issue with Skyrim Special Edition, Fallout 4, or Starfield. Doing so will help everyone on all platforms.

Issue Data
Status: Closed
Issue Type: Bug Report
Project: Unofficial Skyrim Special Edition Patch
Component: Skyrim SE: Dragonborn
Category: Items
Assigned To: Nobody
Platform: All
Severity: Low
Votes: 0
Watching: N/A
Opened By Ethruvisil on Jan 15, 2019 12:15 pm
Last Edited By Arthmoor on Jan 19, 2019 3:15 pm
Closed By Arthmoor on Jan 23, 2019 12:54 am
Resolution: Fixed
Comment: Fixed for USSEP 4.1.7.

Issue #25785: Bloodskal Blade won't shoot energy (save and possible cause)

 
A user on UESP has given a possible reason for the bug where the Bloodskal Blade's special effect doesn't work (which then causes the player to get stuck): It gets replaced by a non-functional, non-quest-item copy if you enter the location and let it reset in 30 days.

This bug has also happened to me (on Legendary Version). The sword can be dropped and doesn't shoot bolts, dropping it doesn't fix it. I can neither confirm nor deny that I had entered Raven Rock Mine before, but maybe the save helps: https://ufile.io/2or4j



Attached Files:

Speichern 384 - Ethruvisil Rabenfels Mine 529.14.45.skse
Related Issues: 25525  25528  

Comments

3 comment(s) [Closed]
Arthmoor said:
 
We're going to need the actual save file. The one you attached is merely the SKSE co-save file which is useless by itself.

Comment #1 Jan 19, 2019 3:15 pm
Ethruvisil said:
 
It's in the ufile.io link in my original post. It wouldn't let me attach it, i think the file was too large.

Comment #2 Jan 20, 2019 12:46 pm
Arthmoor said:
 
Well. Never in a million years would we have suspected the engine would delete a reference stored in an active quest alias, but here we are, and that's what happened. The replacement it spawned on the floor does not get transferred into the alias and once that respawning has happened it's permanently broken on that save. Made worse because you can't guard against this other than to remove the respawn flag from the expected reference. So that's the best we can do is remove the flag and it should stop happening on new games.

Comment #3 Jan 23, 2019 12:53 am
Showing Comments 1 - 3 of 3