Problem - Pulling while hunting stuck on LoS

[Leo]

RGMercs Build?

Most recent

What level is the character?

70

I noticed today when I was setting my SK up to hunt and when I set the pull ability to any spell, he will not move forward or nav to get into line of sight. He just stands there with the target, trying to cast, ignoring the "you can't see your target message." It use to move to the target when pulling until it got LoS then used the spell to pull. Seems like a check is missing somewhere but I haven't been able to narrow it down. I'm using most recent updated version with the Project Laz default SK config. I did verify that it is set to handle line of sight under the events settings as well.

 

[Algar]

Looks like an unintended change from yesterday.
Hilarious because I literally just noticed this on a set of stairs and a mob not in LoS, went to mention it in channel, and saw your post.

In my defense I tested over multiple hours XD

I'll get it fixed forthwith.

I noticed today when I was setting my SK up to hunt and when I set the pull ability to any spell, he will not move forward or nav to get into line of sight. He just stands there with the target, trying to cast, ignoring the "you can't see your target message." It use to move to the target when pulling until it got LoS then used the spell to pull. Seems like a check is missing somewhere but I haven't been able to narrow it down. I'm using most recent updated version with the Project Laz default SK config. I did verify that it is set to handle line of sight under the events settings as well.

 

[Leo]

Yea I figured it had to have been something recent as it was working fine until I just updated. Figured you all would be able to track it down faster than me if it's been changed recently. Thanks for keeping this beast running man!

 

[Algar]

Yea I figured it had to have been something recent as it was working fine until I just updated. Figured you all would be able to track it down faster than me if it's been changed recently. Thanks for keeping this beast running man!

Cheers for that, sorry for the miss. It didn't present because it required a mob to move out of LoS or a LoS to be improperly reported...
Either way, it should be fixed now (on github, or some time in the next hour when the launcher does its magic)
Edit: It literally updated as I posted this. Lucky timing or someone is watching this one and forced it, and cheers if that was the case

 

[Leo]

yea man back to working great! whatever magic you worked fixed it. Thank you good sir!

 

[Leo]

doh spoke too soon, so ruined city of dranik is good place to test. specifically because when it engages the pull routine to run up to a mob that is pathing, it will stop where it has LoS but then if the mob paths out of LoS before it cast's the pull ability it just stands there trying to cast the pull ability. Might need a LoS check before each time we go to use our pull ability if it's a spell or AA. Of course setting auto attack as the pull ability works fine as it navs to melee range to pull.

 

[Algar]

doh spoke too soon, so ruined city of dranik is good place to test. specifically because when it engages the pull routine to run up to a mob that is pathing, it will stop where it has LoS but then if the mob paths out of LoS before it cast's the pull ability it just stands there trying to cast the pull ability. Might need a LoS check before each time we go to use our pull ability if it's a spell or AA. Of course setting auto attack as the pull ability works fine as it navs to melee range to pull.

We have code that responds to the can't see message if you are pulling, can you ensure you updated, change your logging to debug, and let me know if you see any messages about "see"?

For clarity, the changes were blocking that pulling code from occuring, but this is no longer the case... so if there are still issues, I may have exposed another latent bug.

 

[Leo]

kk let me see if i can grab some debug messages for you.

 

[Leo]

[RGMercs:INFO 7721.227> (pull.Lua::unknown_func():2260)] >>> Pulling an elite ikaav sorcon [1367]

[Tue Nov 11 17:19:41 2025] You have been healed for 356 points of damage.
[Tue Nov 11 17:19:42 2025] You cannot see your target.
[Tue Nov 11 17:19:43 2025] You cannot see your target.
[Tue Nov 11 17:19:44 2025] You cannot see your target.
[Tue Nov 11 17:19:45 2025] You cannot see your target.
[Tue Nov 11 17:19:46 2025] You cannot see your target.
[Tue Nov 11 17:19:47 2025] You cannot see your target.
[Tue Nov 11 17:19:48 2025] Leoclr begins to cast a spell.
[Tue Nov 11 17:19:48 2025] You cannot see your target.
[Tue Nov 11 17:19:49 2025] You cannot see your target.
[Tue Nov 11 17:19:50 2025] You cannot see your target.
[Tue Nov 11 17:19:51 2025] ______'s casting is interrupted!

 

[Leo]

[INFO ] PULL::FindPullTarget Pulling an elite ikaav sorcon [1367] with Distance: 137
[DEBUG ] RTB Location: 875 -1020 -40
[DEBUG ] Found Target: 1367 - Attempting to Nav
[DEBUG ] RGMercs sent MQ Command: >> /squelch /attack off <<
[DEBUG ] RGMercs sent MQ Command: >> /nav id 1367 distance=200 lineofsight=on log=off <<
[DEBUG ] SetTarget(): Setting Target: 1367 (buffPopWait: 708)
[DEBUG ] SetTarget(): Set Target to: 1367 (buffsPopulated: true)
[INFO ] Pulling an elite ikaav sorcon [1367]
[DEBUG ] UseSpell(Terror of Discord, 1367, false)
[DEBUG ] Set Last Cast Result => CAST_RESULT_NONE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] UseSpell(Terror of Discord, 1367, false)
[DEBUG ] Set Last Cast Result => CAST_RESULT_NONE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Module Pull - save settings requested!
[DEBUG ] (Pull) DoPull is now: true | [Type : on|off ] | [Default: false ] [Previous: true ]
[DEBUG ] RGMercs sent MQ Command: >> /rgl pullstop <<
[DEBUG ] Module Pull - save settings requested!
[DEBUG ] (Pull) DoPull is now: false | [Type : on|off ] | [Default: false ] [Previous: true ]
[DEBUG ] RGMercs sent MQ Command: >> /grouproles set MODEDITEDOUTTOONNAME 2 <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] RGMercs sent MQ Command: >> /cast "Terror of Discord" <<
[DEBUG ] Set Last Cast Result => CAST_CANNOTSEE
[DEBUG ] ALERT: Pulling Disabled at user request.

 

[Algar]

I've confirmed that the code I have now properly detects the cant see events and reacts. Did you turn your can't see handler off?
Combat > Positioning.

I think that needs to be adjusted, regardless, if so, but the confirmation that it's the issue would be good.

 

[Leo]

I've confirmed that the code I have now properly detects the cant see events and reacts. Did you turn your can't see handler off?
Combat > Positioning.

I think that needs to be adjusted, regardless, if so, but the confirmation that it's the issue would be good.

I toggled it off and on to see if it would make a difference last night. It didn't matter what state the toggle was in; the result was the same, which is the log I pasted. I can test again today when I get home to pull more logs if you need. Whatever I can do to help, let me know.

 

[Algar]

I toggled it off and on to see if it would make a difference last night. It didn't matter what state the toggle was in; the result was the same, which is the log I pasted. I can test again today when I get home to pull more logs if you need. Whatever I can do to help, let me know.

I've pushed some updates to improve logging, but between that and the minor code changes I've made (none of which I think should fix this), I am unable to reproduce currently.
I wonder if the NPCs updated location is off-mesh... hmm, adding one more check to the abort conditions.
Either way, the fallback logic should break you out of this and temporarily stop the mob from being pulled, I would think.

 

[Leo]

I've pushed some updates to improve logging, but between that and the minor code changes I've made (none of which I think should fix this), I am unable to reproduce currently.
I wonder if the NPCs updated location is off-mesh... hmm, adding one more check to the abort conditions.
Either way, the fallback logic should break you out of this and temporarily stop the mob from being pulled, I would think.

Makes sense, I'll check when I can today. When I was testing last night, I went to a spot where I knew a mob was in range to pull like 100 away, but not in line of sight, and activated the pull routine. That's how I was able to generate the log files, as it would attempt to pull and not move, as stated before.

 

[Leo]

Seems to be working again after the update. Thanks again man you're awesome.