Problem - Hunter targeting mobs from long distances out of LOS.

[rhiza]

RGMercs Build?

latest

What level is the character?

60

Hello,

I've noticed that when using hunter mode, every now and then especially on longish paths, it will abort the pull, then targets the mob (even if not in LOS) and then starts running to the same mob again.

This has happened on both roaming and static spawns.

I've tinkered with the pull distance in combination with the hunt distance and I have got it to stop pausing intermittently while running, however it is still targeting the non-LOS mob from fairly large (400+) distances away which looks suspect as hell.

 

[stuff]

Could it be a mob that was previously on xtarget, but not killed?
Or a mob near your other party member if you have them?

 

[rhiza]

Could it be a mob that was previously on xtarget, but not killed?
Or a mob near your other party member if you have them?

nah mate fresh mobs that have spawned ages away

 

[stuff]

What about your z axis? Doesn't seb have areas stacked on top of each other?

 

[Algar]

I'm not sure I understand the issue you are trying to convey, the script is targeting things within a range you choose to set, right?

Is it that the mob is being targeted at all when you don't have LoS? Do you think that charging exactly to a mobs location when you don't have LoS is any less suspicious?

Pausing while running means your PC was running so long without reaching a target that the script reevaluates, and I agree, it sometimes seems janky when you are using long distances, but again, these distances are user configurable if you find some of the behavior undesirable. Perhaps we could lengthen the time before the script will reassess slightly...

However, the ultimate answer here is to simply not use automation when you are unsure of who is nearby or watching and monitor your accounts regardless.

If I've misunderstood your point, please, enlighten me, with my apologies.

Edit: Forgot to mention, there are quite a few resources to help you quickly ascertain if someone is nearby. My personal favorite is https://www.redguides.com/community/resources/alert-master.2062/

 

[rhiza]

Thanks for the response mate. Let me see if i can clarify what i'm experiencing and what i think would be expected.

Couple of points:

• I don't think its time related. I've seen it work flawlessly how I would expect it with distances of 800+
  • When this happened, the closest mob was over 800 units away.
  • Hunter mode nav'd to the target spawn.
  • When in LOS, the hunter targets the mob and engages.
  • Kills mob.
  • Happy days.
• I think the behavior mentioned above is pretty normal and reasonable to be expected. In multiple instances on these forums, MQ dev's have stated that targeting mobs while not in LOS is generally a bad idea.
• When the hunter is NOT behaving correctly it usually looks like the following.
  • Hunter identifies nearest spawn, this can be any range.
  • Hunter nav's towards spawn.
  • At seemingly random times/distances the pull 'aborts' naving to the target.
    • I've seen this occur less than 200 distance and greater than 400 - 800 distance.
  • Hunter then targets the mob it was naving to, regardless of distance or LOS.
  • Hunter then nav's to the same / original target (since it's still the nearest).
  • Kills mob.
  • Less happy days.

Functionally, no difference, I tinkered with some settings specifically the pull distance and the hunter distance, which has removed some of the undesirable behavior when it 'aborts' the pull so it runs to the mob seamlessly now. However it is specifically still targeting mobs when they are not in LOS. at random points through out the pull (pathing to the nearest mob).

The fact that as i've mentioned it works fine at larger distances and longer pull times makes me suspect this is unintended.

 

[Algar]

Thanks for the response mate. Let me see if i can clarify what i'm experiencing and what i think would be expected.

Couple of points:

• I don't think its time related. I've seen it work flawlessly how I would expect it with distances of 800+
  • When this happened, the closest mob was over 800 units away.
  • Hunter mode nav'd to the target spawn.
  • When in LOS, the hunter targets the mob and engages.
  • Kills mob.
  • Happy days.
• I think the behavior mentioned above is pretty normal and reasonable to be expected. In multiple instances on these forums, MQ dev's have stated that targeting mobs while not in LOS is generally a bad idea.
• When the hunter is NOT behaving correctly it usually looks like the following.
  • Hunter identifies nearest spawn, this can be any range.
  • Hunter nav's towards spawn.
  • At seemingly random times/distances the pull 'aborts' naving to the target.
    • I've seen this occur less than 200 distance and greater than 400 - 800 distance.
  • Hunter then targets the mob it was naving to, regardless of distance or LOS.
  • Hunter then nav's to the same / original target (since it's still the nearest).
  • Kills mob.
  • Less happy days.

Functionally, no difference, I tinkered with some settings specifically the pull distance and the hunter distance, which has removed some of the undesirable behavior when it 'aborts' the pull so it runs to the mob seamlessly now. However it is specifically still targeting mobs when they are not in LOS. at random points through out the pull (pathing to the nearest mob).

The fact that as i've mentioned it works fine at larger distances and longer pull times makes me suspect this is unintended.

Cheers for that, I understand now.

I have some guesses (on both the issue and potential fixes), but best to wait on that until someone can have a look at the code armed with this info.

In the meanwhile, most pulling functions log to the debug channel, so if you can reproduce this, getting a log may be helpful.

I've never personally experience this issue, but I largely hunt in broad, open areas (which is why I have guesses).

 

[rhiza]

Cool cool, sorry I didn't explain myself better in the first place. I'll try get some logs this evening.