[Example][C#] WoW Process Loader

[wowhackz0r]

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.

new version closing the processes.

However, i am pretty sure i am right in opening it twice like i do, i am not just reading the handle by opening it, you have to call that function for blackmagic to know which process to open.

if i didn't recall the function, it would just read from the last process it opened, not the specific one chosen

[Apoc]

new version closing the processes.

However, i am pretty sure i am right in opening it twice like i do, i am not just reading the handle by opening it, you have to call that function for blackmagic to know which process to open.

if i didn't recall the function, it would just read from the last process it opened, not the specific one chosen

Last I checked; BM allowed you to pass a handle to it, to use instead of one it registers internally.

I may be wrong, if so, please do show me the code. (As I said; I don't use Shynd's lib, as I'm not OOP)

[wowhackz0r]

Last I checked; BM allowed you to pass a handle to it, to use instead of one it registers internally.

I may be wrong, if so, please do show me the code. (As I said; I don't use Shynd's lib, as I'm not OOP)

i do not have a lot of experience with blackmagic, as all i am using it for is to open the process and read the memory, nothing to complex.

if there is a way to pass a handle to it, i did not see it, as that would be easier, as using the process selector with the keyboard input i am using with
would be made much easier as that used the windows handle not the process name

i will look and see if there is a way to pass a handle to BM

[Apoc]

I know BM's static classes (SThread, SProcess, etc) require handles to be passed to certain functions. There's your place to do so. I guess I'll have to grab BM again and see what it's actually doing nowadays.

[-Ryuk-]

Hey when I run this I get the error "Not all privileges or groups referenced are assigned to the caller" on this line: "WoW.OpenProcessAndThread(processes[i]);"

How would i fix this?

[mnbvc]

here is my way to do this:

using my connect class i can access everything i need in a specific wow pid

    public class Connect
    {
        public Memory mem;
        public ObjectManager obj;
        public SendKey key;

        private int pid;
        private IntPtr hwnd;
        private string name;

        public Connect(int process)
        {
            this.hwnd = SWindow.FindWindowByProcessId(process);

            mem = new Memory(process);
            obj = new ObjectManager(mem);
            key = new SendKey(this.hwnd);

            this.pid = process;
            this.name = obj.info.LocalName;
        }

        public int PID
        {
            get { return this.pid; }
        }

        public IntPtr HWND
        {
            get { return this.hwnd; }
        }

        public string NAME
        {
            get { return this.name; }
        }
    }

i my frame class i just create a list of these connect classes and set them as the datagridview datasource, then they will be displayed:

private List<Connect> ptr = new List<Connect>();



            int[] pids = SProcess.GetProcessesFromClassname("GxWindowClassD3d");
            foreach (int pid in pids)
            {
                ptr.Add(new Connect(pid));
            }
            this.dataGridView_Process.DataSource = this.ptr;
            this.dataGridView_Process.Rows[0].Selected = true;

then i can select a line and call the databounditem (my connect class) like this:
((Connect)this.dataGridView_Process.SelectedRows[0].DataBoundItem).obj.LocalPlayer.TargetGuid
which would get the info from the selected wow, in this example the localplayer target guid

[WannaBeProgrammer]

Hey when I run this I get the error "Not all privileges or groups referenced are assigned to the caller" on this line: "WoW.OpenProcessAndThread(processes[i]);"

How would i fix this?

If ur on vista/Win7 you should run C# as admin or run the .exe as admin, else i dunno.

[lanman92]

Do you have debugging privileges? System.Diagnostics.Process.EnterDebugMode() == easy.

[vadi]

Hmm, can't download (

[_Mike]

Do you have debugging privileges? System.Diagnostics.Process.EnterDebugMode() == easy.

Why does everyone keep suggesting this? And why does everyone include it in their libraries/binaries and therefore requiring them to be run as admin?
Stop blindly repeating bad advice. Wow is not a system process.

[jayswag]

Good work

[amadmonk]

Why does everyone keep suggesting this? And why does everyone include it in their libraries/binaries and therefore requiring them to be run as admin?
Stop blindly repeating bad advice. Wow is not a system process.

The last time I checked, Blizzard was setting restrictive ACL's on the wow client process, which -- if it's still true -- DOES require SeDebugPrivilege to overcome. Did they remove the ACL's?

[Cypher]

The last time I checked, Blizzard was setting restrictive ACL's on the wow client process, which -- if it's still true -- DOES require SeDebugPrivilege to overcome. Did they remove the ACL's?

Whilst that did indeed used to be the case, it seems to no longer be necessary. I can attach HadesMem to WoW and inject a DLL without elevating HadesMem to admin, and without enabling the debug privilege.

Tested on v4.0.6.13923.

P.S. Afaik, you technically never REALLY needed the debug privilege, you just needed to correctly set your own ACLs, however it's obviously easier to just enable everything rather than fiddle around.

[amadmonk]

Well, yeah. But since I'm usually using .Net, it's far easier (as you say) to do Process.EnterDebugMode than to deal with Microsoft's typical opaque and obtuse ACL API.

And since most of the ACL's you needed required admin privileges anyway (or at least "Power User"), it still makes perfect sense that people are just conditioned to enable SeDebug by default. It's just so much easier to set it and forget it.

[FinnX]

Cant download it?