Bounty Hunter Archive
Thread: Anonymous Mission Testing and What I Told the Devs
Now we have seen the devs get swayed by the whining of jedi players at fanfest, specifically on the points about paddy ganking, and targeting specific Jedi players. Well, guess what..... paddies are easier than Knights, so what did you expect? Between their previous profession skills (provided they were a combat prof) and the fs skills, they can be surprisingly difficult sometimes. Anytime you cross that carebear line into pvp, you are going to have to live with the fact that other people are going to beat on you until you learn how to adapt. It's straight Darwinism at its finest that the paddies are the first to get their missions pulled, and Knights last, as you progress up in mission difficulty. Deal with it.
As for targeting players, I point back to the pvp not being controllable by SOE. Look at the guild wars that go on all the time. Is that griefing? Over the last year Ive heard alot of crying by smaller guilds that "'so and so' guild picks on us all the time when we are overt." These guys dont get any love from the devs, and as well they should not. Neither should Jedi. The game is designed so that you can make Knight without getting on the terms. Unfortunately, it will take longer than a 1-month subscription period to do so, so SOE now fears losing their 'return customers'. Beyond that, the whole Kashyyyk issue makes it nearly impossible to find a Jedi on Kashyyyk with knowing their name.
Please flame away, jedi trolls!!!!!
Kyyrtek wrote:
I will never be surprised at the the idiotic posts I read in this forum. Jedi - get over yourselves, you are the alpha class and you have to accept that being 1.5x stronger comes with setbacks. Just like smugglers were tied to AS and WS for slicing, bh were tied (originally) to jedi to make the game 'work'. It was necessary to keep the population down, to add the element of keeping jedi hidden, and on top of everything to intentionaly make it difficult.
Now we have seen the devs get swayed by the whining of jedi players at fanfest, specifically on the points about paddy ganking, and targeting specific Jedi players. Well, guess what..... paddies are easier than Knights, so what did you expect? Between their previous profession skills (provided they were a combat prof) and the fs skills, they can be surprisingly difficult sometimes. Anytime you cross that carebear line into pvp, you are going to have to live with the fact that other people are going to beat on you until you learn how to adapt. It's straight Darwinism at its finest that the paddies are the first to get their missions pulled, and Knights last, as you progress up in mission difficulty. Deal with it.
As for targeting players, I point back to the pvp not being controllable by SOE. Look at the guild wars that go on all the time. Is that griefing? Over the last year Ive heard alot of crying by smaller guilds that "'so and so' guild picks on us all the time when we are overt." These guys dont get any love from the devs, and as well they should not. Neither should Jedi. The game is designed so that you can make Knight without getting on the terms. Unfortunately, it will take longer than a 1-month subscription period to do so, so SOE now fears losing their 'return customers'. Beyond that, the whole Kashyyyk issue makes it nearly impossible to find a Jedi on Kashyyyk with knowing their name.
Please flame away, jedi trolls!!!!!
You know....the new and improved system of "grinding Jedi" never made much sense to me. While I'm sure more then ONE Jedi has said, "Finally, I'm fully templated...now what?". From a financial point of view, wouldn't you want your customers to make this statement AFTER 6 or 7 months....instead of after 1?
hanshadow wrote:
Tanks, this is no different than it is today. It isn't hard to tell when a BH is approaching. If you are out in the wild, and a blue dot pops up headed toward you, it's probably a BH. If you are in a city, the Jedi can't tell.
What's different again??
Difference is that in live I can "/target Jediname", so that when I get to him I can start shooting etc. The way I do it by the time I am noticed on the radar I have already targeted the Jedi, dismounted and have combat initiated.
In Pub. 20 by the time I target the Jedi there is no longer any surprise, if any, at all!!!
Tanks wrote: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.
THis is precisely what I requested in a thread I started a few days back. I think its a fair compromise.
Neutral Imperial Agent
Nyracasso wrote:
Solution!
Don't let the Jedi know you're after him.I know it's tough
, butthat is your responsibility and your advantage.
If they're close enough to /duel you, then you shouldalready have him or her targetted, and shouldknow what to do.
It's not a marks responsibility to make him or herself ready for you to attack them.
Zorron wrote:
Your conclusion, that the name should begiven after the Arakyd reports the planet location, does not follow directly from your observations.Giving the name so soon would certainly bring back the bottom feeding, and maybe even more bad things that this patch stamps out.
You do know that is a 3-5 minute lag from the time you get the mission and get the planet location. I don't think people will keep on doing this over and over trying to get a newbie Jedi's name. Especially since there is no list of newbie Jedi. Now, I could see people dropping missions on known Cantina or house sitting AFK Jedi a bit sooner.
A proper conclusion from your observations, that fixes the problem you are referring to without breaking anything else, is that the name should be given when you are within 500m of your mark's waypoint. That's still outside radar range so you continue exploiting server lag to make the most of your first strike, butbecause you're only minutes away from attacking, you are still tempted to go for it instead of dropping the mission (aka bottom feeding).
The reason I mentioned Arakyd response is that it would be easier for devs to program. It is a single occurance per mission.
You can't launch an Arakyd probe if a mark is offline. I guess BH was not one of those professions you grinded out to get your Jedi.
Zorron wrote:
Oh, one other thing. If you really tested thoroughly, and if you weren't so antagonistic to the idea of truly anonymous terminals, your #1 priority for fixing wouldn't be the provision of the name at some point. It would be having an ability to check if the mark is still online, maybe with some kind of button in the mission description that does "VERIFY MARK ONLINE STATUS" and tells you if they are online or offline. Because as the code is right now, when the servers have been up a while the majority of missions on the terminals will be for offline Jedi who have logged on, gone on terms and have long since logged off. With anonymity in place, once a server hasbeen up 24 hours or so you guys will be wasting huge amounts of time looking for online Jedi, unless you get the devs to fix this.
Then again, maybe Tanks doesn't wantthis fixed the proper way, so he can proposehis ownfixalong the lines of"let us have the name so we can check if they are online"....
Tanks wrote:
Zorron wrote:
Your conclusion, that the name should begiven after the Arakyd reports the planet location, does not follow directly from your observations.Giving the name so soon would certainly bring back the bottom feeding, and maybe even more bad things that this patch stamps out.
You do know that is a 3-5 minute lag from the time you get the mission and get the planet location. I don't think people will keep on doing this over and over trying to get a newbie Jedi's name. Especially since there is no list of newbie Jedi. Now, I could see people dropping missions on known Cantina or house sitting AFK Jedi a bit sooner.
A proper conclusion from your observations, that fixes the problem you are referring to without breaking anything else, is that the name should be given when you are within 500m of your mark's waypoint. That's still outside radar range so you continue exploiting server lag to make the most of your first strike, butbecause you're only minutes away from attacking, you are still tempted to go for it instead of dropping the mission (aka bottom feeding).
The reason I mentioned Arakyd response is that it would be easier for devs to program. It is a single occurance per mission.
No offense tanks, but The system as is on test makes it so a bh actually has to do some work, and stalk his prey from afar before he attacks... What you really want is bh's to still have the ability to have 5 on 1 gank squads, no matter the jedi.. With todays healing ability the jedi now have, 5 on 1 is impossible. 2 on one is near impossible.
And if you think for one minute that bh's will not shoot up a droid to get a mark, and then have others do the same thing until they get the same mark, your way out of touch with how some mental cases in this game work. They will do it, and for the sole purpose of greifing a jedi over and over and over simply because some bh's think they have a "higher cause" to eliminate jedi from the game. Which is crap. It's just an excuse to greif somebody.
They will , oh yes they will.
Farenheit wrote:
No offense tanks, but The system as is on test makes it so a bh actually has to do some work, and stalk his prey from afar before he attacks... What you really want is bh's to still have the ability to have 5 on 1 gank squads, no matter the jedi.. With todays healing ability the jedi now have, 5 on 1 is impossible. 2 on one is near impossible.
And if you think for one minute that bh's will not shoot up a droid to get a mark, and then have others do the same thing until they get the same mark, your way out of touch with how some mental cases in this game work. They will do it, and for the sole purpose of greifing a jedi over and over and over simply because some bh's think they have a "higher cause" to eliminate jedi from the game. Which is crap. It's just an excuse to greif somebody.
They will , oh yes they will.