LAZYBOT support thread, Q&A, requests and updates

[dragonbane24]

Does anyone have any clue as to why when update Offsets, Recompile DLL, and move to the program folder that I can no longer get the exe file to load. I'm missing something that I have not been able to learn from the information contained in these forums.

Does it give you any errors when recompiling? Make sure you're building for .NET 3.5 and not 4.0 for both the LazyLib and LazyEvo. Also make sure you're not using a 64-bit WoW client. The latest patch automatically updated everyone that has a 64-bit OS to use the 64-bit client by default.

Not sure if we should start a new forum thread for this or not. I don't want to hijack someone else's support thread.

[MyNewName]

No. It does not. I got it to work fine. I am in game. Now working my way through the descriptors file. Will let you know when i have it up and running.

[gauderio]

someone is able to run the bot? I run wow.exe through the bot, but it does not identify the process ... what should I do to make the bot identifies the process wow.exe he even opened?

[Melba459]

Ye, in the left of the bot choose behavior engine, not custom class. And delete custom class folder from LB.

[MyNewName]

Dragon, How is your progress? I can get the program to attach, but still cant find the Playername, I have tried to rebase it just incase, but no good. I did go ahead and update all the descriptors so the only thing i can see holding back the program from being released again is... The playername Offset. This is the one I am using now. 0xDC92D8

[tylen]

This is the one I am using now. 0xDC92D8

Thins is one i found in 5.0.4.16016 dump thread when tried to edit pointers.cs , didnt work for me neither, bot attaches to process only cant start coz of "please enter the world"

[jumperu]

Does it give you any errors when recompiling? Make sure you're building for .NET 3.5 and not 4.0 for both the LazyLib and LazyEvo. Also make sure you're not using a 64-bit WoW client. The latest patch automatically updated everyone that has a 64-bit OS to use the 64-bit client by default.

Not sure if we should start a new forum thread for this or not. I don't want to hijack someone else's support thread.

Please feel free to post here as much as you want, that goes for anyone else working on the bot. We all have the same objective, to get the bot working.
I'm sorry i can't be of more help, it was easy in the past when i just had to change the offsets in pointers.cs and everything was working great, but now so much has changed.

A big thank you to anyone working on the bot, trying to make it work so all of us can enjoy some free botting.

[lazyang]

uiii Jumperu is still alive <3

[MyNewName]

Thins is one i found in 5.0.4.16016 dump thread when tried to edit pointers.cs , didnt work for me neither, bot attaches to process only cant start coz of "please enter the world"

Ok. Is there a way to derive a way to find player name by using a bot that is working. PQR finds the playername very easily and attaches on login? Any ideas on this?

[MyNewName]

Thins is one i found in 5.0.4.16016 dump thread when tried to edit pointers.cs , didnt work for me neither, bot attaches to process only cant start coz of "please enter the world"

I do believe i found the area of code that needs to be changed. If you have any luck let me know... This is located in Under the manager tab in the ObjectManager.cs file..

/// <summary>
/// Gets a value indicating whether [in game].
/// </summary>
/// <value><c>true</c> if [in game]; otherwise, <c>false</c>.</value>
public static bool InGame
{
get
{
try
{
if (ForceIngame)
{
return true;
}
return Memory.ReadRelative<byte>((uint)PublicPointers.InGame.InGame) == 1;
//1 ingame 0 not ingame
}
catch
{
return false;
}
}
}

[MyNewName]

#region ProcessHandle

public static bool OpenProcess(int processId)
{
// ReSharper disable AssignNullToNotNullAttribute
var principal = new WindowsPrincipal(WindowsIdentity.GetCurrent());
// ReSharper restore AssignNullToNotNullAttribute
if (principal.IsInRole(WindowsBuiltInRole.Administrator))
Process.EnterDebugMode();

ProcessObject = Process.GetProcessById(processId);
ProcessHandle = OpenProcess(0x000F0000 | 0x00100000 | 0xFFF, false, processId);
if (ProcessHandle != IntPtr.Zero)
return true;
return false;
}

public static void CloseProcess()
{
CloseHandle(ProcessHandle);
Process.LeaveDebugMode();
}
another possible variable. I am done for the day, might grind on it later. Good luck everyone

[dragonbane24]

I didn't have to change anything in the OpenProcess handles to get my version to see the player name. Here's a snippet from my pointers.cs file.

       #region Globals enum

        /// <summary>
        ///   5.0.x
        /// </summary>
        public enum Globals
        {
            //PlayerName = 0x9BE820,   // 4.3.4
            //PlayerName = 0xF2AAB8,   // 5.0.4 (15913)
            //PlayerName = 0xF2EDA0,   // 5.0.4 (15929)  (0x42E8 diff)
            //PlayerName = 0xF37F10,     // 5.0.4 (15952) (0x9170 diff)
            PlayerName = 0xDC92D8,     // 5.0.4 (16016) (-0x16EC38 diff)
        }

        #endregion

#region InGame enum

        /// <summary>
        ///   5.0.x
        /// </summary>
        public enum InGame
        {
            //InGame = 0xAD7426, //4.3.4
            //InGame = 0xDCCF5E, // 5.0.4 (15913) 
            //InGame = 0xDD11EE, // 5.0.4 (15929) (0x4290 diff)
            //InGame = 0xDDA506, // 5.0.4 (15952) (0x9318 diff)
            InGame = 0xC6B8DE, // 5.0.4 (16016) (-0x16EC28 diff)
        }

#endregion
    }

I did have to change the Descriptors file partly here:

#if MISTS
        public enum eObjectFields
        {
            OBJECT_FIELD_GUID = 0x0,
            OBJECT_FIELD_DATA = 0x8,
            OBJECT_FIELD_TYPE = 0x10,
            OBJECT_FIELD_ENTRY = 0x14,
            OBJECT_FIELD_SCALE_X = 0x18,
            OBJECT_FIELD_PADDING = 0x1C,
        };
#else
        public enum eObjectFields
        {
            OBJECT_FIELD_GUID = 0x0,
            OBJECT_FIELD_DATA = 0x8,
            OBJECT_FIELD_TYPE = 0x14,
            OBJECT_FIELD_ENTRY = 0x14,
            OBJECT_FIELD_SCALE_X = 0x18,
            OBJECT_FIELD_PADDING = 0x1C,
        };
#endif

And the PObject here: (Otherwise it was reading the wrong offset for Object data.)

        /// <summary>
        ///   Object's Type.
        /// </summary>
        public int Type
        {
//#if MISTS
//            get { return Memory.Read<int>(BaseAddress + 0x10); }
//#else
            get { return Memory.Read<int>(BaseAddress + (uint) Descriptors.eObjectFields.OBJECT_FIELD_TYPE); }
//#endif

        }

[xhavokxx]

hmm, nice. well im way behind if urs works can we have a copy to test?

[dragonbane24]

I do not believe I have the rep to attach files here. But let me share a few changes I made.

I've probably made 100's of changes to LazyBot since I got the source. So unless I post the entire source, it may not compile properly for you. But these files should get several of you up and going. And I won't say that these are error-free, but they've been able to run dungeons, gather herbs/ore, etc. I'm still working out the kinks with all of the 11 different classes and combat rotations with the new energy types they have (Chi, Demonic Fury, etc.).

Note that I used #define MISTS to allow me to compile a bot to run on Beta vs. live last month. Now I have MISTS defined in all build configs since the structures between live and beta are nearly the same. (But the pointers are different.)

Pointers.cs : Paste2 - Viewing Paste 2194567
Constants.cs : Paste2 - Viewing Paste 2194581
Descriptors.cs : Paste2 - Viewing Paste 2194593

Also note that I went through the Descriptors file and commented out any fields that weren't being used. So do not un-comment and use them unless you fix 'em.

If this helps you, I could use the rep. Many thanks to those that have been posting offsets in the memory threads.
BTW - Paste2 is running really slow for me.

[lazyang]

do you think you will share you work if its updated for the latest patch? i really miss lb but can't help, no idea of programming :/
atm i try some other bots but can't find one who works smooth like lb.