Bounty Hunter Archive
Thread: I believe MBHs have only 4 issues that need to be addressed....currently
1) MBHs need some way of targeting a Jedi mark BEFORE we are within sight of the Jedi.
The best proposal I've seen thus far is the universal targeting system that would allow a MBH to simply use /tar "bhmark". This would keep the anonymity of the Jedi intact, while still enabling the MBH to take advantage of the "First Strike" element of surprise. Furthermore, I don't believe it would be THAT hard to implement. Seems to me it would be nothing more then a "default" action as a result of a static command.
2) MBHs should receive a system message if a Jedi target leaves the plant Kashyyyk, so long as the MBH is on the planet Kashyyyk.
Initially I thought it would be impossible to find and kill a Jedi mark on Kashyyyk given the amount of instances to check and the LOS on the Web Weaver level. Although success can be greatly attributed to AFK Jedi grinding and PC informants, it IS possible to hunt and kill a Jedi on Kashyyyk. As a result of "anonymous missions" though, the use of PC informants will no longer assist a MBH looking for a target. This may result in a MBH searching Kashyyyk for a Jedi that had already left the planet hours ago. It was not uncommon for both Jedi AND BHs to use "lookouts". Many Jedi would place a "lookout" in front of an instanced area in order to inform others that a BH is in the area. Likewise, it was not uncommon for a BH to have a "Starport lookout" in an effort to monitor Jedi traffic, should our Jedi target decide to leave the planet. Once again, with the implementation of anonymous Jedi targets, it is not unreasonable to believe that many that many MBHs will consider a Jedi located on Kashyyyk as an invalid target. To stress this point again, it is not inconceivable that a MBH would spend a huge amount of time trying to track down a Jedi that has been in Theed for the last hour. I would suggest a simple message be sent to the MBH once the Jedi leaves the planet. Finding out if your Jedi target is still online is not really a problem...simply use a seeker droid. If your target had logged off, a message will be given that the target is not online. However, the droid does not respond with a confimation that your target was "not found on this planet". It is because of this system that a MBH may actually have to jump to another planet and launch another probe droid just to confirm that the target is STILL on Kashyyyk,then launch back into space and hyper back to the planet they had just left in an effort to establish planetary location. A MBH doesn't need to know WHERE the Jedi mark is, a MBH just needs to know they are STILL there.
3) /offerride should be considered a "helpful" action, and this option should be locked out for both the MBH and the Jedi once combat has been initiated.
If the Devs intend to make a MBH mission strictly 1 vs 1, then all outside influences needs to be locked. As a solo MBH I have tried to follow a Jedi that was in an unattackable speeder, once I "gained" on the speeder, the Jedi would simply eject from the speeder, target and destroy my speeder, and accept another "offer ride". Leaving me waiting for up to 20 seconds just to call another speeder in an effort to follow. This ability also negates any reason for a Jedi to obtain Force Run. If the MBH - Jedi missions are to be 1 vs 1, then it should be as such, and a MBH should not be, almost, required to bring a "driver".
The fourth issue is NOT BH specific, however, I have seen a trend wherein it effects non-Jedi players at a more frequent rate then it effects Jedi.
4) The "You cannot perform Knock Down recovery while Knocked Down" status should be either confirmed as working as intented with a defined reason for the result.
Is this a desired effect due to a state effect? Is there a counter? Is this the result of an intended "failure rate" with an improper display message? Should Knock Down recovery fail but at a lesser rate? It has been recorded that a fight between a Jedi and a BH does not last passed the inital Knock Down via saber throw by a Jedi, after which the BH never recovers, resulting in a very unfair fight. Furthermore, the damage modifier for a Knocked Down state should be reduced. If after a Jedi is successful in Knocking an opponent down, due to the modifiers and the Jedi attack speed, it CAN take less then 5 seconds to incap a Knocked Down player, or perhaps this is a result of the Armor Break special (but that would be a Jedi issue, not a generic or BH issue).
So there you have it....everything else can be "worked" around.....but this is just my opinion.
One thing that'd be cool though probably unreasonable would be the use of the /tar "bhmark" to also work with group members. This would allow the existance of player informants, however I can see it being abused by having the informant stand near a group of jedi and running the macro until their BH friend pulls one of the missions, causing the target macro to target one. It could be possible to limit this to the same level as the current system would allow greifing by moving the ability to use /tar bhmark to after the arakyd or even seeker stage.
Edit: Mostly I just think that the player informant-BH relationship is something that shouldn't be removed. One thing this game slowly loses is interdependancy, and I don't see why someone helping you find your mark on kash would be unhealthy for anyone but the jedi, and with missions being anonymous it would most likely still be a one time visit.
Message Edited by A_Lamer on 07-13-2005 11:38 AM
You're right on with issue 1.
I don't care what the mark's name is. Jedi are murderous, power-hungry savages. But, as an agent charged with carrying out sweet justice against the vile scum, not having a name until TAB-TAB-TAB manages to target a player is unacceptable.
Hitting TAB is just as likely to target the CL4 Durni/meatlump standing30m behind you as it is the CL82 Gurk/Bol 10m in front of you.
aye, as long as there is a error-proof way of know the marks online status and atargeting system, the actual name isn't as important.
Tucheck wrote:
If we consider that the Jedi - BH TEF issue will be resolved, I can only think of 4 things that concern the MBH.
1) MBHs need some way of targeting a Jedi mark BEFORE we are within sight of the Jedi.
Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi.
2) MBHs should receive a system message if a Jedi target leaves the plant Kashyyyk, so long as the MBH is on the planet Kashyyyk.
So far devs are NOT doing anything regarding Kashyyyk and Jedi.
3) /offerride should be considered a "helpful" action, and this option should be locked out for both the MBH and the Jedi once combat has been initiated.
It is our next TOP issue now.
4) The "You cannot perform Knock Down recovery while Knocked Down" status should be either confirmed as working as intented with a defined reason for the result.
Yep, general bug. Devs are aware of it and it is somewhere on the bug fix queue I am sure.
Tanks wrote:
Tucheck wrote:
If we consider that the Jedi - BH TEF issue will be resolved, I can only think of 4 things that concern the MBH.
1) MBHs need some way of targeting a Jedi mark BEFORE we are within sight of the Jedi.
Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi.
2) MBHs should receive a system message if a Jedi target leaves the plant Kashyyyk, so long as the MBH is on the planet Kashyyyk.
So far devs are NOT doing anything regarding Kashyyyk and Jedi.
3) /offerride should be considered a "helpful" action, and this option should be locked out for both the MBH and the Jedi once combat has been initiated.
It is our next TOP issue now.
4) The "You cannot perform Knock Down recovery while Knocked Down" status should be either confirmed as working as intented with a defined reason for the result.
Yep, general bug. Devs are aware of it and it is somewhere on the bug fix queue I am sure.
"Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi."
How about at planetfall, since seekers don't work on Kashyyyk. You do your bit, get in your Fettmobile, land on whatever planet the Jedi was reported to be on. Get a name. Could even be as cool as getting a "tell" from the SpyOps fella. "Hey...I got a name on that person you're hunting. Schmuckety Saberlover". But I'm guessing they won't go with that either.
And I HATE that KD bug.
Tucheck wrote:
3) /offerride should be considered a "helpful" action, and this option should be locked out for both the MBH and the Jedi once combat has been initiated.
If the Devs intend to make a MBH mission strictly 1 vs 1, then all outside influences needs to be locked. As a solo MBH I have tried to follow a Jedi that was in an unattackable speeder, once I "gained" on the speeder, the Jedi would simply eject from the speeder, target and destroy my speeder, and accept another "offer ride". Leaving me waiting for up to 20 seconds just to call another speeder in an effort to follow. This ability also negates any reason for a Jedi to obtain Force Run. If the MBH - Jedi missions are to be 1 vs 1, then it should be as such, and a MBH should not be, almost, required to bring a "driver".
I kind of like that idea. Kind of get you in the BH mood. At this point I wouldn't care where the name come from as long as we get it before I am 256M out.
Leatherneck_of_Alderaan wrote:
"Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi."
How about at planetfall, since seekers don't work on Kashyyyk. You do your bit, get in your Fettmobile, land on whatever planet the Jedi was reported to be on. Get a name. Could even be as cool as getting a "tell" from the SpyOps fella. "Hey...I got a name on that person you're hunting. Schmuckety Saberlover". But I'm guessing they won't go with that either.
And I HATE that KD bug.
Geaux Darkcloud
Geauxx wrote:
I kind of like that idea. Kind of get you in the BH mood. At this point I wouldn't care where the name come from as long as we get it before I am 256M out.
Leatherneck_of_Alderaan wrote:
"Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi."
How about at planetfall, since seekers don't work on Kashyyyk. You do your bit, get in your Fettmobile, land on whatever planet the Jedi was reported to be on. Get a name. Could even be as cool as getting a "tell" from the SpyOps fella. "Hey...I got a name on that person you're hunting. Schmuckety Saberlover". But I'm guessing they won't go with that either.
And I HATE that KD bug.
To "add" a little bit to it, you could have a wait a random number of minutes between planetfall and getting the message.
Yes, sometimes that would mean you're right up on the guy when you get the name. But I think it would add something to the process.
Tanks wrote:
Tucheck wrote:
If we consider that the Jedi - BH TEF issue will be resolved, I can only think of 4 things that concern the MBH.
1) MBHs need some way of targeting a Jedi mark BEFORE we are within sight of the Jedi.
Still working on getting the names from either the Arakyd or first Seeker response. This would also eliminate getting the same missions over and over on house sitting Jedi.2) MBHs should receive a system message if a Jedi target leaves the plant Kashyyyk, so long as the MBH is on the planet Kashyyyk.
So far devs are NOT doing anything regarding Kashyyyk and Jedi.
3) /offerride should be considered a "helpful" action, and this option should be locked out for both the MBH and the Jedi once combat has been initiated.
It is our next TOP issue now.
4) The "You cannot perform Knock Down recovery while Knocked Down" status should be either confirmed as working as intented with a defined reason for the result.
Yep, general bug. Devs are aware of it and it is somewhere on the bug fix queue I am sure.
Thanks Tanks.