Anyone explain?
--------------------
Blokhed - In the Foothills
You catch a faint scent of a horse nearby.
* HP:Beaten MV:Winded - Dixon: Critical > [k dixon]
You do the best you can!
* HP:Beaten MV:Winded - Dixon: Critical > cmm
b
Mood changed to: Berserk
[bash ] - Dixon: Critical >
-
Your heartbeat calms down more as you feel less panicked.
*Dixon* sends you sprawling with a powerful bash! Eat one bash for posterity
* HP:Battered MV:Winded - Dixon: Beaten > b
*Dixon* hacks your right leg.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
[bash ] - Dixon: Beaten >
* HP:Beaten MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your body.
[bash ] - Dixon: Beaten >
As *Dixon* avoids your bash, you topple over and fall to the ground! Should have won this with a zerk mallet
*Dixon* sends you sprawling with a powerful bash! Bash 1
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* barely hacks your body.
You wish that your wounds would stop BLEEDING so much!
b
[bash ] - Dixon: Beaten >
*Dixon* sends you sprawling with a powerful bash! Bash 2
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
You wish that your wounds would stop BLEEDING so much!
* HP:Beaten MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body hard.
You wish that your wounds would stop BLEEDING so much!
[bash ] - Dixon: Beaten >
*Dixon* sends you sprawling with a powerful bash! Bash 3
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
You try to pound *Dixon*, but he parries successfully.
[bash ]
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
*Dixon* sends you sprawling with a powerful bash! Bash 4
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Critical MV:Winded - Dixon: Beaten >
*Dixon* hacks your left leg hard.
You wish that your wounds would stop BLEEDING so much!
stare Just plain flamboozled the system is screwing me over
* HP:Critical MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg hard.
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > You stare at the sky.
You try to pound *Dixon*, but he parries successfully.
ed - Dixon: Beaten > * HP:Critical MV:Winded - Dixon: Beaten >
*Dixon* sends you sprawling with a powerful bash!
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > spit
*someone* hacks your left hand.
You are dead! Sorry...
Denied Bashes
Re: Denied Bashes
He was just beating your timer.
It's called a rebash. Once you get good enough at it you'll learn to either count or feel out how to time your bashes so that they go in the moment your opponent is being stood up by the game.
Just takes practice, or in the case of lame asses, a script.
It's called a rebash. Once you get good enough at it you'll learn to either count or feel out how to time your bashes so that they go in the moment your opponent is being stood up by the game.
Just takes practice, or in the case of lame asses, a script.
Re: Denied Bashes
Just like to point out I use mush client and dont use scripts :P if you look at log I posted I had a lot of bashes in there while you sat trying to time it right.
Re: Denied Bashes
Looks like you might have been getting some lag since your input and the bash timer starting seem to have a melee round between them. Or am I reading that wrong?blokhed wrote: *Dixon* sends you sprawling with a powerful bash! Bash 3
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
You try to pound *Dixon*, but he parries successfully.
[bash ]
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
*Dixon* sends you sprawling with a powerful bash! Bash 4
You wish that your wounds would stop BLEEDING so much!
Other little things: Dixon is Rank 6, which means he has the Lancer damage bonus to spawn. It's not as wild as master damage, but still packs a punch. Couldn't tell from Dixon's log what you were wearing, but it also looks like your abs might have been low. Still frustrating as hell to get re-bashed that many times, but might have made the difference here if you could have survived another bash.
Re: Denied Bashes
Possible Lag aside, is there really a point in the timeline of bashing that you can manually(or scripted) start a bash (that isn't as soon as possible) that will land before your previously-bashed opponents bash?
As I understood entering the bash command (even slightly lagged) whilst bashed should register before an opponents requirement to manually(or scripted) start a new bash. Lag wouldn't account in the instance I entered my command to bash asap after being bashed to register as soon as game unstunned me.
I entered in no other commands, until the end stare, other than bash, depending on the idea that I would at least get the opportunity to land/miss before him after having been bashed.
As I understood entering the bash command (even slightly lagged) whilst bashed should register before an opponents requirement to manually(or scripted) start a new bash. Lag wouldn't account in the instance I entered my command to bash asap after being bashed to register as soon as game unstunned me.
I entered in no other commands, until the end stare, other than bash, depending on the idea that I would at least get the opportunity to land/miss before him after having been bashed.
Re: Denied Bashes
Is there really a point in the timeline of bashing that you can manually(or scripted) start a bash (that isn't as soon as possible) that will land before your previously-bashed opponents bash?
Re-worded :
Is there a point in the timeline of bashing where you can start a bash that will complete before your previously-bashed opponents bash command goes through?
Theoretical answer :
Bash is 13 pulses long. Lag or no lag, if 13 pulses go through, your bash will complete and a success check will calculate and you will either land or miss a bash.
A combat round is 12 pulses. A bash sits you for 2 rounds, so 24 pulses.
Here's the tricky part. While you are "sat" for 24 pulses, it probably takes 1 pulse (virtually 0.3 seconds) for the game to change your Bashed-status to Standing-status, which is the pulse where a perfectly timed opponents bash command can start before your bash command starts. Therefore, re-bashing will always go through first, if timed perfectly.
Disclaimer : This is just an idea that could make sense. And as an aside, Dixon got mad lucky to time 3+ rebashes in a row, well played!
Re-worded :
Is there a point in the timeline of bashing where you can start a bash that will complete before your previously-bashed opponents bash command goes through?
Theoretical answer :
Bash is 13 pulses long. Lag or no lag, if 13 pulses go through, your bash will complete and a success check will calculate and you will either land or miss a bash.
A combat round is 12 pulses. A bash sits you for 2 rounds, so 24 pulses.
Here's the tricky part. While you are "sat" for 24 pulses, it probably takes 1 pulse (virtually 0.3 seconds) for the game to change your Bashed-status to Standing-status, which is the pulse where a perfectly timed opponents bash command can start before your bash command starts. Therefore, re-bashing will always go through first, if timed perfectly.
Disclaimer : This is just an idea that could make sense. And as an aside, Dixon got mad lucky to time 3+ rebashes in a row, well played!
Re: Denied Bashes
As well, the gaps that may appear in my log aren't timing but received narrates/comms being parsed to another window. Makes my command line/log a bit junky but short story I didn't try timing anything and was depending on getting a postbash bash through. Lack of this 3 times in a row is what rankled me.
Re: Denied Bashes
Just to add a visual representation of my suggested theory :
*Dixon* sends you sprawling with a powerful bash! <--- 24 pulses of being bashed starts.
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
<--- 24th pulse, bashed-status reaches its last pulse.
<--- 25th pulse. You are now "unbashed".
<--- 25th pulse. Dixon's bash command goes through. (His bash starts rolling)
You try to pound *Dixon*, but he parries successfully.
[bash ] <--- 26th pulse. You start your bash timer.
That's my general idea.
*Dixon* sends you sprawling with a powerful bash! <--- 24 pulses of being bashed starts.
You wish that your wounds would stop BLEEDING so much!
You're in no position to do anything aggressive.
* HP:Beaten MV:Winded - Dixon: Beaten >
*Dixon* hacks your right leg.
You wish that your wounds would stop BLEEDING so much!
* HP:Critical MV:Winded - Dixon: Beaten > b
*Dixon* hacks your body.
You wish that your wounds would stop BLEEDING so much!
<--- 24th pulse, bashed-status reaches its last pulse.
<--- 25th pulse. You are now "unbashed".
<--- 25th pulse. Dixon's bash command goes through. (His bash starts rolling)
You try to pound *Dixon*, but he parries successfully.
[bash ] <--- 26th pulse. You start your bash timer.
That's my general idea.
Re: Denied Bashes
I think Theid is generally right. Another point to think about is that the bash mechanics were changed some 10 yrs or so ago so in the event of a virtual tie, there is no longer a "bash-off" like there used to be. No idea how the system actually resolves this, but I've always assumed it is based on who engaged whom and thus by combat order - ie, in the event of a tie, the person who would normally melee 1st in the combat order will get their roll to go through first. Your first bash would be an example of this. Some think it's determined by login order, similar to door/flee mechanics. Shrug.
As for timing, I've always called bs on that and always will. Sorry, you'll never convince me that certain people have the ability to spam "bash" until it goes through at the exactly correct moment, then not hit enter again. Sometimes, sure, but some people do it consistently. That is called a trigger. Re-bashing 3x in a row isn't crazy and it's certainly possible but it becomes apparent pretty quickly when someone re-bashes 3+ times in a row during every engagement.
As for timing, I've always called bs on that and always will. Sorry, you'll never convince me that certain people have the ability to spam "bash" until it goes through at the exactly correct moment, then not hit enter again. Sometimes, sure, but some people do it consistently. That is called a trigger. Re-bashing 3x in a row isn't crazy and it's certainly possible but it becomes apparent pretty quickly when someone re-bashes 3+ times in a row during every engagement.
Re: Denied Bashes
Good point Lykan. If I had to take a guess, I think in the past after a double failed bash, where both combatants failed at the exact same time, the game rerolled the bash dice over and over until someone landed. What happens now, is you get a disengage/engaged roll instead. I don't remember if you could become disengaged from a failed bash in the past.. Or if there was missed bash lag? It's been a long time..