Bounty Hunter Archive
Thread: Edge of map, in the water, mission incomplete
Except Jedi right?
Aristoi wrote:
I've played SWG since week 2. I've been a Bounty Hunter since Oct 03. Here's a few tips of the trade to avoid losing marks.
- When your marks stuck inside something your pretty much SOE err SOL. Pre-CU you use to be able to AoE attack something near by to agro it and get it out. With LoS added in the CU AoE attacks now don't hit things you can't see, nor do they pass thur walls as they use to pre-cu. With the pet agro fix for CH you can't send in a droid or pet to draw them out either. The only way I've gotten marks unstuck was to get CS to come walk them out for me, even had a CSR fight me with my mark afterfreeingit. But Aristos SWG CS suxors. Na, not really, everytime I've asked CS to help they've answered within 10 mins. How do I get such fast response? In my ticket I send it in under: I'm stuck performing an action. I make sure to include: my toons name, what planet I'm on, my way-point, my marks name and way-point, the closest starport. While most times CS comes right out to help I have had a few tell me I sent the ticket in under the wrong catagory and to re-send it under missions interactive NPC's. Either way they've always come out and freed my mark.
I'm sure theres other tips I could give but thats all I have for the moment.
To whoever said "i don't think workarounds are acceptable in this state (aka everybody leaving) of the game.", well I for one am going to leave if they make this game any easier.
To whoever said limit the number of mark spawns even more?! Worst idea ever! Would you like some kind of afk-macro BH-mark-tracking thing while they're at it? "OMG I have to click ctrl-v! OMG my brain can only handle the numbing sensation of 3-click grinding! This is frustrating and I'm having a negative player experience! WAAAAH!" Cry me a river.
To whoever upchucked that pseudo-code, just APPLY FOR A JOB!
Just suck it up, you have been given plenty of advice in this thread on how to get through this. And that's unfortunate, because this isn't even very hard to figure out on your own. It isn't some kind of extreme game breaking bug either.
You're a bounty hunter - grow a pair.
I can accept the technology limitations that make it impratical (I wont say impossible) to prevent the situation of the calculated spawn point occuring over water or off the edge of the map.
What I don't understand is why a fail-safe can't be implemented to allow the mission to continue even when this does happen. Rather than resulting in a "mission incomplete", why not create a routine that compensates for it? Perhaps a mission update that the probe had been following false readings and then require the player to launch a new seeker to find the target's real trail. On the backend the system calculates a newvector for the target, just like it would when the player first lands on the planet.
Thunderheart wrote:
Havoc420 wrote:
Ok...I'm not a BH but I have friends who are...here is my question in regards to this being a technical issue...
If the game code knows where all the water, trees, housing etc is....why would the game generate the marks position IN the water or a house etc? How is THAT a technical issue is the code KNOWS where these things are yet it generates the mission IN them?
As I said, I'm not a BH...but this doesnt sound like a technical issue..more like a coding issue. Please explain further TH if possible.
Well, the code doesn't know where the water or the houses are. They are actually different sub-systems. One system generates the terrain. Another keeps track of where you are and where all the player structures are. Another is a kind of "find good location" system. It has to talk to all the other systems to make its best guess. I'd go into it further, but I'm afraid the discussion wouldn't stay on track or keep a level tone.
We are always working to improve this though and thats the important part.
Like I said, Blix tightened it up as much as possible, but when you have a dozen servers talking to each other about a moving location across a dynamically generated terrain, the number crunching gets pretty crazy.
i've found a work around for this problem.
launch a single seeker and wait at the starport till it gives the target lost message,launchanother seeker and he should have moved(hopefully away from the water).it's still quicker than cancelling and going back to get another mission
Thunderheart wrote:
Havoc420 wrote:
Ok...I'm not a BH but I have friends who are...here is my question in regards to this being a technical issue...
If the game code knows where all the water, trees, housing etc is....why would the game generate the marks position IN the water or a house etc? How is THAT a technical issue is the code KNOWS where these things are yet it generates the mission IN them?
As I said, I'm not a BH...but this doesnt sound like a technical issue..more like a coding issue. Please explain further TH if possible.
Well, the code doesn't know where the water or the houses are. They are actually different sub-systems. One system generates the terrain. Another keeps track of where you are and where all the player structures are. Another is a kind of "find good location" system. It has to talk to all the other systems to make its best guess. I'd go into it further, but I'm afraid the discussion wouldn't stay on track or keep a level tone.
We are always working to improve this though and thats the important part.
Like I said, Blix tightened it up as much as possible, but when you have a dozen servers talking to each other about a moving location across a dynamically generated terrain, the number crunching gets pretty crazy.
HERE IS HOW TO AVOID MARKS SPAWNING IN WATER:
- Look at your planetary map
- If the mark waypoint if over water - go make a coffee
- Come back to find the waypoint has moved several hundred meters
- Go kill the guy
- Loot him
- Drink the coffee
Quiet420 wrote:
we shouldn't have to use workarounds.
Well it's either use a workaround, or don't complete the mission, so you go your way and I'll go mine.
Quiet420 wrote:
800,000 people already went their way while you went yours....meanwhile 3 mil more people tried wow...and 1.8 mil are still playing it....we need small things like this fixed....not workarounds.
So go design a fix for it. I'm sure TH would be glad for the help.
Quiet420 wrote:
there are two at the end of the previous page...guess you didn't look.
No, there are two ideas at the end of the previous page - I can come up with awesome ideas all day long, but ideas don't mean jack without someone to work out a practical way to code and implement them.
Katalisha wrote:
Quiet420 wrote:
we shouldn't have to use workarounds.
Well it's either use a workaround, or don't complete the mission, so you go your way and I'll go mine.
Everyone understand how to use the workaround and the workaround is viable.
The issue is that a fundamental mission type that is unique to SWG is a failure simply because the subsystems cannot interact well with each other.
Its like when you used to log off for 20mins to get rid of bad buffs. Sometimes you got a buff that was so bad you simply couldn't play because you'd have health or action costs. Could you work around it, yes. Was it better for the Devs to adjust the game so you could overbuff bad buffs, yes.
The frustration is not that people can't complete BH missions that are in water, the frustration is that such a bug still exists after 2 years.