Bounty Hunter Archive
Thread: Bug or Working as intended?
Page 1 of 2
EdahFreecloud
Fri Sep 03, 2004 1:10 pm
#1
OK I am fairly new to the hunting of jedi, and this has happened to me on my first 2 jedi marks, please tell me if this is how things are supposed to work or not.
I will keep this brief as possible: I am a master fencer, pistoleer 0/0/4/4, BH 3/0/0/0::: I am fighting jedi, I use dizzy/lunge on him, he drops to a knee and starts using a saber throw on me from kneeling, (heres the bug question) My combat que then locks up on me and I cannot attack, cannot peace, I cannot take brandy, cannot lunge again to drop him to prone, cannot switch weapons to shoot him as I run for my life 
. Is this a jedi mind trick or something?It wasnt warcry either BTW,Has this happened to anyone else?
. Is this a jedi mind trick or something?It wasnt warcry either BTW,Has this happened to anyone else?
BenkeiHami
Fri Sep 03, 2004 1:20 pm
#2
if it wasn't warcry it sounds like a bug to me. Does it just lock for a few seconds, for minutes, or till you relog? Can you attack mobds normaly, other players? I would try doing a fullscan at the launcher.
KDS1
Sat Sep 04, 2004 1:19 pm
#4
I think its a jedi skill, but not sure. Its happened to me about 4 times during the last few days. But the last time it happened was a few hours ago and the jedi had run off and I was fighting his friend who I dont think was a jedi ( never pulled a saber) but yeah a few times the combat queue has just hung for about 15 - 20 seconds. Often several times in a row.
Bannon9k
Sat Sep 04, 2004 1:48 pm
#5
were you spamming attacks at all?
I've noticed myself that if I spam attacks I normally just hit peace to clear the combat que. However, if your spamming attacks REALLY fast and just hit the peace button once, it will continue to stack the attacks onto the que. Thus while running, giving you the appearance that your not attacking. This would prevent food from being eatten, or any other action from taking place.
Just a heads up at a possibility.
EdahFreecloud
Sun Sep 05, 2004 12:25 am
#6
It totally locks up until im dead, I couldnt burst run either.. I submitted a /bug on it.. and i went hunting again last night and it didnt happen. so im not too fussed about it
RyFord
Thu Aug 25, 2005 11:14 am
#7
I get a BH on me and kill him. 30 minutes later he is standing in front of me with my mission again. I thought there was a cooldown on hunting the same person.
I killed him twice but could only farm him once for PvP rating 
Neomonk
Thu Aug 25, 2005 11:21 am
#8
I wasnt aware of a cooldown timer. If there is, its news to me.
Ilcbar
Thu Aug 25, 2005 11:21 am
#9
If he went back and got another mission and it happened to be yoursthen it was just a fluke but working as intended. There is no "cool down" on hunting the same personand we don't know who we are going to hunt when we pull the mission.
RyFord
Thu Aug 25, 2005 11:23 am
#10
Ilcbar wrote:
If he went back and got another mission and it happened to be yoursthen it was just a fluke but working as intended. There is no "cool down" on hunting the same personand we don't know who we are going to hunt when we pull the mission.
I know the part about not knowing. I just always assumed you could not go back to the same person. The guy is a decent enough person and we laughed it off but it seems odd to defeat someone and then 30 minutes later here they are again.
RyFord
Thu Aug 25, 2005 11:46 am
#11
well he just came back and died again...this makes 3 times in an hour now 
poor guy
Dr_Nalio
Thu Aug 25, 2005 11:48 am
#12
I think it has to do with playing at off-peak hours and a limited amount of missions on the terms then for Jedi. It's easier to find your mission. I had a friend get a lot of repeat visits from a bh the other day just like you're describing.
Scobey
Thu Aug 25, 2005 11:51 am
#13
I have actually been told by a lot of BH friends that this is happening alot. I think it may actually be a bug, and some of my BH friends have said that they got the same jedi 3 straight missions. I thought your vis was reset after BH death, and you shouldn't be on the terms anymore, but I guess that is wrong.
Page 1 of 2