Every now and then, I am receiving the "x misses y TOTO" log message (see screenshot).
I am assuming that this is due to the fact that I am experimenting with the Ogre's ability to dual-wield two-handed weapons, and the associated "hit penalty" debuff, but that's not at all clear from the message.
(Incidentally, I also think the descriptions of the debuff and the level 5 talent could be clearer - is this penalty to hit applied after the acc/def calculation or before, for example?)
[1.3] Odd log message for "hit penalty" debuff
Moderator: Moderator
[1.3] Odd log message for "hit penalty" debuff
- Attachments
-
- tome-1.3.0-1423501980.png (30.07 KiB) Viewed 1187 times
Re: [1.3] Odd log message for "hit penalty" debuff
Well, there's not really a difference, overall hit chance is a product of individual hit chances either way.
Re: [1.3] Odd log message for "hit penalty" debuff
Don't know about the rest but TOTO is an obvious Wizard of Oz Easter Egg. Now that we have ogres in the game we're not in Kansas anymore.
On a more serious note, line 446 in Combat.lua
self:logCombat(target, "#Source# misses #Target# TOTO.")
On a more serious note, line 446 in Combat.lua
self:logCombat(target, "#Source# misses #Target# TOTO.")
Re: [1.3] Odd log message for "hit penalty" debuff
Sure, just logging it under the assumption that you don't want to release that "Easter egg text" in the final version.
I wonder if this would all be clearer if the penalty was applied directly to accuracy, so that you could see the effect on the character sheet and not just wonder about a nebulous debuff message?
I wonder if this would all be clearer if the penalty was applied directly to accuracy, so that you could see the effect on the character sheet and not just wonder about a nebulous debuff message?
Re: [1.3] Odd log message for "hit penalty" debuff
There's no way to make it fixed then, though.
Re: [1.3] Odd log message for "hit penalty" debuff
I don't understand the mechanics around this so I'll defer to your judgement!
I was really logging the combat log text issue, and just trying to sneak another observation in under the radar, but if it's difficult to implement then I think the hit penalty works just fine "as is".
I was really logging the combat log text issue, and just trying to sneak another observation in under the radar, but if it's difficult to implement then I think the hit penalty works just fine "as is".