Behind target check (proof of concept)

[Ultraviolence]

Here's a new method of checking your position relative to your target (sort of). Basically, it'll parse an error frame, and when the message "You must be behind your target" fires it'll run your code (or return true or false if you want).

Rogue example:

if not behindCheck then
    behindCheck = CreateFrame("Frame")
end

local frame = behindCheck
frame:RegisterEvent("UI_ERROR_MESSAGE")
frame:SetScript("OnEvent", function(self, event, ...)
	if (select(1,...):find("behind") ~= nil) then
		CastSpellByName("Gouge") --do stuff here
	end
end)

CastSpellByName("Backstab");

It may be useful to add a timer function to this as well.

[_Mike]

The only problem with this code example is that it is kinda ineffeciant, and will cause frame lag. I haven't found a workaround yet (or at least not one I could understand), so if a more experienced addon developer could chime in or PM me, that would be awesome.

Every time you run the macro you create a new frame. So after a while you'll have hundreds of frames processing combat log events.

[CrazyCactuaR]

Every time you run the macro you create a new frame. So after a while you'll have hundreds of frames processing combat log events.

Would you know how to close/delete the frame once it's finished? On a whim i guess;

a:UnregisterEvent("COMBAT_LOG_EVENT_UNFILTERED");

may work but untested.

[wowsc4p3]

Making it cast stealth is pointless; it will require standing behind the enemy and in stealth. make it cast shadowstep

[CrazyCactuaR]

Making it cast stealth is pointless; it will require standing behind the enemy and in stealth. make it cast shadowstep

It's for assasination spec isn't it?

[Ultraviolence]

Would you know how to close/delete the frame once it's finished? On a whim i guess;

a:UnregisterEvent("COMBAT_LOG_EVENT_UNFILTERED");

may work but untested.

Thanks for reminding me about that, I added it in and it helped a lot, although there is still a frame rate dip (40-50 frames lost), at least it doesn't freeze the screen. It's not too big a problem for me but I don't know how it would affect an older system. I should also note that it's always good to have an addon such as Combat Log Fix which automatically resets the combat log if it ever bugs out.

Every time you run the macro you create a new frame. So after a while you'll have hundreds of frames processing combat log events.

Do you have a solution?

[Ultraviolence]

Updated the main post with the new working script.

[d3deadl0rd]

Can someone plz explain how to use that? What should i add to paste it in macro and use?

[Iaccidentallytwink]

I am quite surprised this didn't get any attention when it was posted... does this still work? It's quite good.

[d3deadl0rd]

I wonder i could have any script working the same way. I need hemo infront and ambush from behind/ guess there is something like that just cant find it for sad.

[Ultraviolence]

I am quite surprised this didn't get any attention when it was posted... does this still work? It's quite good.

Yes, it still works. It was implemented into PQRotation as well.