Development Cycle Archive
Thread: Publish 7 Feedback: Bounty Hunter Jedi Tracking Missions
WOOOOOOOOOWW!! Great job, Devs!
Really, great great job!! My 15 dollars are going to stop very soon.
Master BH on Naritus. Picked up a Jedi mission out of Kadarra. Very fast update from the Probot, saying Endor. Jump to Endor, put up seeker, very fast initial update, and follow up updates (22 seconds). Head to Jedi's location. Notice waypoint is not moving. Get to the waypoint and nothing. Jedi was online (friends list). Did an areatrack, and came up empty. Seeker keeps saying he is there. Searched the area while it reports. As soon as the 1st seeker ran out, I launched a second. It reports the Jedi as 2500 Meters away. Take off after him (he was heading to a starport). Notice that again the waypoint is not moving. Seeker runs out launch another, it reports him as another 2500 meters away at the starport. Get there, and it's time for my Spice Crash. He was there, so I get to watch him parade around while I lay there with 1 health. He was attackable. He was out of sight when the seeker ran out, so I put up another and it says he is still waiting for the shuttle. Spice crash goes, so I go after him, and he is not there. Seeker keeps updating saying he was right there, and he was not. I believe he jumped planet. Seekers appear to be way out of sync with their movements. I know there is some lag. But they are not moving 2500 meters in 22 seconds. And the last one I believe he had actually jumped planet. Even if he had not, it was telling me he was standing in front of me, and he was clearly gone. Seeker updated 10+ times to the same waypoint coords while I stood there.
I also had a weird one with an NPC bounty. Kadarra again. Probot says Naboo, I jump shuttle to Moenia. Get there, and I cannot generate my swoop, and cannot call Seeker or Probot. Did not have those options on their popup menus. I had left my bike out in Kadarra, but when has that ever mattered. When I returned to Kadarra everything was fine. Aborted mission in frustration.
Ohhh heres a good one:
BH 1 pulls mission for jedi kills jedi via 3 incap griefing (to keep mission), Jedi must clone (if they log out as a corpse they recieve another death count via bugs in the system)
A. BH 1travels to the Cloning facility, if lucky, jedi hasn't made it far away. Jedi, unable to log out in time, (or still ghosted in game) is killed, and when Jedi logs back in an extra death on top of it (for a total of +3 deaths from one mission).
B. The second BH2 in cohorts with the first, waits outside the Cloning facility. Upon the jedi cloning, BH 2 kills the jedi via 3 incap death (to keep mission) The jedi must clone, or face the extra death bug, however knowing that they will be killed yet again, by BH2 they choose to sit there and wait on a CSR from the chat room to come. Jedi is mad because by the time a CSR gets to him, he is Auto Cloned or has gone LD. (3 extra deaths from one mission)
P.S. DarkFett I am a Jedi on Ahazi and was playing all night. I choose not to use force at all, and avoid the grief of dying (chancing multiple deaths via available grief tactics) . You can point and say we are all afk, but some of us are using Tactics and playing our Jedi the way it was meant to be: careful. You can't complain about that.
Eventually people will avoid using force, unless they can anniahalate anyone comming close to them (long distance vision of a jedi) and BH's will get mad they don't have anyone to fight.
On a personal note I love being the hunted. I am the person who signs up for gimped BH tracking role play events on my main (who can defend herself) but the available grief tactics to this untested method is undeniably exploitable, and grief crazy.
Ok, here is how it works. You send out droids, if they have logged off at any time before you start tracking them whether or not you had the mission on them when the logged in/out,For some f'n reason, it says target offline... Another thing, sending a droid out and finding them is all dandy but the updates always have the same f'n waypoint for about 10 minutes. Finally it gives you another update, and you go there.... low and behold it does same thing. So if the jedi is moving you have no chance to find him (unless he stops moving for about 20 minutes).
Another gripe, if you have the mission on a jedi, all they have to do is logout, log in.. Jedi are unable to be tracked (you get "your target is offline" when he is clearly online).
If you call this "working bh missions" Please re-evaluate what you guys consider working. Because this is clearlybroken. I mean if you get lucky enough to find a fricken jedi, you don't even get paid withexp or money!These times on the droids updating to an actual waypoint the jedi is quite honestly asinine, if you think anyone is going to find a moving jedi.
Please, fix this crap sometime before the next publish, because I was hoping you guys made them work. They work on the rare occurence a jedi is logged in, afk on a 10-20 minute break. Otherwise they're just as bad as before.
Have a nice day.
Are we so stupid!?!
A guy get the jedi slot macroing every profession while he **edit**s with his girlfriend all the day, get the jedi and .... he uses macros AGAIN! And AGAIN!
Star Wars: An Empire MACROING!
Great job, really!
Thunderheart, what do u tell about this? Do u think we enjoy when a jedi is macroing on his balcony and a group of furious Bhs is insulting Devs and Soe?
Aluvia wrote:
The current system for hunting Jedi is nothing but sanctioned grief play.
I agree.
From your own Rules of Conductpage on the main SWG website
1. You may not harass or threaten other players.
2. To expound upon the general guidelines, you may not harass other players.
Harassment is defined as specifically targeting another player or group of players to harm or inconvenience them. Harassment can take many forms, as it goes to the state-of-mind of the person or Squad on the receiving end of the action. However, in order to account for those who are more sensitive than others, the CSR involved will make a determination as to whether or not thereported issuewould be considered harassment and act accordingly.
No matter how you try to justify it, BH missions are nothing more than sanctioned harrassment of one class of players by another.