Bounty Hunter Archive
Thread: Jedi Friends DB'ing them to get avoid xp loss
It's funny that ONLY jedi are the ones who see nothing wrong with this cowardly move.
Namen_Xenomi wrote:You know, I don't know what the big deal is. If they do this and clone, you STILL have the mission. Just go kill them again.
So kill them twice and hope it doesnt happen again?! you suck
There's a way around it.
/deathblow;
/macro deathblow;
Activate this before your first strike.
I didnt want to post this here, as now Jedi will use it too. However, even if they do use it it will be a toss-up between which computer sends the command to the server first.
Also, no real need to worry about this if they are out in the wild as it will probably be too dangerous for them to keep an open duel and a DB ,acro running for the offhand chance that the Jedi gets Incapped.
BamaDan78 wrote:
Yeah...they go clone...and while the BH is figuring out where the jedi cloned to, the jedi is getting prepared for the fight, thus eliminating the first strike.
It's funny that ONLY jedi are the ones who see nothing wrong with this cowardly move.
Please stop blanketing people - I am a Jedi and I think it's a lame and cowardly exploit. Thanks.
Katalisha wrote:
BamaDan78 wrote:
Yeah...they go clone...and while the BH is figuring out where the jedi cloned to, the jedi is getting prepared for the fight, thus eliminating the first strike.
It's funny that ONLY jedi are the ones who see nothing wrong with this cowardly move.
Please stop blanketing people - I am a Jedi and I think it's a lame and cowardly exploit. Thanks.
QFE
Ekwalizer wrote:
There's a way around it.
/deathblow;
/macro deathblow;
Activate this before your first strike.
I didnt want to post this here, as now Jedi will use it too. However, even if they do use it it will be a toss-up between which computer sends the command to the server first.
Also, no real need to worry about this if they are out in the wild as it will probably be too dangerous for them to keep an open duel and a DB ,acro running for the offhand chance that the Jedi gets Incapped.
and usually being ranged we're only what, 30 m+ when they incap? nice lil headstart for their friends macro
Ekwalizer wrote:
There's a way around it.
/deathblow;
/macro deathblow;
Activate this before your first strike.
I didnt want to post this here, as now Jedi will use it too. However, even if they do use it it will be a toss-up between which computer sends the command to the server first.
Also, no real need to worry about this if they are out in the wild as it will probably be too dangerous for them to keep an open duel and a DB ,acro running for the offhand chance that the Jedi gets Incapped.
Might I ask a qualifying question? What about the DB warm up? Does it not cancel the DB and finish the warm-up if you are moving?
This macro might slow you down, having to wiat for it to cycle to the second or third zip-bar before delivering the DB...
Just a thought.
Ekwalizer wrote:
Yer probably right. I haven't used it myself, I just figured it might skip the timer.
GeckoFighter wrote:
Ekwalizer wrote:
Yer probably right. I haven't used it myself, I just figured it might skip the timer.
be a nice exploit.
??
It's lame are stupid, but its not the end of the world. I havnt played my jedi in forever, but if I remember correctly, dying doesnt fill your force pool. So if you are quick, you can still catch the jedi with low force. Sometimes we are faced with a stupid game mechanic, we need to make the best of it..
Ekwalizer wrote:There's a way around it.
/deathblow;
/macro deathblow;
Activate this before your first strike.
I didnt want to post this here, as now Jedi will use it too. However, even if they do use it it will be a toss-up between which computer sends the command to the server first.
Also, no real need to worry about this if they are out in the wild as it will probably be too dangerous for them to keep an open duel and a DB ,acro running for the offhand chance that the Jedi gets Incapped.
Have you actually tried this macro yourself? The warm-up was added for this very reason, to kill those deathblow macros. Last time I did something like this, it killed the current deathblow timer and started over again and you don't want that do you?