Search the Community
Showing results for tags 'hit'.
Hello, I recently stumbled upon something i think is a bug, or at least i absolutely can't see any logic behind what's happening to me, for the first time after 15+ hours in hard difficulty i got one-shotted by a marauder goon wich kind of surprised me because usually they are not even half of a threat to me, and then i realised after the same thing happened quite a few time in a row with different type of enemies including marauder goon, scrap mechanical at least one of each type of marauder and even mantisaurs or raptidon that i was dying upon landing a hit with my melee weapon, at the
Hello, It is more a proposition, not really a bug. There is a cool thing in Tyranny : you can saw the % of transformation for each step. It would be really cool if in Pillars that would be the same thing ! : For found bugs or even generally a better comprehension of stacking rules. EDIT : If there is a diminushing return, it is the good place to learn the true %. Like : 30 % + 10 % = 40 %.... or 37 % ? Quote of Boeroer in another topic.
Bryy posted a topic in Pillars of Eternity: General Discussion (NO SPOILERS)Grazes seem to serve no real purpose and are not explained at all. Well, other than buffing the perk lists that is. Right now, they are way too common, instead of what they should be which is uncommon. A graze should be something that gives your character some breathing room in the endgame of a fight, or makes them go "oh ffff". Right now, grazes are so common that they should just be called regular damage.
I have found a possible bug, I have noticed it with the bow Borresaine, when equipped by a ranger, havn't been able to test it yet. Crit effect: stun, should be increased/decreased duration with crit/graze, however the effect seems to last 7.5s whenever the shot hits/crits/grazes as well as if the effect hits/crits. Combat log indicates 7.5s for stun under any condition. Is the duration of the effect altered on crit/graze of the effect or the initial hit? Also is this a bug in the application of a duration modifier or simply in the combat log?