Issues with evading combat initiation

1. The opponent can just spam "attack X". There is no downside to doing so, as even if you spam a few times past successfully dragging a person into combat, nothing happens - just a message that you already are attacking them. Maybe after failing combat initiation, there should be a cooldown before it can be issued again? Would make attacking those shifty people a bit harder, and more relying on IC skills, rather than OOC command spamming.

2. Aim at X seems to always succeed. Another way is to first aim at a person, and then attack them, and that seems to work around the evasion. I think Aim at X should go through the same checks as Attack X to see whether you were successful in stopping the said person, though maybe a slightly lower difficulty, and making the "flee" from aim a bit easier than "flee" from attack.

Let me know what you think! I just love the evasion idea, and think whether someone succeeds in attacking you, or not, should depend on Character sheets, not command spamming/using them in aim/attack chain.

How is arguing if it relies on stats, or not, relate?

This of course depends on your build vs theirs (and perhaps their weapon). If they massively outstat you, yah gonna have a bad time. Personally I've had pretty good luck being a grease-weasel and am having fun with it. I don't think I have taken it as far as it can go though.

Rules Sec.1 - Cheating

1.E. Circumventing In Game Code

The game is not perfect and due to either code constraints or database

constraints, we can not always prevent things that would normally be

prevented in the real world. Exploiting these gaps is forbidden. One

example of this would be to spam door codes in order to get access to

a room or area that your character does not know the access code to,

this type of behavior is strictly forbidden. If you have a question

or are unsure what this section covers, please ask an admin for

clarification before attempting.

This goes for spamming of anything which, when spammed, lets you do something that shouldn't happen.

I play a combat character and people spamming attack to get around a bad die roll while I'm moving and evade their attacks is pretty much a daily staple. It happens all the time. A coded solution would solve it.

I want to +1 Villa here.

This is literally a daily occurrence. I've seen brand new characters do it, and characters who've been in the dome for years do it. If this is indeed against the rules, then this rule is seemingly not enforced at all currently.

I'd like to get a rules clarification on this, please.

Types attack X,

'Player Y swiftly flees your attack'

We're supposed to let them go as the attacker, or if the victim and the attacker continues to attack, we xhelp?

I'd also like to say that seemingly by default, all the NPC's do this to some extent. It's very common to get multiple successful flee procs from an opening attack by an NPC.

Like others in the thread I see 2-3 attack attempts in a row while someone's moving all the time.

It would have to be coded so that if you try to attack someone and you don't actually get an attempt on their life because you were moving or something, the cooldown doesn't activate. And even then because of the way things go sometimes the attacker might still end up with a lot of problems because something puts them into the cooldown that wasn't supposed to.

That would be easier from a code standpoint and not require a secondary check where you're setting a timer, doing string searches and pattern matching.

KILL COMMAND SPAMMER PENALTY

"I have added a penalty multiplier to the existing evade attack penalty (where an attacker chasing a victim might spam the kill command to repeatedly roll against the victim who is already moving through an exit) such that if you spam 'attack' or 'kill' too much, it will multiply the victims awareness more (the penalty basically multiplies each time you get busted for doing this). The new penalty shows up in your @stats with a flashing red @ and notifies GMs when you've earned the penalty. It will go away after 24 hours. It will only affect your ability to succeed at spamming attack when the victim is 'swiftly fleeing'.