• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver

Problem - Monk occasionally stops fighting

Joined
Sep 16, 2020
RedCents
1,799¢
I have a monk that I use for farming tradeskill components periodically in kissassist 'hunter' mode. Since the latest game update / Very Vanilla update, the monk periodically stops attacking while hunting around the zone. He will still riposte, but basically stops doing any active attacks or disciplines until either the mob dies from damage shield damage or from riposte damage. After that mob dies, he will continue hunting.

I think it may be related to adds in the camp detection algorithm. From what I've seen, I think the problem occurs when adds are not properly detected. I'm not 100% certain on this, but I don't seem to see an 'Add(s) detected in camp' message before the problem occurs. Has anyone else seen similar behavior, or have any suggestions?
 
Make sure your camp size and melee ranges align.
Melee like 75 camp 100 campexceeded 110

Unfortunately that didn't work. I've been watching behavior for a while, and it seems to happen right after one mob dies, and the character switches targets. I might have something to do with when it switches to a pet target, rather than an actual mob ... it kills the pet, and then doesn't attack the next mob. It seems to lose track of the actual mob for attacking, although the next mob is targeted. It's very strange.

I've run this character like this periodically for months though, and never had any problems until this patch, so this is definitely a new problem.
 
There were some changes made to the hunter code. In hunter mode, when searching for mobs, it now uses your current location and not your camp location. Then searches for mobs in MaxRadius range. Also depending on what you have ReturnToCamp set to in your ini file, the hunter will return to camp or not after all mobs are dead.

Check and make sure your not getting a invalid path navigation message. May need to capture a debug log of this happening, that will let us figure out where in the code the character is stuck and why.
 
There were some changes made to the hunter code. In hunter mode, when searching for mobs, it now uses your current location and not your camp location. Then searches for mobs in MaxRadius range. Also depending on what you have ReturnToCamp set to in your ini file, the hunter will return to camp or not after all mobs are dead.

Check and make sure your not getting a invalid path navigation message. May need to capture a debug log of this happening, that will let us figure out where in the code the character is stuck and why.
How do I submit the logs? I caught it happening twice this morning.
 
I wanted to piggy back off this thread because im having this exact issue. Was there ever any resolution ?
I added the following to start attacking when my character is just standing there like an idiot:

DPS1=command:/keypress 1|100

And then I added a hot key for the '1' keypress that does /attack on

It's a workaround but has been mostly stable for me. I never marked it 'solved' since it's really a hack.
 
I actually was able to use DPS1=command/melee attack|100 and it seems to have fully fixed my problem. It sounds like either line is the same workaround.
 
I have a monk that I use for farming tradeskill components periodically in kissassist 'hunter' mode. Since the latest game update / Very Vanilla update, the monk periodically stops attacking while hunting around the zone. He will still riposte, but basically stops doing any active attacks or disciplines until either the mob dies from damage shield damage or from riposte damage. After that mob dies, he will continue hunting.

I think it may be related to adds in the camp detection algorithm. From what I've seen, I think the problem occurs when adds are not properly detected. I'm not 100% certain on this, but I don't seem to see an 'Add(s) detected in camp' message before the problem occurs. Has anyone else seen similar behavior, or have any suggestions?
Did you ever think that he just gets tired of being the worst DPS class in the game and was protesting? Just saying...

On topic: Have you checked the mesh for that area? Back in the day, my SHD did the same thing in Shard's Landing at two particular areas because the mobs would agro, but I was in a no-path zone. It was quite odd. Had to fix the mesh and then it worked.
 
Problem - Monk occasionally stops fighting

Users who are viewing this thread

Back
Top
Cart