Spam does kill, but.. (t):

[ Follow Ups ] [ Post Followup ] [ Dioxide's CForum ]

Posted by Proud Blade(VIP) on August 23, 2000 at 21:50:38:

In Reply to: Got a question.... posted by WhiteSpy on August 22, 2000 at 21:23:26:

There's a tradeoff.

1) If you "stack" many commands, you will often be screwed when your opponent springs a surprise on you, one combatant gets a string of luck, another person joins the fight, or the like. Things that might be a good idea after a round of combat might not look so good after you see how the next six rounds have been going. (The classic case is the bash-spamming warrior who is gtting his ass kicked during normal combat exchanges. Bash looked smart when you thought your foe was easy prey, but when you realized that your opponent is much tougher, and you have five "bash" commands entered.... ouch.

2) However, even a very slight pause (typo, hesitance, distraction by RL) can lead to an opponent squeezing in a command just before you in very particular circumstances. If you trip an opponent, there will be a tiny window (after two rounds) where your opponent will have just enough time to squeeze in one command. If they blow it (they are still typing "e" on Eastern Road), it can be a footrace to get the next command in. (You: "trip", Them: "flee") In that situation, having exactly one command "on the stack" at all times will mean you maximize the utility you get out of those "footrace" situations.

3) I'm certainly no elite, but my advice is: Keep zero commands stacked, unless you -know- the battle is yours no matter how badly you screw it up. Then, keep zero commands stacked unless you think your opponent is going to stay and fight. Keep at most one command stacked only when you know it's going to be a slugfest, you are extremely sure of the best tactics to use, and you just want to try to get your stuff in a fraction of a second before they do.

Follow Ups:

Post a Followup

Name:
E-mail:
Subject:
Comments:


[ Follow Ups ] [ Post Followup ] [ Dioxide's CForum ]