Dead SoftInteract unit prevents engaging in-melee range body pulled mobs

[tirisfalstudio-dot]

Description

Hello, i have had this bug since i've been using the bot (a little bit more of a year) basically the bug is mostly with melee class. It happens when the bot starts combat with a target and body pulling another mob while on the way/fighting the first target. As soon as the initial target dies, the bot stays stuck on the dead mob ignoring completely the one it body pulled until dying. I have it on video and i will attach it.

I'm playing on classic anniversary servers at the moment.

Is it something i'm doing bad or is it a known issue ? Thanks

Addon Version

1.7.70

World of Warcraft Client

World of Warcraft Classic

Reproduction Steps

1. Use a melee profile
2. Voluntarily body pull a mob while on the way to the fight

Last Good Version

No response

Screenshots

fefb4ebe-d40c-4302-b114-2e61be4bb640.mp4

Logs

l.txt

[Xian55]

Gooday!

It is kind of a known issue, i've been experienced many times in the past.

NO Plan basically means that there are no suitable Goal which would fulfill the minimum requirements to execute the plan.

Thanks for uploading the video, and sharing some minimum logs about the case. After carefully watching the video i can notice that you are using Soft Target System. After killing the first enemy the "targeting circle" around it remains so that corpse remains the soft target.

Meanwhile the attacking unit also has the circle which presumably becomes your primary target.

After doing some experiments which the soft targeting enabled i've noticed this edge case.

Basically what should happen is, your character supposed to interact with the corpse, in order to get rid of the soft target, in the current situation the loot action supposed to be quick, however for some reason it does not happening.

If you could share your class profile, i might be able to reproduce the issue.

[tirisfalstudio-dot]

Thanks as usual for the very fast answer, and Happy New Year btw!!! Here's the profile, i'm available to help in any way.

Rogue_10.json

[Xian55]

Thank you and happy new year to you as well.

Sadly since i have to debug Soft Interact related issues i cannot conduct on my own lab, this might take some time to fix.

[tirisfalstudio-dot]

Thanks a lot. If i can do anything to help please let me know

[Xian55]

I've noticed the issue before: 6e5ca63

I've tried to fix the issue but it did not always resolved the issue based on my testing, so it is currently dead code.

---

So i've managed to create a melee class on the TBC PTR as there i have access to the Soft Target capability.

I have to say i managed to reproduce the issue, it was quite easy. Essentially the same situation what you sent in the video.

It's quite easy to reproduce the issue really.

As of now i don't have a full, foolproof solution to the issue however i can provide a workaround

TLDR:

"Combat": {
  "Sequence": [
    // ... other more important combat actions ...
    //
    // add the following at the end of the Combat Sequence
    {
      "Name": "Unstuck SoftTargetDead",
      "Key": "D",
      "Requirements": [
        "SoftTarget && SoftTargetDead" // might be safe to use 'InMeleeRange &&'
      ]
    }
  ]
}

So your Rogue profile Combat section should look like this

      {
        "Name": "Lesser Healing Potion",
        "Key": "F12",
        "InCombat": "true",
        "WhenUsable": true,
        "Requirements": [
          "Health% < 15"
        ]
      },
      {
        "Name": "AutoAttack"
      },
      {
        "Name": "Approach",
        "Log": false
      },
// ---------------------------------
      {
        "Name": "Unstuck SoftTargetDead",
        "Key": "D",
        "Requirements": [
          "SoftTarget && SoftTargetDead" // might be safe to use 'InMeleeRange &&'
        ]
      }
    ]
  },

temp_solution.mp4

---

Long story

In prior of the Soft Interact system (that was almost the end of TBC Classic), for melee classes i was relying the auto attack, error message You are facing the wrong way! to correct the player direction to make sure it faces the target all the time.

However when i was initially incorporated the Soft Interact / Soft Target system into the project i was not really thorough.

WowClassicGrindBot/Core/ClassConfig/ClassConfigurationBaseActions.cs

Line 38 in fee9a54

Requirement = "!SoftTargetDead"

WowClassicGrindBot/Core/ClassConfig/ClassConfigurationBaseActions.cs

Line 46 in fee9a54

Requirement = "!AutoAttacking && !SoftTargetDead"

Commit: b255d90

Core: ClassConfigurationBaseActions: Approach and AutoAttack has a predefined Requirement to prevent colliding with Soft Targeting feature if its enabled...

In the two mentioned code snipped i've added guard rails to prevent the following situation:

• As ranged you killed a mob far away
• Between your stationary - far away - location and the corpse there was in-between a flower
• When the bot pressed the Interact / Approach key the player started moving towards the corpse.
• • Over the years the Interact with target key functionality has been changed couple of times by Blizzard.
• • There was a time when pressing the Interact key it once was enough to reach the corpse. (unless there were some tricky terrain in the way which might block the player movement)
• • Later on - the current implementation - is basically periodically pressing the Interact key, after some trial and error this solution seems to be more reliable then pressing the button once.
• However midway due the unlucky positioning the flower would get higher priority, stopping the player and starts to interact with it.

So this aspect of the project requires more thinking on my end to make it more bullet proof.

The temp solution should work, not so long ago i've introduced a way to "remember" 0cd3038 where the last target was killed, during death, assuming the player was facing the target i did some math to calculate the potential corpse location in a range. Then thanks to the Soft Interact system i have a way to "rediscover" the corpse later.

These small change allowed me to decouple the formerly tightly coupled loop of Combat -> Loot -> Skinning.

[tirisfalstudio-dot]

Amazing job, will try the new code in my combat sequence !! Thanks so much

[tirisfalstudio-dot]

Workaround works great! Thanks for the help

[Xian55]

Working on a fix, its somewhat annoying issue, when a dead softtarget exists, it has precedence over your primary target when it comes to Interact with Target hotkey :(

Here's my current progress:

Desktop.2026.02.01.-.23.25.51.02__multi_target.mp4

Desktop.2026.02.01.-.23.41.27.03__multi_target_2.mp4

[misterkoko]

Working on a fix, its somewhat annoying issue, when a dead softtarget exists, it has precedence over your primary target when it comes to Interact with Target hotkey :(

Here's my current progress:

Desktop.2026.02.01.-.23.25.51.02__multi_target.mp4
Desktop.2026.02.01.-.23.41.27.03__multi_target_2.mp4

Are you able to share the new progress code or do we just keep using the code from the workaround mentioned here #720 (comment)

[Xian55]

My current progress not yet covers all the edge cases.

As soon as i will be ready, it will be available.