Technical questions regarding "passive" blocking - Printable Version +- The Lurker Lounge Forums (https://www.lurkerlounge.com/forums) +-- Forum: Lurker Games (https://www.lurkerlounge.com/forums/forum-6.html) +--- Forum: Diablo II (https://www.lurkerlounge.com/forums/forum-8.html) +--- Thread: Technical questions regarding "passive" blocking (/thread-10200.html) |
Technical questions regarding "passive" blocking - Crystalion - 09-25-2003 Quoting Snorelax and myself from a LL Armory thread: Quote:andSnorelax,Sep 24 2003, 07:50 PM Wrote:Edit 2: I should really start checking things before I post. From http://www.hut.fi/~tgustafs/hitrecovery.htmlThis reminds me of a question I've not seen addressed in v1.10... Quote:Snorelax,Sep 24 2003, 11:31 PM Wrote:From some testing others did on the basin, it does indeed work as a passive blockSo the tech question of interest, is what is the passive block effect base time (duration in frames) and extension to it for FBR? Seems hard to test, so any code readers care to comment? I thought these are better addressed here in the workshop, than in the strat forum (and, of course, the AB is down right now, so I'm not aware of what light old posts there might shed on the problems). Technical questions regarding "passive" blocking - Guest - 09-25-2003 quoting myself ;) Quote:from expert testing with up to 300 fbr and holy shield i've found that either Quote:And finally, a burning question: do monsters (and minions/act 3 hireling etc.) benefit from this "passive" blocking effect as well? This would seriously clip the effectiveness of some attacks vs. such monsters (Dragon Talon, Zeal, etc.). why would it? you aren't supposed to parry more with the effect. they don't get the def/block penalty when moving, so that's the only way it would effect them. the only monsters that don't have a block animation are greater mummies, act bosses and the lowest oblivion knights. so they've got 100% "passive block". extra fast monsters i'm sure parry faster(all their animations are sped up), i don't think they get individual fc/fbr/fhr mods to them. or they might, i'm not an expert <_< Technical questions regarding "passive" blocking - Crystalion - 09-25-2003 Quote:b) it's buggedI suspect both b & ~c (not c). That is, I believe, at a guess, from the patch message, that they did attempt to eliminate block lock and changed the code. What I suspect is that the new "get sneezed on and thereby interrupted" "feature" of v1.10beta effectively overrides this. I don't know if this is intentional. Weeks ago I remember reading speculation that the sneeze interruption effect was deliberate to encourage players to have high DR. Other than the mismatch (ala Ruvanal) in frontend and backend timings, I've also seen this suggested as a reason why multi-attack skills are messed up (i.e. they get interrupted easily, but the frontend continues with them pointlessly). Whatever the underlying reasons, you might (if you haven't already) post a Maggot Lair or Blizzard report re: anti-block lock feature not working as stated in the readme. Technical questions regarding "passive" blocking - Raziel - 09-25-2003 Crystalion,Sep 25 2003, 07:48 PM Wrote:Weeks ago I remember reading speculation that the sneeze interruption effect was deliberate to encourage players to have high DR. .. and then they cap DR at 50%? :blink: Technical questions regarding "passive" blocking - adeyke - 09-25-2003 Methinks "DR" there was "defense rating," not "damage reduced." Technical questions regarding "passive" blocking - Guest - 09-25-2003 Quote:(i.e. they get interrupted easily, but the frontend continues with them pointlessly). yeah, this is how it is for every single skill, just multi-hit ones are more noticeable. the reason though i bet is "lag improvement". since i keep hearing it wasn't like this in 1.09, maybe just all skills got to use the same bandwidth conserving whatever, for optimization, and the devs didn't notice the effects of it. thinking about it again, maybe you're supposed to not be able to attack at all when you're in hit recovery, and this just hasn't been added for the client side. the very low amount of updating on healthbars is lag improvement since 1.02 or thereabouts, i think i saw that mentioned in a "severe bugs list for 1.10", heh. |