Jump to content

Ronin@

Members
  • Posts

    134
  • Joined

  • Last visited

Everything posted by Ronin@

  1. According to item description it should be 5.0 sec. It's 4 here even though I have 17 Int , if that matters: Randomly it gets cut in half:
  2. Here's another example of queued actions getting stuck: https://www.dropbox.com/s/8wnvjwi6un3bo2t/PillarsOfEternity%202016-05-23%2005-29-39-48.avi?dl=0
  3. I was actually protected but could attack and cast normally.
  4. Desintegration DoT is also inconsistent with the description. It says 330 damage for 21.8 sec but does 53 damage per tick which amounts to quite a bit more than 330. Here's an example:
  5. Hmm. I get 44 crit against both 11 DR and 14 DR. There's definitely something wrong with this spell.
  6. Hmm. Tried it and everything seems to work perfectly. Any damage <0.5 = 0 dmg and any damage in the range of 0.5-0.99=1, just as it should be. The rounding is still the same as any other. Sure, the displayed number is different but it's a triffle as it's quite rare to see such low numbers during a regular playthrough anyway. The chanter still has a lot of issues. It's quite a new concept so it needs more work, no doubt about that. As for you answer to my original problem - it's not supposed to be a DoT, even if it is, why do I do 44 Crit damage to someone with 11 DR?
  7. Oh, I thought you said the total damage doesn't change, not the damage per tick. Why would say that a DoT Crit leads to lower damage most of the time then? Anyways, as I said, it's not always divided into 3 sec intervals. Sometimes the remaining < 3 sec get one more tick that does somewhat random damage (can't figure out the formula yet). Still, the total crit damage ends up in the range of about 124-129% which is kind of unerwhelming considering the increased duration too. I'm pretty sure 13.9 doesn't get rounded down to 13. DR could be decimal number too. It doesn't need to be rounded as it's not important. You only round off the total damage as you can't have decimal HP values.
  8. The "display" and the "reality" are different ? I thought the displayed number on top of the unit is always the real one. Can you give me an example where that's not the case?
  9. Hmm, are you sure about this? DR.0.25 for each tick? The way I see it DoT formula is pretty complicated. Yes, the ticks are 3 sec apart but sometimes it adds one last tick at 0 sec, other times it doesn't. In my example there was no "0.0 sec tick" even though there were 0.3 sec left from the 9.3 sec duration. This means that 1.9 is unexplainably missing. Unless... each tick gets rounded and 1.9 damage is the total remainder from the rounding of the 4 ticks. And since Crits don't increase damage, contrary to what combat log displays, does that mean grazes are actually better than crits ? This is just not right... Edit: Did a test with my animal companion. 19 Corrode DR, 4 ticks x 13 damage = 71 damage instead of 74.4. Now... even if these 13 damage ticks are actually 13.49 it still doesnt add up to 74.4. We're obviously missing something here. It would be nice if someone could shed some light on the whole DoT thing.
  10. It just makes no sense. It's supposed to be 33.3 damage but it's 30 instead. Not sure why it ignores DR too. These guys had 13 fire DR.
  11. It's not just a combat log bug. As you can see it does 17 damage with the first damage tick. 4x17 =68. I'm supposed to do 74.4. DR seems to apply inconsistently every time I use a DoT but let's assume it's applied to the total damage. This guys's Corrode DR was 4.5 so the damage applied is still off, even by a little bit. Edit: Did some tests and DoT ticks seem to take into account the momentary stats of the caster, not the ones when he initially cast the spell. Not sure if this is intended or not but I figured I should mention it. I'm not sure but I think duration changes too. Edit2: Crit DoT damage isn't 150%. Watched it do 5 ticks x 14 damage + 1 tick x 7 damage = 77 damage vs corrode DR 16 which means I did 93 total damage. My normal Dot Damage was still 74.4 so the Crit actually amplified my DoT damage by exactly 25%.
  12. First of all Reaping Knive's damage is wrongly calculated. Combat log says 16 damage, real damage is 18. I didn't have any buffs apart from the burning weapons song. Also, the Concelhaut pet takes my animal companion's name for some reaon. 30% of damage dealt as focus to caster is actually still ~50%:
  13. Thank you Kaylon, but I think there's more to that. Check these out: ---------------------------------------------- Apparently the first time it activates it doesn't work at all. The second time it activates it increases both Min and Max damage by 20% (and it's based off of base damage+might+weapon quality), not 25 as it should. It's either that or it takes just base damage+weapon quality as a base and adds 25%. Either way it shouldn't be like that.
  14. It's possible but I think I remember seeing more than 1 on one of my playthroughs. Don't have a save anymore though.
  15. The helm grants +5 corrode and freeze damage reduction but gets suppressed by my Shroud of Mourning granting +3 to these two reductions:
  16. Just wanted to add my 2 cents on this. The wrong description got removed but Solitary is still not working. My character still gets paralyzed as usual. That aside, it's still unclear what exactly does Solitary do. What does 25% of Damage Range guaruanteed mean? If it's a passive when does it activate? When does the 3 second duration start? Why does it have an aura range if it's affects only the wearer? It's just confusing.
  17. I'm not sure how it happens yet but sometimes the spell's potions remain after the battle and get moved from my quickslots to my inventory.
  18. Hey Sking, I'm actually talking about "Sparks the souls of the righteous", not "Avenging storm" although I don't think that one is intended either.
  19. This blunderbuss seems to exhibit a couple of oddities. When combined with Wounding shot, the Hobbled affliction hits my allies for some reason. Not only that but my team is actually behind my priest. The Blind spell also seems to be malfunctioning. It actually hits everyone in a certain range around the target, not in a 60 degree cone aoe as the tooltip suggests.
  20. Hey Aarik D, Absolutely! Here you go: https://www.dropbox.com/s/8u5047og995sbxd/0e64ce5b06134f23b32d74f0901cd134%2021117251%20GreatHall.savegame?dl=0
×
×
  • Create New...