[3.03] Unlabored Blade's Firebug Not Proccing

[hippofant]

Description:

 

The Unlabored Blade's Firebug ability procs once and only once per combat. Other soulbound weapon procs are working: Stormcaller, Steadfast, and Greenstone Staff all proc their abilities multiple times per combat, both of which proc their on-hit effects given a few swings.

 

 

Output.log is attached, though there's not anything relevant in it as far as I can tell. There are some savegame issues I've been having - my autosaves are from the 14th, the game won't autosave over them, and they keep being dredged up from the depths somewhere every time I delete them so I've been playing without autosaves at all - but nothing within highlights anything to do with the Unlabored Blade I think.

 

 

Here's is a DropBox link to my savegame where Zahua has a fully-leveled Unlabored Blade: https://www.dropbox.com/s/vdvfa6l0w7x93dy/406d009a-9ea4-43e7-b080-1ba6fc036b8b%20quicksave.savegame?dl=0 You can make him attack a party member of go find an enemy to hit; either way, as far as I can tell, the Unlabored Blade will proc Firebug once and only once.

output_log.txt

Edited September 25, 2016 by hippofant

[Sking]

Hey hippofant,

 

I've thrown some love at this issue and I'm getting different results than you. I cannot get firebug to proc at all. I'm going to run around your save and check for difference, but if there is anything else you think may be a factor let me know.

 

I got your back

- Sking

[hippofant]

Playing around with it some more, it looks like it only procs once per load.

 

I loaded a new savegame from Cayron Valley (I am progressing slowly through WMII), stripped Maneha, and then had Zahua attack her with the Unlabored Blade. Combat log screenshot is attached:

 

 

As you can see, there's an early Firebug proc, and then nothing for a really long time. I then took Zahua and attacked a Langueth and some Snow Bears and there were no further Firebug procs - no combat log for those, but yeah. I swapped over to Maneha, had her equip her fully levelled Unlabored Blade (created with IEMod and console commands), and she procced a Firebug once and no more:

 

 

Then I went to Stalwart and had Zahua attack Taena for a bit. No firebug proc for as long as I did it. (The occasional pierce damage Zahua does to Taena is because I forgot to take off his retaliation item.)

 

Output log for this series of tests is attached. Was in unmodded Pillars of Eternity Steam installation, v3.03.1047, but I've been playing with IEMod and the console, so I don't know if that's causing problems. (Can't imagine why it would, but I'm not very familiar with the engine.)

Dropbox link to the save: https://www.dropbox.com/s/uo90719qwrc9nyx/406d009a9ea443e7b0801ba6fc036b8b%2028109233%20CayronsScar.savegame

 

output_log.txt

[hippofant]

I shut the game down, loaded up the same savegame, and this time went right to Taena, to demonstrate that this isn't a location-specific thing. I then demonstrate why I have no future as a game tester, because I promptly kill Taena, forgetting to input NoDamage1. I then load up the autosave that was made after entering the house, and then hit Taena a few times with my rapiers (oops), before switching to the Unlabored Blade. (Also, I forgot to take off the retaliation gear, again.)

 

But again, you can see an early Firebug proc, and then nothing for quite a while. (37 attacks, by my count. Is there a way to pipe combat logs directly to a file so I can just upload them rather than screenshotting?)

 

Then I go over to Renengild's house, take off Zahua's retaliation item because I'm a smartie, make a new save, and I have Zahua attack her a bunch with the Unlabored Blade - no proc. No screenshots because I'm too lazy to provide proof of negative results.

 

However, I then LOAD UP the save I just made again in Renengild's house. Then I have Zahua attack Renengild: boom, Firebug proc (top of 2nd column):



And now, when I check the output_log (attached), there's a line (3675) that says

 

 

ERROR: Ability found activated that should not be activated at this point. Name = Firebug
 
(Filename: C:/buildslave/unity/build/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56)

 

in amongst a whole bunch of text about loading and failing to load stuff.

 

I'll also note that the Firebug doesn't actually seem to do anything. My understanding is that it should do fire damage to the target and other targets, though obviously I have no real experience of it, but no fire damage shows up in the combat logs.

My suspicion, then, is that something's wrong with how the Unlabored Blade's been coded, and the Firebug proc is being activated wrong, and possibly never being terminated. Thus after the first proc, the Unlabored Blade is always "still casting" Firebug, and so it can't activate again, until you save/reload, whereupon the Blade's status is reset. (Just an uninformed guess though; again, I have little knowledge of how the game engine works.)

 

I can't rule out that it's just me though, and maybe I've screwed something up with my modding and console-ing - possibly because I cheated in a second Unlaboured Blade when I wasn't getting any procs? - since other people have, presumably, gotten it to proc, given that there are build discussions about it. I might load up a save from earlier, before I cheated in the second Unlaboured Blade, and see if it makes any difference.

Edit: Link to save game made in Runenhild's home: https://www.dropbox.com/s/t9ob7lst76yl3id/406d009a9ea443e7b0801ba6fc036b8b%2028166512%20RenengildsHouse.savegame

 

Double edit: Am dummy. Accidentally uploaded output_log from modded version of game. I've reproduced the output_log with the firebug error message by attacking Renengild, proccing Firebug, killing her, saving, and reloading it. Changed the save file to match. Loading the save should make the Firebug error message appear in output_log again.

output_log.txt

Edited September 28, 2016 by hippofant

[hippofant]

Loaded up an older save from before I cheated in a second Unlaboured Blade. Levelled it up. Went and hit somebody with it once. Still got just one proc:

 

[Cyseal]

hippofant, that is elaborate testing.

[AndreaColombo]

After all the effort that went into this, it can't be left unfixed!

[Loren Tyr]

My suspicion, then, is that something's wrong with how the Unlabored Blade's been coded, and the Firebug proc is being activated wrong, and possibly never being terminated. Thus after the first proc, the Unlabored Blade is always "still casting" Firebug, and so it can't activate again, until you save/reload, whereupon the Blade's status is reset. (Just an uninformed guess though; again, I have little knowledge of how the game engine works.)

 

Actually, that's probably a fairly accurate guess. GenericAbility's like these do indeed toggle an 'activated' state on and back off again, among other things to prevent them from going off multiple times simultaneously. If for whatever reason it never actually deactivates again you'd get exactly the pattern you demonstrate; other scenario's could give the same pattern of course, but with that line from your output_log.txt this seems far and away the most probable. Raising the question of why it isn't deactivating, obviously, but it's a step.

 

I was toying around a little bit with this yesterday as well, and also noticed that it didn't seem to be doing anything except log 'xxx activates Firebug' (and also only a single proc, at most). Wasn't at it too long and I wasn't sure it was a genuine issue (in one case the target died from that hit, in another it was an ally), but given your experience with it it does seem to be. There is a small possibility that the NoDamage option could be interfering with that somehow (I had that on part of the time as well), though it's not very likely. 

 

This bug is actually reminiscent of one from (I think) the 3.03 beta, where Spellchance procs in general were not working anymore (eg. the Soulbound Scepter and Jolting Touch stilletto as well), only showing the proc in the log. That was since fixed, though; at least for those two, but it must have been a general issue with Spellchance handling.

[Loren Tyr]

Hmm, Firebug is definitely not actually doing anything. Even with NoDamage off and plenty of enemies around, it shows up once in the log but does nothing (Soulbound Scepter Dominate proc still works fine though, even though it uses the same kind of mechanism).

 

Am also not seeing the "Ability found activated" error in the log, but I am seeing an "ERROR: Charged_Spellbind_Biting_Winds_Ability(Clone) doesn't have an associated prefab, but a prefab was found matching the object name." No idea what that's supposed to be attached to, though it might be unrelated to the Unlabored Blade issue.

[Injurious Will]

I can't get Unlabored blade to proc either.  On top of that, I can't get Steadfast to proc Champion's Boon, which is supposedly a 25% chance on kill!

 

I just took out the Skaen temple with a solo rogue and Steadfast did not proc once.  I must have killed 50 mobs. There is clearly something whacky with the way these things are coded.

 

 

[Boeroer]

Agreed!

 

It may also be a flaw in Unity3d.

Edited October 17, 2016 by Boeroer

[BMac]

This willl be fixed 3.04.  It applies only to Firebug and Healing Chain on The Unlabored Blade, and to Despondent Blows on St. Ydwen's Redeemer.  I was able to get Champion's Boon to cast from Steadfast, and it doesn't have the same data problem the other abilities had - but I'll let QA know.

[Injurious Will]

This willl be fixed 3.04.  It applies only to Firebug and Healing Chain on The Unlabored Blade, and to Despondent Blows on St. Ydwen's Redeemer.  I was able to get Champion's Boon to cast from Steadfast, and it doesn't have the same data problem the other abilities had - but I'll let QA know.

Hi Bmac.  I have now gotten Steadfast to proc twice, but the success rate on it seems really, really low vs. the 25% on kill description.  Thanks!

[BMac]

http://dilbert.com/strip/2001-10-25

 

But if you start a new thread and upload your save file, QA can see if there's something different going on in your game.