TargetGUID problem

[Pimpace]

Hey Guys!

First of all, I'm using an OOP bot without any injection.

CurrentTargetGUID = 0xA96188 for 4.2.0 14333

I'm having a little problem about TargetGUID. In previous wow versions when I write a GUID in TargetGUID memory offset, wow has changed the target, and target frame has appeared, everything went fine. Now when I put a GUID here, wow just does targeting in "half way". You only can see now the target red-circle selector around the target, but there is no target frame at all, and in this case bot can't read any target information.

Any of you have this problem yet? There is any solution for this? I mean, maybe we need more than one offset to be written, or something like that.

Any hint, idea would be appreciated!

Thanks

[lanman92]

Easiest fix would be to call the TargetUnit function instead of hacking it and slapping a value into a field.

Reverse the lua function TargetUnit. I think that's the name of the function.

[Edit]
Since your out of process(sort of), you may want to write to the LastTarget offset, and hit a hotkey which does target last target.

[Frosttall]

Since your out of process(sort of), you may want to write to the LastTarget offset, and hit a hotkey which does target last target.

Really good idea


Lets see if there is still the old structure (just the GUID) or a new struct like now.

[lanman92]

Not my idea. I think Shynd had a post about it on his blog or something.