10 years of diablo

[GriffonSpade]

Kp,Apr 15 2006, 12:02 PM]Easy enough.  It's best fixed by rewriting the combat routines, and a few tweaks to the monster stat table.
As I've explained before, this is very unwise.  Quests don't synchronize well across systems, and quest uniques are generally very powerful for the time at which you get them.
Neat idea.  A five minute hack, most of which is spent adding the new keybinding to request the clear.
This is difficult.  It's mostly the fault of the general lack of synchronization about monster positions.  If all players agreed where the monsters were, there'd be very few mis-aimed projectiles.  Getting melee right is even worse, since the reaction needs to be immediate.  This goes back to my earlier post about how hard it would be to make the game fully synchronized (and the responsiveness consequences that entails).
Player positions are synchronized pretty regularly already, although there's perhaps not as much warp-synchronizing as there could be.
Although worthwhile, this is extremely difficult due to the sheer complexity of the Diablo in-game protocol.  Every single message handler needs to be checked and probably rewritten.
This should be relatively easy, once you bind some event to trigger the fix.
Warriors already get more HP from vitality...
[right][snapback]107315[/snapback][/right]

No, not the quests themselves, just the unique monsters that are in them spawned on the regular dungeon level to provide more flavor, the dropping their quest item was just a thought



Honestly I'm not 100% sure how it is currently synchronized, but this is how I'd like it to be personally.

Is it not possible to simply have it show a reaction without actually affecting stats, and then they send the stats back whenever they ping back?

Example 1:
Warrior attacks Rogue, and his hit check fails so the rogue does not enter hit recovery on the warrior's screen
Rogue's check has her getting hit, losing hit points, and going into hit recovery
Warrior then sees the rogue lose hitpoints, despite seemingly not being hit, but noticably stopped attacking and walking for a moment.

Why does it have to be immediate at all? Is it possible to make PvP impact simply not trigger showing hit recovery or block on attack, and simply have the target go "ah" every time you get a successful swing(hit, miss, or block)?


Example 2:
Warrior attacks rogue, and range check passes, rogue makes "ah" sound, no hit recovery is yet shown
Rogue receives and applies attack, hitting her shield, causing her to go into block
Warrior sees rogue go into block


(Side thought, seeing other players go into attack, hit recovery, or block always done in minimal number of frames possible)

Yah, more warp-synchro would be very nice
Yah, but what is that vitality(90 * 2?) compared to a sorcerer's magic(250 * 2?) who can rapid fire kill most monsters from a great distance en masse, and when they cant can still use golem and stone curse easily, compared to a warrior who has to chase everything around, get up in their face, and kill them 1 at a time.
This would give them the equivalent of 360 hp(sorcerers get -1/3 damage from mana shield correct? this essentially gives them 750 hp from magic! Still nearly double the new amount a warrior would have! Though this is balanced due to them needing this for offense as well...warriors ARE supposed to be the ones able to absorb damage, right?)
I doubt the rogues getting more hp makes much of a difference, as it doesnt provide much advantage to those who use mana shield.
Maybe it would allow the poor warriors to survive a couple fireballs in the arse as well :P

PS Toverkol, its would be +25%/-20%, since to gain back what you lose from 20% you would need 25%(1 * .8 * 1.25 = 1) :P
Edit: Perhaps even change the FOS shrine effects themselves, having them each have 50% chance to do what they originally do, and 50% chance(only if you actually have any spells!) to give +25% current max mana(up to normal max) and +25% current max hp(up to normal max), at the cost of X levels in a random spellX-was originally thinking 2, but could maybe make it costly to get this back, and make it 5