Bounty Hunter Archive
Thread: Anonymous Mission Testing and What I Told the Devs
Message Edited by Geodan on 07-12-2005 06:10 PM
There's also a thing that might prove a problem for some. I pay a lot for my arakyds. Even if I get the name already at the arakyd stage I would probably go ahead no matter who the Jedi is. I am not rich so I won't waste 200k in droids going back and forth to town until I find a suitable target that I think maybe is arounf 170k. I really don't think griefing would be an issue even if we get the name early on.
JediWife wrote:
_____________________________________________________________________________________________________________________________
Tanks writes:
Please make the name of the Jedi available after the Arakyd probe reports the planet location. This would resolve a lot of issues and still stop the so called griefing by gank squads, targeting specific Jedi etc., etc.
_____________________________________________________________________________________________________________________________
Okay, for a change I think that the BH community has an acutal problem that needs further consideration. I think you should get a name at some point before contact. I disagree with Tanks that it should be at the Arakyd stage, since the bounty hunter simply has to drive a short distance out of town, launch, upload and get the name. I think it should be given as the first seeker locates the mark. This gives the bounty hunterseveral options: Abort, Engange, or Wait for a better time to strike. He/She now has the name and can choose when and where the first strike will be completed. Since most of you are going to be combating higher leveltemplates, rushing in might simply mean arush to the cloner.For the first time, bounty hunter actually becomes a viable profession that takes not only skill but patience.
BTW, my alt is a MBH. I think its a broken game mechanicthat allowsoneplayer to risk XP loss while the other risks nothing. If I hunt a Jedi, I don't deathblow and if I get killed its no big deal. The hunt was the fun part. IMO, if a bounty hunters entrie goal is focused on disrupting the gameplay of someone else, they have some serious RL issues.
There are many ways this could be implemented in a better way.
One way would be time limits placed on bh's being able to take missions on the same jedi
another would be to have cool off periods for jedi after being hunted stopping a constant barrage of bh bounties upon them by bh guilds - griefing the same jedi.
another would be to make names available after u take the bounty stopping bh's knowing until they send probe droid what marks name is.
But in a pecimistic way i feel the worst case scenario is more likely to happen.
i just hope the devs listen theres so many ways they can do what they want to do without rubbing everyone up the wrong way but maybe at the cost off some peoples subscriptions we will see
zaal mbh bloodfin
zaal_swinari wrote:
This decision to hold back the names really takes the realism out of the game, recently we have devs tell us they want to make the game more star warsy with the cu ect ect .... and then this
There are many ways this could be implemented in a better way.
One way would be time limits placed on bh's being able to take missions on the same jedi
another would be to have cool off periods for jedi after being hunted stopping a constant barrage of bh bounties upon them by bh guilds - griefing the same jedi.
another would be to make names available after u take the bounty stopping bh's knowing until they send probe droid what marks name is.
But in a pecimistic way i feel the worst case scenario is more likely to happen.
i just hope the devs listen theres so many ways they can do what they want to do without rubbing everyone up the wrong way but maybe at the cost off some peoples subscriptions we will see
zaal mbh bloodfin
Ulrek_Oden wrote:
zaal_swinari wrote:
This decision to hold back the names really takes the realism out of the game, recently we have devs tell us they want to make the game more star warsy with the cu ect ect .... and then this
There are many ways this could be implemented in a better way.
One way would be time limits placed on bh's being able to take missions on the same jedi
another would be to have cool off periods for jedi after being hunted stopping a constant barrage of bh bounties upon them by bh guilds - griefing the same jedi.
another would be to make names available after u take the bounty stopping bh's knowing until they send probe droid what marks name is.
But in a pecimistic way i feel the worst case scenario is more likely to happen.
i just hope the devs listen theres so many ways they can do what they want to do without rubbing everyone up the wrong way but maybe at the cost off some peoples subscriptions we will see
zaal mbh bloodfin
Agreed many other, better solutions... But apparently the developers chose to take the easier route...Sad....
I dont think they took an easier route. Think its more or less a "Lets not think things through" route.
I personally like the idea of a /target bounty command. I could care less who the target is I just want to be able to find the right one quickly once I get close to decide if I am attacking, retreating or waiting for a better time to attack.
Reyza wrote:
Removing the names from the mission terms is good, but at some point the BH should be able to identify his mark via a name from a seeker droid when the BH is within some incrememt of distance from the target, for example 500m. A BH has invested far too much time at this point to dump a mission b/c the mark is not someone on his personal/guild hunt (grief?) list.Additionally, I suspect a seeker droid would be capable of determining if a mark has left the planet in attempts to flee.I think adding factional markers to jedi targets is a good step too, but I'd take it even a step further and add 1 of 2 options to provide realistic risks for BH's who hunt same side faction.1) Make jedi missions acceptable only to opposing side factions or neutral BH's.or2) Reward negative faction points for killing a jedi in your faction based on the total number killed. For example killing 5 jedi of the same faction for -25 each, 6-10 jedi for -50 each and 11+ jedi for -100 each.If you wish to hunt both imperial/rebel jedi then remain neutral. I fail to see how killing an army's soldiers (jedi) while claiming to be "for" that side would not earn you negative attention and subsequent adverse repurcussions.The term "luke-warm" or "loyal" I feel is irrelevant in this matter. You are either "for" the rebellion/imperials or "against" them.
I disagree with your post about punishing those that hunt their same faction. The reasoning could be that you are RPing and you are killing off the treasonous Jedi hiding amongst your own ranks.
Quiet420 wrote:
If you want to cause real people to lose real time, then there needs to be a counterbalance, which is your time...I'm all for the removal of xp loss and any form of death penalty...now that pub 20 will put the sanctioned griefing, and those who take advantage of it6 feet under, xp loss remains the last barrier to an enjoyable jedi/bh mechanic.
Ummm... without XP loss, what's to stop a BH and Jedi from just farming credits? What's to stop Jedi from splitting the reward in exchange for just taking a kill?Don't bother tryingto say it would be impossible to do without being able to find the specific Jedi you're looking for on the mission terminal - it woudn't be hard to do at all:
Jedi and BH friend go to a BH Terminal. BH keeps accepting missions while Jedi uses the /duel exploit to see if it is his mission. As soon as the mission is located, Jedi lets BH kill him and they spilt the cash. Repeat a few times and both are quite rich with very little effort.
Good job. You've just provided the devs with another reason to fix the /duel exploit AND remove exp loss at the same time.
slave138 wrote:
Quiet420 wrote:
If you want to cause real people to lose real time, then there needs to be a counterbalance, which is your time...I'm all for the removal of xp loss and any form of death penalty...now that pub 20 will put the sanctioned griefing, and those who take advantage of it6 feet under, xp loss remains the last barrier to an enjoyable jedi/bh mechanic.
Ummm... without XP loss, what's to stop a BH and Jedi from just farming credits? What's to stop Jedi from splitting the reward in exchange for just taking a kill?Don't bother tryingto say it would be impossible to do without being able to find the specific Jedi you're looking for on the mission terminal - it woudn't be hard to do at all:
Jedi and BH friend go to a BH Terminal. BH keeps accepting missions while Jedi uses the /duel exploit to see if it is his mission. As soon as the mission is located, Jedi lets BH kill him and they spilt the cash. Repeat a few times and both are quite rich with very little effort.
JediWife wrote:
Okay, for a change I think that the BH community has an acutal problem that needs further consideration. I think you should get a name at some point before contact. I disagree with Tanks that it should be at the Arakyd stage, since the bounty hunter simply has to drive a short distance out of town, launch, upload and get the name. I think it should be given as the first seeker locates the mark. This gives the bounty hunterseveral options: Abort, Engange, or Wait for a better time to strike. He/She now has the name and can choose when and where the first strike will be completed. Since most of you are going to be combating higher leveltemplates, rushing in might simply mean arush to the cloner.For the first time, bounty hunter actually becomes a viable profession that takes not only skill but patience.
BTW, my alt is a MBH. I think its a broken game mechanicthat allowsoneplayer to risk XP loss while the other risks nothing. If I hunt a Jedi, I don't deathblow and if I get killed its no big deal. The hunt was the fun part. IMO, if a bounty hunters entrie goal is focused on disrupting the gameplay of someone else, they have some serious RL issues.