[Example][C#] WoW Process Loader

[wowhackz0r]

I created this for the bot I'm working on and thought it could be useful to others. It's tested and works, source and application are included. I would love critique on it, but if your just going to say it sucks don't post.



What does it do?
It provides a method you can implement into your bot to allow you to easily select which process of wow you would like to run a specific instance of your bot application with for easier setup of a botting environment with multiple instances of WoW running.
Please post feedback!!!

[Mirror]

Wow, this actually will be helpful, thank you. I'll be reading the source code if you don't mind, (no copying and pasting just looking too see how and why you did things.)

+6 rep.

[Apoc]

Don't get me wrong; I have nothing against people trying to learn. But this doesn't do anything your post says it does...

            int click = comboBox1.SelectedIndex;

                    WoW.OpenProcessAndThread(processes[click]);
                    uint playerBase = WoW.ReadUInt(WoW.ReadUInt(WoW.ReadUInt(0x00CF7C00) + 0x34) + 0x24);
                    uint mana = WoW.ReadUInt(WoW.ReadUInt(playerBase + 0x8) + (0x18 * 4));
                    uint health = WoW.ReadUInt(WoW.ReadUInt(playerBase + 0x8) + (0x17 * 4));
                    float x = WoW.ReadFloat(playerBase + 0x798);
                    float y = WoW.ReadFloat(playerBase + 0x79C);
                    float z = WoW.ReadFloat(playerBase + 0x7A0);

                    label10.Text = WoW.ReadASCIIString(0x00C923F8, 12); // Player name
                    label12.Text = health.ToString(); // Health
                    label13.Text = mana.ToString(); // Mana
                    label14.Text = x.ToString(); // X
                    label15.Text = y.ToString(); // Y
                    label16.Text = z.ToString(); // Z

That's the bulk of the code. (The rest is just setting debug privs and grabbing a proc handle on the WoW procs via BlackMagic)

Besides printing some basic info to the WinForms app, what is this supposed to be doing that hasn't been documented 1000x over?

Edit; as for a critique; you're never closing the handles to the processes you open. (IIRC: BlackMagic has a CloseHandle func somewhere. Don't take my word for it, I don't use the lib.) And you're also opening the handles twice. Once in the button1 handler, and again in the button2 handler. (I think it's button2 at least)

[wowhackz0r]

Wow, this actually will be helpful, thank you. I'll be reading the source code if you don't mind, (no copying and pasting just looking too see how and why you did things.)

+6 rep.

go right ahead, C&P if you really want to, i posted it so other people could learn, as long as you understand the code, C&P can lead to learning

[wowhackz0r]

Besides printing some basic info to the WinForms app, what is this supposed to be doing that hasn't been documented 1000x over?

Well I have read more than one person posting topics on the process of creating a process selector, and modifying this to fit your project would be that...

As for it not doing, it does everything I stated.

[Mirror]

Don't get me wrong; I have nothing against people trying to learn. But this doesn't do anything your post says it does...

            int click = comboBox1.SelectedIndex;

                    WoW.OpenProcessAndThread(processes[click]);
                    uint playerBase = WoW.ReadUInt(WoW.ReadUInt(WoW.ReadUInt(0x00CF7C00) + 0x34) + 0x24);
                    uint mana = WoW.ReadUInt(WoW.ReadUInt(playerBase + 0x8) + (0x18 * 4));
                    uint health = WoW.ReadUInt(WoW.ReadUInt(playerBase + 0x8) + (0x17 * 4));
                    float x = WoW.ReadFloat(playerBase + 0x798);
                    float y = WoW.ReadFloat(playerBase + 0x79C);
                    float z = WoW.ReadFloat(playerBase + 0x7A0);

                    label10.Text = WoW.ReadASCIIString(0x00C923F8, 12); // Player name
                    label12.Text = health.ToString(); // Health
                    label13.Text = mana.ToString(); // Mana
                    label14.Text = x.ToString(); // X
                    label15.Text = y.ToString(); // Y
                    label16.Text = z.ToString(); // Z

That's the bulk of the code. (The rest is just setting debug privs and grabbing a proc handle on the WoW procs via BlackMagic)

Besides printing some basic info to the WinForms app, what is this supposed to be doing that hasn't been documented 1000x over?

Edit; as for a critique; you're never closing the handles to the processes you open. (IIRC: BlackMagic has a CloseHandle func somewhere. Don't take my word for it, I don't use the lib.) And you're also opening the handles twice. Once in the button1 handler, and again in the button2 handler. (I think it's button2 at least)

So wait... whats wrong with it? English please?

[Apoc]

It allows you to run more than 1 wow instance and select which character you would like the bot to run on.

What bot? This doesn't automate anything. Thus; doesn't fulfill the definition of a bot. You're simply displaying basic information from out of process...

[Apoc]

So wait... whats wrong with it? English please?

I didn't say there was anything majorly wrong with it (other than possibly leaking handles like crazy). It's most definitely not a bot. Just a simple information display. If that's all he was aiming for; he should state so. A bot requires some form of automation to be done. This doesn't do anything automated.

[wowhackz0r]

What bot? This doesn't automate anything. Thus; doesn't fulfill the definition of a bot. You're simply displaying basic information from out of process...

I never said this WAS a bot, i said it could be modified for the CREATION of a bot, nowhere did I say this was a complete bot of any fashion.

The output on the window was simply to display that yes, indeed that specific instance of WoW was being loaded, not to try and claim anything botlike.

EDIT: I reread my first post, I did not clearly state well enough what this does, however I do believe the included pic provides more than enough description of it, editing my first post now.

[Apoc]

I repeat.

What does it do?
It allows you to run more than 1 wow instance and select which character you would like the bot to run on.

I'm fairly sure that says 'sic... like the BOT to run on.'

If that's not what you meant; so be it. However; be more clear in your posts if you want to avoid confusion.

My point about leaking handles still stands however.

[Multitask]

I repeat.



I'm fairly sure that says 'sic... like the BOT to run on.'

If that's not what you meant; so be it. However; be more clear in your posts if you want to avoid confusion.

My point about leaking handles still stands however.

i would have to agree with the OP here. earlier he made reference that this was something to be implemented into a bot. so his discription is correct. if you add this to your bot, it will allow you to select the wow process.

[Apoc]

Well; he edited the first post. It's a bit clearer now (still confusing as hell with that insane run-on sentence).

Either way; the leaking handles issue still remains. Close your handles when you're done with them. (And especially; don't open a handle twice for no apparent reason.)

[Multitask]

Well; he edited the first post. It's a bit clearer now (still confusing as hell with that insane run-on sentence).

Either way; the leaking handles issue still remains. Close your handles when you're done with them. (And especially; don't open a handle twice for no apparent reason.)

ah, i didnt mean disrespect or anything, just from what i read a few min ago it seemed that his explanation was valid

[wowhackz0r]

Well; he edited the first post. It's a bit clearer now (still confusing as hell with that insane run-on sentence).

Either way; the leaking handles issue still remains. Close your handles when you're done with them. (And especially; don't open a handle twice for no apparent reason.)

Yes, i need to close the handles.

However, if you look at the code a little closer, there is a very apparent reason i open it twice.
The second time it opens the specific process you select, the first time it cycles through all of them to retrieve the character name, second time it chooses the process you select.

[Apoc]

Yes, i need to close the handles.

However, if you look at the code a little closer, there is a very apparent reason i open it twice.
The second time it opens the specific process you select, the first time it cycles through all of them to retrieve the character name, second time it chooses the process you select.

Doesn't change the fact that you open it twice. (You read the name in both button handlers)

Once you open a handle; store it somewhere [eg; an array] and re-use it later. There's no reason to open it again. You're just leaving the previous one open (thus, leaked), and opening a new one every time you hit button2 or whatever button it was.

Trust me; I'm being nice as far as critiquing your code goes. Ask kynox. I can be brutal.