-
Posts
4242 -
Joined
-
Last visited
-
Days Won
11
thelee last won the day on September 23
thelee had the most liked content!
Reputation
2894 ExcellentAbout thelee
-
Rank
Arch-Mage
Profile Information
-
Steam
simulcra
Recent Profile Visitors
11121 profile views
-
yeah the +1 AR from stalker is really good. i've done the same (with bear). but also with antelope (extra AC on top of higher AC). honestly i am not terribly scared of fort and will attacks, at least early on. better deflection and really good reflex (getting caught by drake breaths, man) do sound better to me than mostly irrelevant-in-early-game AR. i'll admit i've never done boar, but that regen seems too slow to be that good.
-
i don't doubt it might be outdated (that section probably hasn't been touched since 1.x), i'll add it to my queue for next update. yeah, though for me the damage of the animal companion isn't very important. i mean, it's important for ranger's overall dps in general, but overall i get more value for most situations just as a source of engagement (with protective companion), so survivability is more important to me, unless i'm ghost heart. yeah it's not bad, that's why i specified it's better mid-late game when you get some scaling. IME AR is just really hard to make relevant in the early to early-mid game in PotD, which is also the hardest part of the game. IIRC a bear companion will have 8 AR at game start (5 + 2 bonus + 1 default fine bonus). Against even a lower-pen attack (like 6 PEN) thanks to PotD scaling you actually get 0 survivability bonus compared to a non-bear (thanks to the +2 PEN from difficulty). it'll protect you a bit from overpenetration (esp crits) but not by much. and then against harder enemies, forget about it, even with zealous endurance or a tier 2 constitution inspiration you may still get 0 DR. it's only really as you keep scaling up and enemies start capping their scaling (or vs spell-based-scaling scaling up too slowly) and/or you get tons more reliable sources of AR boosts or PEN debuffs that it really helps alot. (edit: same goes for players, really. even when you first get heavy armor it's underwhelming the protection versus the cost because of how asymmetrically weak heavy armor weaknesses are. in terms of early armor, it's the exceptional medium armor you can steal from dark cupboard that imo starts having a real impact on survivability and almost exclusively because it covers its weaknesses better than heavier armor)
-
i'm actually partial to antelope for PotD. AR boost is kinda hard to see gains from until scaling from mid-late game, even with resilient companion, bc it's such an arms race against enemy PEN. Meanwhile +10 to all defenses helps all the time, even if subtly. But large size on Bear is pretty handy when you need a body to do some body-blocking (may be dependant on your willingness to micromanage though).
-
echoing Chaospread, honestly i'm super sour on corpse-eater for SC barb. Best part of SC barb is getting high level shout abilities, and corpse eater makes it 100% more expensive. if you're set on corpse-eater i'd multiclass it (so the +1 rage cost hurts overall less) and if you're set on SC barb i'd choose something else.
-
i find the huana voyager to be extremely useful in particular for this. load up like those double-barreled cannons and you don't have to waste time turning, just fire (you may even have a turn to hold position for greater accuracy). contrary to what i said earlier, iirc, rathun might be perfect case for grapeshot. IIRC they don't have surgeons, so once you disable their above-deck sailors, they literally can't sail anymore.
-
it shouldn't actually be killing off enemy combatants prior to a boarding fight. i could be wrong, but istr this is a deliberate choice by the designers. grapeshot can be very effective in low to mid ship fights. the problem is that it scales very poorly into high-level ship fights because surgeons are too good and there are lots of crew members. you can continue to get the enemy ship to cycle combatants around, but they will still have crew members to spare to shoot you down, while their injured sailors heal so quickly that you aren't causing any lasting damage. grapeshot in this case doesn't get you closer to winning, it just slows down how quickly you lose. the one exception is when you have high-enough-rank sailors to trigger events with some regularity, then you can waste tons more enemy time with grapeshot and the game sometimes glitches out and deletes sailors from ship combat (not boarding combat) while trying to move sailors around to deal with events. but cannonball shots also can trigger events, get you closer to winning, and can disable the ship surgeon AND ship cannoneers. for high level ship fights, there's only two good strategies and all other strategies are worse: 1. just cannonball the enemy ship down with the best DPS you can manage 2. use magranite flamethrower on a fast ship like your default or the voyager with high level cannoneers and just brute force the enemy ship down. the fundamental design problem is that they simply made cannonball do too many vital things (your main win condition, disable surgeon, disable enemy weapons [which is their main win condition]).
-
yeah if you do this without save/reloading, the game will stop you at 20 stacks. however the game like... FORGETS what the current stack is and you start creating a new stack after some save/reload cycle. once again, i believe the game will stop you at 20 stacks with this NEW stack. but a save/reload will let you start creating a new stack. it actually ends up being extremely easy to stack this infinitely, just make sure you don't cap out at 20 stacks i think and the game loses track. i actually deliberately avoid doing this because of the combination of just how easy it is to pull this off and how degenerate it makes ranger and ranger multiclass.
-
nope. so based on other people loading my save, it's pretty clear that the bad state persists in the save game. i think what's happening is that something bad gets cached or something, because my original game eventually went back to normal and i could cast twin stones (from scrolls this time) just fine. i think the bad spell state got pushed out of the game cache after a certain point. however, the moment i reloaded my bad save (yes i kept it), everything got screwed up again. even creating a new game doesn't fix it. and it's bad in my current game now. i tried re-naming gameglobalobjects.lvl crosssceneobjects.lvl to see if bad data gets stored there, but i think that entire path just gets clobbered upon fresh game load from desktop, it didn't end up making a difference (and my renamed files disappeared). either way, my game is back into a bad state again and I've exhausted my patience for debugging this for at least another few days. edit: i noticed an issue in my current run with ninagauth's killing bolt. it's supposed to spawn a spirit if you annihilate a non-spirit with it. i did, and i spawned a spectre. then later, and then again a few more times, i killed a non-spirit with it but got no spectre. possibly related issue? some game object is getting lost and a reference is becoming broken? hmm
-
I’m almost stridently confident that graze is not multiplicative. i wonder if AWT is implemented in a weird way (sounds like it) where the debuff duration is calculated separately, like not a part of the initial effect, because if it grazes as part of a separate step instead of as the same calculation step a graze becomes indistinguishable from multiplicative penalty. edit: actually I only know for certain that graze is not multiplicative when it comes to damage, it is very possible graze is multiplicative for durations, because crits ARE multiplicative for durations! This is actually a nice discovery
-
very interesting finding! i think this bears further testing (edit: also in part because typically when I do math I get answers that match the game down to the tenths, so I want to be certain nothing's being missed), because my memory tells me that I did some math/testing and was pretty sure that below-average resolve added additively to durations, it would be weird if it functioned additively in one direction and then in a different system (non-inversion) in another. i'm happy to be corrected, but it would be a pretty big deal if below-average resolve adds duration multiplicatively instead. if it is multiplicative, then in general debuffing resolve is even stronger. inversions are weird and non-linear so if you're deep in the hole it's more punishing than multiplicative, but as you get more out of the hole it becomes weaker than multiplicative, and then you're at the point that the sign flips and it's purely additive. for most cases (e.g. not dorudugan) debuffing resolve would then be pretty good support. for an enemy at 10 resolve, landing a resolve affliction to get +15% additively to debuff durations is one thing, but 1.15x on your debuff duration is a whole other (actually quite good) thing.
-
i agree. i don't think i seriously used miasma until relatively recently, and only because the run before those i had used arkemyr's wondrous torment to incredible effect against dorudugan (i even wrote a build up relying on it here somewhere in the forum history). those spells don't exactly scream "i'm incredible!" but frankly they are. debuffing resolve by 10 in particular is a really subtly effect, not just making enemies easier to hit but making all your DoTs and debuffs much more powerful. the inversion math means that against enemies with above-average resolve, it's comparable to +10 intellect for your party and if we saw that on a buff we'd all agree that's a stupidly powerful buff for everyone. (against dorudugan in particular, they go from 35 resolve to 25 resolve... that's +260% worth of debuff duration increase thanks to inversions, essentially +52 intellect to everyone trying to land an effect... including refreshes of miasma/arkemyr)