Bounty Hunter Archive

---

RemoMoxey wrote:

---

Musicmaestro wrote:

Just had a fight against a Master Saber, Master Enhancer Jedi. I lucked out as a BH just started a fight so I get up and break cover (MBH/MRM, 4000CM) to go attack and use the other BH to my advantage. Well, the other BH died before I could even get a shot off... At first I simply assumed he was a new BH with poor gear... I was wrong.

She immediately used Adv Saber throw to knock me down then followed with Stasis. Np, a free hit while I was down no big deal... NOT QUITE!..

"You are still too disoriented and cannot get up at his moment."

I could not get up. Stasis was either not breaking on being hit like it's supposed to or the effect was lingering somehow.

Finally managing to get up, just in time to die. The Jedi let the incap timer expire...

I got up, healed and attempted to get off a KD to get some breathing room.

This time was even worse. I was knocked down again:

"You are still too disoriented and cannot get up at his moment."

"You are still too disoriented and cannot get up at his moment."

"You are still too disoriented and cannot get up at his moment."

There was about 12 attacks from the last stasis the jedi used.

Then, as if this wasn't enough of an exploit/bug to deal with...

"You cannot knockdown recover while knocked down."

Ok, I'm pissed off... but then my equipment takes damage at the cloner. PvP you're not supposed to take damage at the cloner... nice SOE.

So, this KD/Stasis bug is disgusting. While this Jedi I'm sure is bragging about taking down two BH in about a minutes time the exploit/bug involved was disgusting and needs immediate attention.

I tend to do very well against most Jedi. Some veterans of over 100 BH battles I last a good 15-20min. I've never lost this fast yet. This reminded me of pre-CU with TKM KD fights.

My Gear:

Assault Bowcaster

spd: 1.4 (effective)

dmg: 515-1173 (Kinetic)

sac: 82

Armour:

Kashyyykian Ceremonial (Recon)

8020 Energy resist w/ AB slices.

---

Some advice for you:

1-You were dizzied, that's why you couldn't get up ("you are still too disoriented and cannot get up at this moment" is the dizzy system message). You were hit by the Jedi with a dizzy while stasised (the free hit was a dizzy). You have dizzy recovery......use it next time .

2-The "can't knockdown recover while knocked down" is a lag/spam bug, CAUSED BY YOU!! When you get KDed, if you have another special loaded and use KD recover the special you have loaded takes preference. This causes you to get the message (althought is should say "you can't use Full Autowhile knocked down" or whatever special you had loaded). If you don't try to spam KD recover and wait 2-3 seconds and use KD recover you will stand right back up (let the yellow highlight on you toolbar disappear before hitting KD recover). You make it worse by hitting KD recover then an attack, wait until you stand up before spamming your next attack. DO NOT SPAM SPECIALS........that's what killed you. This is one of the new CU "highlights" .

---

This has happened to me plenty, and I am very carefull NOT to spam any button, especialy recovery buttons. This is not only caused by user created lag.... if spamming a single action can create that much lag

---

Daivan wrote:

---

RemoMoxey wrote:

---

Musicmaestro wrote:

Just had a fight against a Master Saber, Master Enhancer Jedi. I lucked out as a BH just started a fight so I get up and break cover (MBH/MRM, 4000CM) to go attack and use the other BH to my advantage. Well, the other BH died before I could even get a shot off... At first I simply assumed he was a new BH with poor gear... I was wrong.

She immediately used Adv Saber throw to knock me down then followed with Stasis. Np, a free hit while I was down no big deal... NOT QUITE!..

"You are still too disoriented and cannot get up at his moment."

I could not get up. Stasis was either not breaking on being hit like it's supposed to or the effect was lingering somehow.

Finally managing to get up, just in time to die. The Jedi let the incap timer expire...

I got up, healed and attempted to get off a KD to get some breathing room.

This time was even worse. I was knocked down again:

"You are still too disoriented and cannot get up at his moment."

"You are still too disoriented and cannot get up at his moment."

"You are still too disoriented and cannot get up at his moment."

There was about 12 attacks from the last stasis the jedi used.

Then, as if this wasn't enough of an exploit/bug to deal with...

"You cannot knockdown recover while knocked down."

Ok, I'm pissed off... but then my equipment takes damage at the cloner. PvP you're not supposed to take damage at the cloner... nice SOE.

So, this KD/Stasis bug is disgusting. While this Jedi I'm sure is bragging about taking down two BH in about a minutes time the exploit/bug involved was disgusting and needs immediate attention.

I tend to do very well against most Jedi. Some veterans of over 100 BH battles I last a good 15-20min. I've never lost this fast yet. This reminded me of pre-CU with TKM KD fights.

My Gear:

Assault Bowcaster

spd: 1.4 (effective)

dmg: 515-1173 (Kinetic)

sac: 82

Armour:

Kashyyykian Ceremonial (Recon)

8020 Energy resist w/ AB slices.

---

Some advice for you:

1-You were dizzied, that's why you couldn't get up ("you are still too disoriented and cannot get up at this moment" is the dizzy system message). You were hit by the Jedi with a dizzy while stasised (the free hit was a dizzy). You have dizzy recovery......use it next time .

2-The "can't knockdown recover while knocked down" is a lag/spam bug, CAUSED BY YOU!! When you get KDed, if you have another special loaded and use KD recover the special you have loaded takes preference. This causes you to get the message (althought is should say "you can't use Full Autowhile knocked down" or whatever special you had loaded). If you don't try to spam KD recover and wait 2-3 seconds and use KD recover you will stand right back up (let the yellow highlight on you toolbar disappear before hitting KD recover). You make it worse by hitting KD recover then an attack, wait until you stand up before spamming your next attack. DO NOT SPAM SPECIALS........that's what killed you. This is one of the new CU "highlights" .

---

Clear, concise, excellent discription of what *really* happened during this fight.

Thank you so much for posting this and not letting another one of these "GAME BREAKING!!! DEFCON 1" threads go on and on and putting misinformation and fear and hatred into a SWG community that already has to much of this crap.

***** Five stars for you my friend.

---

---

mindspat wrote:

---

Musicmaestro wrote:

---

Xalya_Shadowalker wrote:

Its a bug. Its usually caused by lag. It happens to everyone. Jedi and BH alike, in PvP and PvE. Stasis isn't the problem. Take a deep breath, quit spamming KD recoveryand calm down. Then press KD recovery again.

Also the item decay you saw at the cloner is decay you took while fighting the Jedi, not extra decay incurred by cloning.

Message Edited by Xalya_Shadowalker on 09-07-2005 10:50 AM

---

First off, How does it happen to Jedi and BH alike when BH do not have Stasis? My concern here is the Stasis not the KD recovery bug which we all know.

Second, the decay I saw at the cloner was cloning condition damage window message after I cloned. You don't recieve this message when you take dmg from jedi. Only when you clone.

---

This exact same thing happens to Jedi 'cs "Stasis is not the culprit"! There's other factors which are global and affect the entire player base.

Answer this, do you or were you using macros?

---

---

xEPICx wrote:

---

XanKrieger wrote:

---

Musicmaestro wrote:

She immediately used Adv Saber throw to knock me down then followed with Stasis. Np, a free hit while I was down no big deal... NOT QUITE!..

---

UMMM chief, u were KD'd THEN stasis'd, acts much like the old KD STarle Shot exploit, except this one isnt a exploit as stasis is ment to freeze u rofl

---

He's just another BH that thinks Stasis is a sploit. He sounds like the type of person that accused me of using Stasis on a turret the other night.

---

---

Musicmaestro wrote:

---

mindspat wrote:

---

Musicmaestro wrote:

---

Xalya_Shadowalker wrote:

Its a bug. Its usually caused by lag. It happens to everyone. Jedi and BH alike, in PvP and PvE. Stasis isn't the problem. Take a deep breath, quit spamming KD recoveryand calm down. Then press KD recovery again.

Also the item decay you saw at the cloner is decay you took while fighting the Jedi, not extra decay incurred by cloning.

Message Edited by Xalya_Shadowalker on 09-07-2005 10:50 AM

---

First off, How does it happen to Jedi and BH alike when BH do not have Stasis? My concern here is the Stasis not the KD recovery bug which we all know.

Second, the decay I saw at the cloner was cloning condition damage window message after I cloned. You don't recieve this message when you take dmg from jedi. Only when you clone.

---

This exact same thing happens to Jedi 'cs "Stasis is not the culprit"! There's other factors which are global and affect the entire player base.

Answer this, do you or were you using macros?

---

I do not use macros at all. Not my style. Also, I do not spam KD recovery. Simply clicking once at the right time is enough.

---

Establish a keymap with the following commands:

/sit; /stand

I've used this in the past and although it's not 100% it's a good way to bypass some issues.

---

Gannarr wrote:

This affect happends to anyone not just bh and its not a stasis bug.

Message Edited by Gannarr on 09-07-2005 11:06 AM

---

Message Edited by hamhamthe3rd on 09-07-2005 08:46 PM