blocks

[Critic]

strange system now with blocks.
they check after misses-check.
and I think it's wrong.
if you dodge blow - it can't hurt you with misses.
but if it misses you - it means you haven't dodged or parried it.
in all cases blocks should be checked before misses-not misses.
in according to logic.

[Bacuha]

Its so for a long time, I think.
Im not sure what order is more logical... You can also say that you should not dodge the blow that missed you.

[Nuitari]

Im not sure what order is more logical... You can also say that you should not dodge the blow that missed you.

We took that stance. Also remember, that lots of blocks are limited in activation count.. like skins, mana shield, etc. It would be silly to have your iron skin shattered by a missed blow.
Anyway, in some future time we'll make it more logical.

[Critic]

Anyway, in some future time we'll make it more logical.

I hope...

Just it needs to divide blocks into two groups: before and after check.
Mana shield, ironskin, maggots, etc - after.
Dodge, parry, etc - before.

[Matthew]

Instead of the 'mobs claw MISSES you' message perhaps it could be stuff like,

A mobs claw connects but bounces off your armor harmlessly. Or something.

[omledufromage]

I like matthew's idea

[myx0m0p]

yea, more various messages for all blocks!

[Moon_Face]

As for me various messeges will only waste your attention.
If it will be implemented, i'll return them back on simple misses by client.

[Quino]

#substitute {%0's %1 misses you.} {With high swing of arm, cleaving thin air you notice %0 aiming at you with %1, but you manage to deflect %1 with lucky twist, placing your armor in way of blow.}

Go ahead, invent more perverts.

Regarding blocks:
Let's take this example: a mob strikes you but knocks at your armor. Still, you normally would try to dodge that blow since you don't know will it strike at your armor or stab at your face; thus you should improve your dodge ability.

[Proph]

Go ahead, invent more perverts.

If you insist....

[Matthew]

People worrying too much about what order what goes in, replacing the line gives the appearence that everything is working fine anyway(in an rp point of view) regardless of whether the order of things happening is changed. I only see a negative for doing this on the non-rp side. EG subs and highlights, which obviously have nothing to do with rp. My suggestion was to change it to only one message that didnt include the words 'miss' or 'misses' so it is not implying one of your skills did not work. Or perhaps a couple of messages, just to account for some of the different damage types. I always thought for instance acid damage weapons could splash the target sometimes with acid, even if it misses.

[Quino]

Subs are not selfish way of fixing that problem with messages. Coding these msgs in mud will cause everyone to have them, even those who don't want to spectate that. And subs are very customisable; if you want it - sub it and everyone's happy.

As for

acid damage weapons could splash the target sometimes with acid, even if it misses.

Add 'It drips scorching acid,' to identify
and code it? That's rather logical idea, but then also flaming, freezing, lightning, etc flags should be applied on misses too.

[Raider]

bumping this.

with misses checking before blocks i have to undress self to master dodge/parry etc.

The order of checks affects skills like riposte, restrike, so should be reviewed :/

[Kiri-Jolith]

bumping this.

with misses checking before blocks i have to undress self to master dodge/parry etc.

The order of checks affects skills like riposte, restrike, so should be reviewed :/

I think in RPG games a missed attack is when you actualy hit, but fail to penetrate AC with your hitroll. If so, it would be logical to check blocks and then to check misses.

The idea was implemented and ready to be tested next reboot.