Problem with offsets and pointers

[Neverhaven]

Hi,

I made a very basic fishing bot, to kinda, get started with WoW hacking, and it's working great on my computer, but once i throw it on my laptop, my gf's computer or her laptop, it doesn't work. I have no clue what the problem could be.
These are the offsets i use:

ClientConnection = [0x012705B0]
ObjectManagerOffset = [0x00002D94]
ChannelingObject = [0x0133D528]
MouseOverGUID = [0x0113D798]
FirstObjectOffset = [0x000000AC]
ObjectTypeOffset = [0x00000014]
ObjectGUIDOffset = [0x00000030]
ObjectBobberBobbingOffset = [0x000000BC]

Does any of those look wrong? I found the BobberBobbing and ChannelingObject offset/pointers myself, so it's likely they're causing some problems.

[FenixTX2]

What language are you coding in? At a faint gues i would say that you are coding on a x64 machine and your gf's computers are x86? If you're using Visual Studios then under the project settings change the platform type to x86 (it'll still work on x64, but will now support x86 machines too.

[Neverhaven]

C# using basic MS Visual Studio Express Edition. I checked, and both machines are x86. The bug it seems, is the check to see if the player is channeling fails. I'm going to install my dev tools on one of the laptops, and see if i can find the problem.

[Cypher]

What language are you coding in? At a faint gues i would say that you are coding on a x64 machine and your gf's computers are x86? If you're using Visual Studios then under the project settings change the platform type to x86 (it'll still work on x64, but will now support x86 machines too.

That makes no sense. The default platform type is 'Any CPU' and the JIT compiler compiles to whatever architecture you're running on.

The problem occurs when you're writing a cheat and running on an x64 machine, because the JIT compiler compiles to binary to x64 and you can't interact with an x86 target (WoW) properly.

So, if it is a config problem, then it would be the other way around. It would work on the x86 machine and not on the x64 machine.

[Jadd]

That makes no sense. The default platform type is 'Any CPU' and the JIT compiler compiles to whatever architecture you're running on.

The problem occurs when you're writing a cheat and running on an x64 machine, because the JIT compiler compiles to binary to x64 and you can't interact with an x86 target (WoW) properly.

So, if it is a config problem, then it would be the other way around. It would work on the x86 machine and not on the x64 machine.

Bam!

Filler.

[Cypher]

Bam!

Filler.

[ame=http://www.youtube.com/watch?v=Nr1fDOzLkAo]YouTube - Most annoying commercial ever: Easy-Off Bam[/ame]

[wraithZX]

Damn you Cypher. They keep putting that ad on when watching Fox Sports.
Ugh FAIL.

[flukes1]

It's CILLIT BANG you yank bastards, not "Easy-Off Bam"... mumble grumble...

[ame=http://www.youtube.com/watch?v=WGooQ8yYC0c]YouTube - Cillit bang techno remix[/ame]

[~OddBall~]

Aussies fool, Yanks can go die in a fire while talking about how awesome their country is

Ok not really, but no one has much of a likeness for them xD

[Cypher]

It's CILLIT BANG you yank bastards, not "Easy-Off Bam"... mumble grumble...

YouTube - Cillit bang techno remix

How dare you call me a yank, I'm an Australian thank you very much.

[snigelmannen]

Well i started looking into stuff and found this and i got some trouble updating the offsets, might be because i suck and usually fails when it comes to coding, is it possible for a newbie to get that program working just by finding and updating the offsets?

Otherwise point me in to the right direction and i can stop trolling here.

here are the offsets im using now.

        uint StaticClientConnection = 0x1139F80;
        uint ClientConnection = 0x012705B0;
        uint ObjectManagerOffset = 0x2C34;
        uint ObjectManager = 0;
        uint FirstObjectOffset = 0x000000AC;
        uint FirstObject = 0;
        uint LocalGuidOffset = 0xC0;

wrong or correct? tried every search function and i only know copy pasta that might be the issue