Bounty Hunter Archive
Thread: How to avoid losing a Bounty Mark during your Investigation
KaiRan wrote:
Ok I have 2 minor comments to add, other than the obligatory Horay! Great post! and Love the Lightning Cone trick! thankyouthankyouthankyouthankyou
1) The wayfar cantina thing, and one or two other spots I have come across in cities repeatedly, is definately a programming error. I have confirmed on MANY occations, including 1 or 2 I delibrately stuck out there, that the ending "stuck in wall" coordinates are ALWAYS THE SAME! I think this may indicate the root of the problem: Invalid "legal" spawn coordinates in cities. Not just the cantina in wayfar, but a few others, incl one of the cities on Naboo, have a similar invalid point I was gauranteed to find my mark stuck in if I interrupted their travel there.
Yep. This happens SO often here and is why this location is on the list of Number 2 spot to avoid during your hunt (second ONLY to the badge locations ((north of Eisley)) on Tat. as well). One day thay will fix this. Hehe.
2) Would anyone object at all to having all the Investigate 1+ marks be RED dots instead of yellow? This would certianly solve the majority of my bugged missions, as just being near my "stuck-in-wall" mark would force them to aggro and run for me! I have been very successful in avoiding detection on other types of red-dot NPCs and still getting off my first few shots without immediate detection.
I have suggested this and it WOULD fix 95% of all lost TEF issues. But there were good counter points, like what would happen if the mark was already at the starport when you got there and he killed you before you were drawn in?
I personally find the challange of creeping up on one of these both more rewarding and more realistic when approaching a target that should know you are comming, according to the text in the mission. Just a thought. I figure this way, we have offset a bug fix with a means of making the missions a bit more challanging, shutting down the cries from MBHs not to fix.
/bump because someone sent me a nice PM thanking me for the work begun here...
... and the task is still at hand. Keep up the fight and keep posting what you see, no matter how insignificant and perhaps we will lick this thing before even the DEVs do 
. LOL.
nice thread....ill keep that all in mind...
riddle me this ::
why is it that mob missions are like 90% or greater (always there) inv 4 missions much less?
/bump
cause too there are too many rant threads.
great resource here... ***** rating!
TheWildJedi wrote:
Yet another satisfied customer. But they will not sticky this... and that is fine...because it does not promote discussion, but mearly a workaround for bug issues that have plagued this profession since day 1.
That's stoopid. Tanks has the power to sticky this, and it's the single most important bounty hunter post. More important, even, than our "top 5 issues". No. one issue is "investigation bugs", and this is the workaround for most of them!
/bump, /sticky, /love
grommond wrote:
Just want to point out I'm doing pretty well thanks to the suggestions here. Used a camp to clear a tree on a mark that was stuck inside. I have run into a problem with Dantooine in particular where marks will be close to their destination by the time I get there, I wait my 4 minutes before launching the seeker and find out that they are already at the town for their destination. I shuttle over there at first opportunity and the WP is sitting at that spot right by where the starport lands under the awning, but no mark. I run around outside town looking for him and no luck. I launch another seeker and it still says he is at that spot. Note that the mark did move to that spot from where the original probe had him. Any ideas?
This is pretty common for me at the starports on Dath. and Dan. I am not sure if the mark was supposed to have left the planet or if there is another kind of missing mark issue. I did catch a mark once in exactly the spot you describe, under the awning for the shuttle. He was actually under the shuttle I came in on and was white dot, unattackable. I hoped when the shuttle left I would be able to attack, but of course I couldn't.
I have also had quite a few marks inside the wall of ther terminal building but have had some sucess drawing them out by attacking other npc's with lightning cone.
Anyway, I have 5 more missions to hit MBH and then I will just be running missions for fun and credits. Maybe the failures won't bother me as much
BetaPlaya wrote:
grommond wrote:
Just want to point out I'm doing pretty well thanks to the suggestions here. Used a camp to clear a tree on a mark that was stuck inside. I have run into a problem with Dantooine in particular where marks will be close to their destination by the time I get there, I wait my 4 minutes before launching the seeker and find out that they are already at the town for their destination. I shuttle over there at first opportunity and the WP is sitting at that spot right by where the starport lands under the awning, but no mark. I run around outside town looking for him and no luck. I launch another seeker and it still says he is at that spot. Note that the mark did move to that spot from where the original probe had him. Any ideas?
This is pretty common for me at the starports on Dath. and Dan. I am not sure if the mark was supposed to have left the planet or if there is another kind of missing mark issue. I did catch a mark once in exactly the spot you describe, under the awning for the shuttle. He was actually under the shuttle I came in on and was white dot, unattackable. I hoped when the shuttle left I would be able to attack, but of course I couldn't.
I have also had quite a few marks inside the wall of ther terminal building but have had some sucess drawing them out by attacking other npc's with lightning cone.
Anyway, I have 5 more missions to hit MBH and then I will just be running missions for fun and credits. Maybe the failures won't bother me as much
Yes, this is very common and as I stated earlier in this thread somewhere... when a mark reaches a starport, he is supposed to "jump on a ship" and head off planet.
This does happen, but rarely... what normally happens (and this is a different bug and should be /bug ged early and often) is that the mark will vanish like he is supposed to, but the droids never update that he left the planet... they only report the last spot he was at before he got on the ship.
SO... in this instance... the droids are bugged and there in no workaround for this right now. This is NOT the typical bug where the mark is there, jusy invisible for you to try to find a way to get him to draw out. He is really not there anymore.
Wish I had better news.
Thewildjedi:
Yes, this is very common and as I stated earlier in this thread somewhere... when a mark reaches a starport, he is supposed to "jump on a ship" and head off planet.
This does happen, but rarely... what normally happens (and this is a different bug and should be /bug ged early and often) is that the mark will vanish like he is supposed to, but the droids never update that he left the planet... they only report the last spot he was at before he got on the ship.
I have never had a mark leave a planet correctly. I assume that a seeker would tell me they were not on planet or something like that and I would need to use another probe.
OMG!!!!!
I THINK they added in a partial fix to this like some of us suggested here... change the TEF to agrro and put it on the mission and the mark.
WELL... that is ONE way to fix this... not the best... BUT I think the red marks now go "red" so they do not become white...
LOL
it is like... IF you get a mark pinned and he is going to become white... he become RED instead so at least you can attack him.
LOL... nice one DEVs.. way to sneak it in there.