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: Dawnguard
Category: Actors
Assigned To: Nobody
Platform: All
Severity: Very Low
Votes: 1
Watching: N/A
Opened By Migck on Dec 22, 2018 9:18 am
Closed By Arthmoor on Apr 1, 2019 1:52 am
Resolution: Not A Bug

Issue #25586: Dawnguard Rune Axe does not consume charge, other changes

 
The Dawnguard Rune Axe has 1000 charge points, yet its enchantment DLC1DawnguardRuneAxeExtraDamage has no charge cost so it lasts forever. Also, as for the effects used in it, DLC1DawnguardRuneAxeDamageEffect is in the Destruction school and has the MagicDamageFire keyword, which it shouldn't considering it's supposed to be like the other Sun Damage effects, plus it can harm friendly undead in its area of effect; and DLC1DawnguardRuneAxeIncrementKills is a scripted effect that can fire on dead actors, since it only checks for the IsChild == 0 condition.

I'm probably tweaking too many things here so perhaps it's more of a feature request, but I'd propose the attached changes to make the axe have 100 base uses for example, and for the effects to be more consistent.



Attached Files:

Dawnguard Rune Axe Uses.zip

Comments

1 comment(s) [Closed]
Arthmoor said:
 
I'm not sure I'd consider any of this evidence of an actual bug. Especially since the enchant cost is set to auto-calc and if their formula says it should come up zero, who are we to say otherwise?

The incrementer calls a script which only runs if the ActorTypeUndead keyword is set. Since it only runs in the OnDying state it should never be capable of working on a corpse.

Comment #1 Apr 1, 2019 1:52 am
Showing Comments 1 - 1 of 1