Question about the Local Player GUID offset [5.4.2]

[Torpedoes]

Is it safe to get the local player GUID using a direct static pointer rather than going through the object manager (for convenience on my end)?
Looking through the offsets I found two candidates: 0xD0A3F0 and 0xD0CF68. Any of them good? Am I overlooking something?

So far I'm using:
Target GUID: 0xD60B38
Mouse Over GUID: 0xD60B20

[hardcpp]

ActivePlayer = 0xCAF7CC;

        public static UInt64 GetActivePlayerGuid()
        {
            uint l_ActivePlayerPtr = Process.Memory.ReadUInt((uint)Process.Memory.MainModule.BaseAddress + (uint)HardCPPWoWDumper.Game.Offsets.ActivePlayer);

            if (l_ActivePlayerPtr != 0)
                if (Context.Version == 542)
                    return Process.Memory.ReadUInt64(l_ActivePlayerPtr + 232);
                else
                    return Process.Memory.ReadUInt64(l_ActivePlayerPtr + 224);

            return 0;
        }

[Torpedoes]

Thank you, I ran across this offset as well. +rep

[hamburger12]

@Torpedoes... it seems you are using DWORD for guids. You have to use __int64 else there will be problems!

[Torpedoes]

@Torpedoes... it seems you are using DWORD for guids. You have to use __int64 else there will be problems!

Hey, hamburger12, I'm actually using uint64, hardcpp is using dwords (which is wrong). Thanks for pointing that out!

EDIT: Actually nevermind, everything is right, I'm just not paying attention...