Development Cycle Archive
Thread: Publish 9 Feedback: Bounty Hunter Droids going to 0,0,0
Rarool
Thu Jul 01, 2004 1:33 pm
#14
Thank you first off for some attention. It is GREATLY appreciated by a large majority of the BH community.
Server: Bloodfin
Issue: Seeker Tracking
Arakynds seem to track very well now giving the planet correctly.
However, many many times the seekers seem to update the starport the Jedi
arrived at and never update from that position.
Once on planet attempts to send new Arakynds also update to the same spot in
the starport. The Jedi are not anywhere near the starport.
Ocu_Lus
Thu Jul 01, 2004 1:36 pm
#15
I tracked two Jedi last night and neither of the missions gave a waypoint to 0,0,0. The first gave the correct planet, Tatooine, but when I sent out seekers after I shuttled in, the waypoint did not update. I stumbled upon the jedi in the starport by pure luck, but he did not have a BH TEF even though I had not canceled the mission.
The second Jedi, my probe said was on Dath. Traveled to Dath, sent out seekers upon arrival, but again, the waypoint did not updated. I was unable to find him to verify if he had taken a TEF.
Server: Valcyn
Investigation skill: 3, working on 4.
Took both missions from Kadaara, first Jedi was tracked to Tatooine, second was tracked to Dath.
A small problem right now is, the developers removed all incentive to hunt Jedi. It costs quite a bit to travel to and from an advanced planet, droid costs, vehicle maintenance, buffs, etc, withwhat seems to be a90% chance that you will get nothing in return. Just something to consider.
NoShields
Thu Jul 01, 2004 1:38 pm
#16
I picked up a mission today in Kaadara. Arakyd reported the target was on Rori so I hopped a shuttle to Restuss.
The waypoint indicated the Rebel base starport so I sent out a seeker and let is do a full cycle of Find&Track. No movement.
I headed to the rebel base on the off-chance the mark was still in the area. No sign, just an empty waypoint at the spot where the jedi had arrived on planet.
I figured I had some time to kill so I set up a stake out in the corner house near the recruiter and waited, tabbing on to any new blips as they came in.
After 5 mins or so my mark came into radar range. I switched my MBH tag for Apprentice Carbine Specialist and went to play AFK possum by the gate I figured the jedi would come in through.
Sure enough he came in and as soon as he'd run past me and out of melee range I turned and laid a couple of SprayShots on him. Blocked.
Everything I threw at him was blocked. Of some 40 shots only 2 connected.
I tried to kite, all the time seeing my shots blocked but he closed the gap, KD'd me with SaberThrow and finished me execution style.
You really need to put some holes in that saber block if you want us to police these guys y'know.
Starscream1
Thu Jul 01, 2004 1:38 pm
#17
Since publish 9, I have noticed this bug much less often. However, the main cause of it before would be that the target was in an area that woudl be considered "inside." This could probably be best defined as an area which you would be unable to call pets or vehciles, use surveying skills, ranger tracking, or anything else you had to be "outside" for.
Currently, droids update withVERY limited functionality.
Droids only update when:
- The target uses a shuttleport or starport the waypoint is update to the spot the target arrived at.
- The target clones at a FORCE SHRINE, the waypoint is updated to the spot a target cloned at. THE WAYPOINT DOES NOT UPDATE IF CLONING OCCURS AT A REGULAR CLONING FACILITY.
Droids never update when:
- The target is in cities, the wilderness, houses, building, caves, on vehicles, mounts or at POI. The above conditions are the only one which cause waypoints to update.
ExSanguin8or
Thu Jul 01, 2004 1:40 pm
#18
Server: Sunrunner
Planet: Dantooine
Location: Just outside of the Ticket room at the Pirate Outpost, presumably the arrival area at that starport.
Details: Not exactly a (0,0) waypoint, but as with others posting here, the waypoint never updated. I never found the Jedi and had no contact with them. Sent several seekers out on Track mode and the waypoint never updated to a different location.
Planet: Dantooine
Location: Just outside of the Ticket room at the Pirate Outpost, presumably the arrival area at that starport.
Details: Not exactly a (0,0) waypoint, but as with others posting here, the waypoint never updated. I never found the Jedi and had no contact with them. Sent several seekers out on Track mode and the waypoint never updated to a different location.
meeuki
Thu Jul 01, 2004 1:42 pm
#19
in my experience the arkayd has only given me a 0,0 waypoint a few times. both times i had already tracked the jedi to a planet, recieved a valid waypoint, then launched a number of seekers that continually updated to that waypoint.
if i would then launch another arkayd it would update to 0,0.
last night i took a jedi mission from coronet, flew to kaadara, launched a arkayd outside of kaadara. it said yavin, i returned to coronet, then jumped to yavin. the arkayd waypoint was where a player would load at the outpost. unfortunately the jedi was at the shuttle so i did not have time to launch a seeker. =)
if i would then launch another arkayd it would update to 0,0.
last night i took a jedi mission from coronet, flew to kaadara, launched a arkayd outside of kaadara. it said yavin, i returned to coronet, then jumped to yavin. the arkayd waypoint was where a player would load at the outpost. unfortunately the jedi was at the shuttle so i did not have time to launch a seeker. =)
Southwick
Thu Jul 01, 2004 1:43 pm
#20
The 0,0 waypoint might be something of the minor issue.
The no update is the real issue here! I had thought that maybe it was a time issue. (ie. the arak locates the shuttleport where jedi last was, and locks that position. This is the last place the server recorded the player) I had thought after 30 min after server saved again we might get a new update, but no luck. Time makes no difference.
MOre info: Araks will not update waypoint if launched again on jedi planet.
Seekers will tell you if target is not currently on planet. Arak will update new planet and lock at last known starport.
The no update is the real issue here! I had thought that maybe it was a time issue. (ie. the arak locates the shuttleport where jedi last was, and locks that position. This is the last place the server recorded the player) I had thought after 30 min after server saved again we might get a new update, but no luck. Time makes no difference.
MOre info: Araks will not update waypoint if launched again on jedi planet.
Seekers will tell you if target is not currently on planet. Arak will update new planet and lock at last known starport.
Leana_Txorana
Thu Jul 01, 2004 1:53 pm
#21
You think the Dev's are going to get an easy time considering the communities current feeling toward them right now?
====================================================================
And isn't it amazing the devs have a hard time figuring out what the community wants when they look for information and have to data mine through off-topic posts to find the data they are asking for.
On the other hand, if people would stop posting off topic they would have an easier time getting the data they need and do the right thing. There were 6-7 replies before the first on-topic post for this thread. If they find the data they are requesting it will be a miracle.
Ziocyte
Thu Jul 01, 2004 1:58 pm
#22
I have attempted to track a dozen or so Jedi since Pub 9 went Live, here are some of my findings:
1. Since Pub 9 I have not encountered the 0,0 WP bug yet. This part of the system seems to have been corrected, a number of friend MBH confirmed this was the case with them in game as well.
2. The seeker droids DO track to an extent. The first WP I get is, in some cases, a place that I know for a fact the Jedi has been. (i.e. Jedi spooted by a friend, or in one case it was the Jedi's home city in wich the seeker reported a wp). After the first WP though, I have not been able to get an update. Here are a few postulations/observations I have made regarding this:
- The Seeker will report 1 waypoint over and over. this also applies to probot droid planet waypoints, being that the first waypoint recorded is the one that the driods stick with.
- The 1 waypoint that is given does seem to be an accurate representation of where the Jedi is or has been.
- One way to update correctly past the first waypoint is to relog and track again. example: Wednesday I pulled a Jedi mission of the terminal. Probot droid said he was on Dathomir. Flew to Dathomir and initial waypoint was about 3000m west of the norther outpost (can't remember the name off hand). I launched seeker droids wich would continue to update the waypoint to the exsact same spot as the initial waypoint. Once I made it to the waypoint, the Jedi was no where to be found, but the seekers would keep updating to the same spot. I then logged out of SWG, relogged and launched another seeker. This time the waypoint moved from the spot I was at to a spot about 2000m south of where I was standing. That waypoint then became the waypoint continuously updated to until i relogged again.
It is not confirmed that in the above example that the Jedi was actually in those spots given by the waypoints.
Thats all I can think of off the top of my head, i'll repost if I can think/find anyting else.
Ziocyte
Master Bounty Hunter
0/0/4/3 Pistoleer
glorfindel23
Thu Jul 01, 2004 2:02 pm
#23
Droids experienced one of two problems: Going to 0,0 or to the point in which the character (sometimes the Jedi, sometimes the Main) logged in/out at.
Since Publish 9 I have used Droids for 1 mission (Jedi have become easy to find without the Droid: take a mission in Coronet, walk over to the Starport where they are all demonstrating Force powers without fear of non-BH TEFs and without much fear of BHs winning if they do show up). Here it is:
Server: Naritus
Planet: Naboo
Location: Kaadara Mission Terminals outside Starport
Arakyd Launched: Outside Kaadara
Planet of Jedi: Endor
Probe Location on Endor: Load zone for Smuggler Outpost Starport
Repeated use of Probe Droids gave this same waypoint. At first I had expected the Jedi was there but shuttled out asI shuttled in, but after several Probe Droids updated the waypoint consistently to the same location, I knew this was not the case.
HOWEVER: I am not sure if this is a new or random bug or if it is the same "Logged In/Out here" bug that was existing side-by-side of the 0,0 one previously (I don't know if this is where the Jedi or the Jedi's main logged in/out or not). The Jedi was online throughout all this, so it was not the result of LD/relogging.
TheLateAnakinSolo
Thu Jul 01, 2004 2:04 pm
#24
TH, just a comment.
Moving jedi missions to MBH will prevent massive dabbler stackers from going after jedi. I mean, a jedi master can easily lose to a def stacker on live. It's just insane!
Plz do something about this.
questioneer
Thu Jul 01, 2004 2:06 pm
#25
it sounds like the issue with this is that the system is doing one of two things
1) it is returning the location of the jedi that is saved from when he logs off/ shuttles. It would make sense that the system wouldnt constantly update the location of every player on the server because this would chew up a lot of processing and such. It seems like the system would just cache the current location and when you log off or go link dead or shuttle it saves that location.
2) The bounty location is stored as a variable attached to the bounty hunter and is only updated every time the bounty hunters information is saved. So instead of taking the location of the jedi from the cache is it taking it from a saved variable somewhere.
and yes this has nothing to do with the 0,0,0 bug.
generelz
Thu Jul 01, 2004 2:13 pm
#26
It is my own personal belief (as a few of the more astute posters have observed) that the 0,0,0 waypoint bug was generally a problem that arose from Jedi that were AFK macroing XP inside their houses or other buildings. I've noticed many times that when attempting to make waypoints inside of buildings, etc. that you tend to get a waypoint of 0,0 or very close to that, apparently due to the fact that each house has it's own coordinate system on top of the world coordinate system.
With the new jedi system, for the most part I believe this would be gone. However, a good way to test this would be to get your QA guys to set this situation up:
1.)Have a jedi set up in a house or PA hall or other building with a few people around.
2.)Have this jedi then use force powers to accrue visability.
3.)Then have a BH pull a mission for that Jedi off the terminals and track him.
One of two things will happen:
a.) The BH will be able to track the Jedi to the location of the house, or
b.) The BH will be led to the "relative" waypoint of the jedi (i.e. the jedi's waypoint "in the house")
*by the jedi's waypoint in the house i mean that if the jedi were to create a waypoint in the house, it would make a waypoint with coordinates close to 0,0,0. Verify to see if the coordinates of the waypoint the jedi created (his relative waypoint in the house) are the same as the waypoint the BH has been lead to.
With the new jedi system, for the most part I believe this would be gone. However, a good way to test this would be to get your QA guys to set this situation up:
1.)Have a jedi set up in a house or PA hall or other building with a few people around.
2.)Have this jedi then use force powers to accrue visability.
3.)Then have a BH pull a mission for that Jedi off the terminals and track him.
One of two things will happen:
a.) The BH will be able to track the Jedi to the location of the house, or
b.) The BH will be led to the "relative" waypoint of the jedi (i.e. the jedi's waypoint "in the house")
*by the jedi's waypoint in the house i mean that if the jedi were to create a waypoint in the house, it would make a waypoint with coordinates close to 0,0,0. Verify to see if the coordinates of the waypoint the jedi created (his relative waypoint in the house) are the same as the waypoint the BH has been lead to.