Doesn't work at all. I'm playing skyrim LE using moonlight tales + bloodmoon rising, I made sure I installed the bloodmoon rising plugin but It's giving me a lot of bugs, somehow this mod prevents specifically moonlight tales werewolves from spawning correctly, the NPCs don't turn into werewolves anymore, what the heck is going on? It does add killmoves for werewolves but it conflicts too much with moonlight tales.
I have tested this mod extensively, spawning numerous npcs (werewolves and victims alike) and I have tried it with all other mods disabled and this mod in combination with others. Out of about 50 killed npcs I only saw a killmove once, and I have repeated that scenario a dozen times. Any idea how to fix it?
Been testing version 2.2 with the Growl patch (2.0) and didn't see any killmove... I spawned werewolves all over Solitude and watched them devastate the city, just normal attacks
Ahh, my biggest apologies... It was a major screw-up on my end, I had forgotten to flag my main plugin as a master file before I re-saved the VioLens patch with the Oldrim CK. I only play on SSE, and someone else confirmed that the VioLens patch worked on that version. Anyways, I appreciate you bearing with me, I hate how I can sometimes be careless at times.
No problem! Let me know if it worked this time. The least thing I want, as a modder, is to be accused for false advertizement due to unintentional errors. (You downloaded the v2.2-fixed, yes?)
An unmodded game is normally running around 6500 scripts at any given time. A stable modded game can have tens of thousands. There's nothing wrong with scripted mods. And as far as optimization, although I think this could use some, the Bethesda provided scripts aren't exactly marvels of coding. A lot of modders code better than Bethesda's "experts" do.
Just something to consider. My main reason for wanting more optimization is that I run with lots of werewolves, both friendly and hostile, so my game experience needs this to be quicker than most. An otherwise normal game would likely have no issue with the script being used here, even without any update.
Thanx! I´ve been testing it for a couple of hours but none of the werewolves I spawned did any finishing move so far. I unleashed some in Whiterun and Solitud and they did just normal killings...
Hmm, yeah, it seems very rare. Main reason is because the killmoves are conditioned (by Skyrim itself) to only happen 30% of the time, so even if the mod asks for one, it doesn't show up reliably.
I patched the killmoves to happen every time and they showed up reliably, but I dunno if the author wants to do that since it can cause incompatibilities with combat/killmove mods.
Okay, did some high-volume testing on this. Main contributors to unreliable effects are: 1) Vanilla Skyrim records for killmoves only having a 30% trigger chance. 2) The script for this is looking for the werewolf to be within 5 hits or so of a kill before triggering. Increasing that value (maybe through a global?) Greatly increases the chances, but makes werewolves much more deadly than they should be.
Removing the trigger chance from the killmoves and switching the script to an enemy that is within 10 hits (or maybe better: under 10% health) produces very reliable kills. Lots of them.
That script is doing a lot of redundant function calls. IMO far too many for a combat script. A lot of those could be done just once, using combat events to load/scrub the data.
Would recommend using a state for this and checking the global only at the time combat starts instead of every 5-20 seconds. Put some returns in there for stopping if a disqualifier is found. For instance, once cTarget is found, verify that it isn't the same as the last cTarget, and if it is, skip everything until the health check. On starting combat (or first time the script detects combat has begun) check if the cTarget is essential or has ActorTypeNPC keywords, rather than waiting until other actions have happened. These aren't values that will change during combat, so they don't need to be checked every update cycle.
So I tried, and didn't start a new game, just wanted to check out. One thing that was happening was when passing time, saving, or quitting, there was a 30 sec delay where the game freezes before resuming. Maybe I just need to try on a new game?
24 comments
It does add killmoves for werewolves but it conflicts too much with moonlight tales.
I spawned werewolves all over Solitude and watched them devastate the city, just normal attacks
Thanks for keep fixing the mod!
Thanx for another awesome mod!!!
Just something to consider. My main reason for wanting more optimization is that I run with lots of werewolves, both friendly and hostile, so my game experience needs this to be quicker than most. An otherwise normal game would likely have no issue with the script being used here, even without any update.
I patched the killmoves to happen every time and they showed up reliably, but I dunno if the author wants to do that since it can cause incompatibilities with combat/killmove mods.
1) Vanilla Skyrim records for killmoves only having a 30% trigger chance.
2) The script for this is looking for the werewolf to be within 5 hits or so of a kill before triggering. Increasing that value (maybe through a global?) Greatly increases the chances, but makes werewolves much more deadly than they should be.
Removing the trigger chance from the killmoves and switching the script to an enemy that is within 10 hits (or maybe better: under 10% health) produces very reliable kills. Lots of them.
Less conditions. The game already makes it less probable even at a 100% chance of happening.
Would recommend using a state for this and checking the global only at the time combat starts instead of every 5-20 seconds. Put some returns in there for stopping if a disqualifier is found. For instance, once cTarget is found, verify that it isn't the same as the last cTarget, and if it is, skip everything until the health check. On starting combat (or first time the script detects combat has begun) check if the cTarget is essential or has ActorTypeNPC keywords, rather than waiting until other actions have happened. These aren't values that will change during combat, so they don't need to be checked every update cycle.
Looks overall good, just needs optimizing.
Nice change
/correction