target

[g-unot]

How do you do to target mobs in 6.0?

[jimmyamd]

you click on them

[jimmys96]

you click on them

and this is relevant to memory editing how exactly?

[g-unot]

Nvm didnt realise GUIDs are 16 bytes now.

Anyway tho, when you target something, do you just write to the address or do you inject / call something?

[DarkLinux]

Nvm didnt realise GUIDs are 16 bytes now.

Anyway tho, when you target something, do you just write to the address or do you inject / call something?

really? I think every tut out shows you how to do it... And you sound crazy, b/c you write the GUID of what you want to target... You could also call a function, but it does the same thing...

[g-unot]

really? I think every tut out shows you how to do it... And you sound crazy, b/c you write the GUID of what you want to target... You could also call a function, but it does the same thing...

Im just curious. Maybe if you use call , the ui will update too

[semar]

Write GUID to lasttarget and then use "/targetlasttarget"

[g-unot]

Write GUID to lasttarget and then use "/targetlasttarget"

Good idea, thanks

[JuJuBoSc]

Or just call CGGameUI::Target and let the game do the magic for you

[provirus]

I hope someone can help me. I have a feeling that I made ​​a stupid mistake.
I'm using this code for targeting:

internal static unsafe void TargetUnit(UInt128 guid)
{
    lock (FASMLock)
    {
        IntPtr address = _wowProcess.Memory.AllocateMemory(sizeof(UInt128));
        _wowProcess.Memory.Write(address, guid);
        string[] asm = {
            "mov eax, " + address,
            "push eax",
            "mov eax, " + (_wowProcess.Memory.ImageBase + WowBuildInfo.TargetUnit),
            "call eax",
            "add esp, 0x16",
            "retn"
        };
        try
        {
            InjectVoid(asm);
        }
        catch
        {
            // Log
        }
    }
}

WowBuildInfo.TargetUnit = 0x903527;
After calling WoW just closes without errors. Please help

[-Ryuk-]

I hope someone can help me. I have a feeling that I made ​​a stupid mistake.
I'm using this code for targeting:

internal static unsafe void TargetUnit(UInt128 guid)
{
    lock (FASMLock)
    {
        IntPtr address = _wowProcess.Memory.AllocateMemory(sizeof(UInt128));
        _wowProcess.Memory.Write(address, guid);
        string[] asm = {
            "mov eax, " + address,
            "push eax",
            "mov eax, " + (_wowProcess.Memory.ImageBase + WowBuildInfo.TargetUnit),
            "call eax",
            "add esp, 0x16",
            "retn"
        };
        try
        {
            InjectVoid(asm);
        }
        catch
        {
            // Log
        }
    }
}

WowBuildInfo.TargetUnit = 0x903527;
After calling WoW just closes without errors. Please help

Here, use this

"push " + guidCave,
"call " + GeneralHelper.RebaseAddress(Offsets.WoWFunctions.CGGameUI__Target)),
"add esp, 0x4",
"retn"

Also, you should learn what add esp does... The reason your wow closes/crashes is you removed way to much :P

[provirus]

Here, use this

"push " + guidCave,
"call " + GeneralHelper.RebaseAddress(Offsets.WoWFunctions.CGGameUI__Target)),
"add esp, 0x4",
"retn"

Also, you should learn what add esp does... The reason your wow closes/crashes is you removed way to much :P

AAAAH! Before WoD we used value, not pointer. Something broke in my mind, and i replaced <<add esp, 0x8>> (old guid size) with <<add esp, 0x16>>. My bad, thank you!

[-Ryuk-]

AAAAH! Before WoD we used value, not pointer. Something broke in my mind, and i replaced <<add esp, 0x8>> (old guid size) with <<add esp, 0x16>>. My bad, thank you!

Add esp, 0x8 wasn't for the size of a GUID, its to remove items from the stack...

[provirus]

Add esp, 0x8 wasn't for the size of a GUID, its to remove items from the stack...

Hm, sorry, I don't understand. Old GUID (8 bytes) = hidword (4 bytes) + lodword (4 bytes). I pushed them to stack. So I should add to stack pointer (4+4 = 8) after cdecl calling. Am I wrong?

[-Ryuk-]

Hm, sorry, I don't understand. Old GUID (8 bytes) = hidword (4 bytes) + lodword (4 bytes). I pushed them to stack. So I should add to stack pointer (4+4 = after cdecl calling. Am I wrong?

No... What I mean is, you pushed two 4 byte values to the stack... thats why you pop 0x8...

With SmartGuid, you are pushing a 4 byte pointer... so you only pop 0x4