[HowTo] Get remaining breath/exhaustion/feign death time

[xalcon]

Hello everyone.
Time to contribute something
My bot died sometimes due to a calculation error... he tried to fly over the great sea :x I was able to fix this error, but in the same time I asked myself how to add an additional security layer to prevent those things in the future. So I decided to reverse the lua_GetMirrorTimerProgress() function and this is the outcome:

// Static Offsets
static uint currentTime_dword = 0xAC7318;
static uint mtpOffset = 0xAD76F8; // Mirror Timer Progress
// Types:
// 0 = Exhaustion
// 1 = Breath
// 2 = Feign Death
public static double getTimeRemaining(int type)
{
    int currentTime = Memory.ReadInt((uint)Memory.MainModule.BaseAddress + currentTime_dword);
    uint pMtpArray = (uint)Core.Memory.MainModule.BaseAddress + mtpOffset + (uint)(7 * type * 4); // 7 = ArraySize, 4 = Integer Size :>
    int maxTime = Core.Memory.ReadInt(pMtpArray  + (uint)4 * 1);
    int modifier = Core.Memory.ReadInt(pMtpArray   + (uint)4 * 3); // Seems always to be -1
    int timerStarted = Core.Memory.ReadInt(pMtpArray    + (uint)4 * 6);
    return maxTime + modifier * (currentTime - timerStarted);
}

I hope this is helpful for someone

v(o.o)

[DarkLinux]

Is that server side?... never really looked at that...

[xalcon]

well, I'm not sure... I think it is client side, but I don't have checked what happens when I modify the timerStarted or the maxTime value. I'm not interested in such haxx :>

[namreeb]

It used to be server side. If you look at the GetTickCount() speed hacks, the breath bar would be long gone well before you started taking damage. In other words, you would not take damage more quickly, despite the speed hack. Note that this is different than, for example, fall damage, which (last time I did WoW stuff) was entirely tracked and reported client side.

[Cypher]

It used to be server side. If you look at the GetTickCount() speed hacks, the breath bar would be long gone well before you started taking damage. In other words, you would not take damage more quickly, despite the speed hack. Note that this is different than, for example, fall damage, which (last time I did WoW stuff) was entirely tracked and reported client side.

I have not looked in a long time either, but afaik they started sanity checking some of the data you send back to stop some of the no-fall-damage hacks. Easy to bypass though...

[lunitune]

Thanks xalcon, had looked at timers a bit and could not work them out. Mainly because I was thinking that there would be a counter that counted down.

For 4.3.2 offsets - done slightly differently to your array method.

http://www.ownedcore.com/forums/worl...ml#post2186381 ([WoW][4.3.2.15211] Info Dump Thread)