[WoW][Warden] Watched Address List - Including Length & Bytes!

[_Mike]

Well testing the speedhack one, and NOPing the offset you provided and no ban, waited an hour.

EDIT: Nope the offsets/length are correct. There checking just before, I guess this is for some other hack/to stop people detouring the hack.

Yes I can verify that they (or at least this one, only one I checked) are correct. Can easily be tested in a debugger.
WoW+0x188de0 is checked frequently.
WoW+0x188e0b was never scanned during the ~3h I had the debugger attached while playing.

Do doubt this speedhack offset will be in the next warden update; If not, it will be soon!

Blizzard must have known that offset was being used for speed hacks. It's almost like they don't want to catch too many people cheating

[-Ryuk-]

Updated for 4.0.6a

[jazerix]

If you're just reading an address, can warden detect it? (assuming the adress is on the list :P)

[Xelper]

If you're just reading an address, can warden detect it? (assuming the adress is on the list :P)

No, simply reading a value is not detected by Warden.

[-Ryuk-]

No, simply reading a value is not detected by Warden.

Correct, you cannot be banned for memory reading

[jazerix]

awesome thanks for the replies...

[Cypher]

Correct, you cannot be banned for memory reading

Assuming of course your bot is private.

(Sorry to nitpick, but there's enough confusion as it is. Eventually you get sick of getting asked the same stupid questions, so I try to be explicit as possible.)

[-Ryuk-]

Assuming of course your bot is private.

(Sorry to nitpick, but there's enough confusion as it is. Eventually you get sick of getting asked the same stupid questions, so I try to be explicit as possible.)

I understand :P xD

[MyWay86]

warden just got updated.

0x000045F0

[Nonowmana]

You can add 0x00004603 ^^

[KuRIoS]

I added it to our wiki... a page under Warden Patch 4.0.6a Offsets - MMOwned Wiki

[reggggg]

Wanted to see where these addresses are without going through them manually ... maybe someone else feels the same:

Executing function 'main'...
459590   Lua_SendChatMessage
45184e   sub_8517A0+AE
4596d8   Lua_SendChatMessage+148
92887    sub_492770+117
80c8ac   
1ba7f0   sub_5BA7F0
cbb9a    sub_4CBB10+8A
d530     start+C240
460d     sub_4045A0+6D
55b81e   CMovement__CreateMovementStatus:loc_95B81E
3a263e   FrameScript__Execute+1E
238a20   sub_638970+B0
1cd48d   CGUnit_C__sub_5CD400+8D
427274   sub_827260+14
91df0    ClientConnection__SendPacket
d7d21    NetClient__Login+1B1
12fa     
73bec8   
915b0    NetClient__HandleRealmData
15df40   sub_55DF40
188db0   CMovement__MoveUnit
37411d   Lua_GetCharacterInfo+5D
42c702   CGGameUI__CheckPermissions+12
18989b   sub_589800+9B
6dfd58   
45f2     sub_4045A0+52
3a1824   sub_7A1550+2D4
90a30    NetClient__HandleData
2882b8   sub_6882B0+8
d57e2    sub_4D57D0+12
15e922   sub_55E610+312
17cf30   sub_57CF30
180ed6   sub_580EC0+16
43f521   sub_83F290+291
213843   CMovement__sub_613770+D3
455f80   ChatFrame__AddMessage
56210d   CMovement__Swimming_FallCalc:loc_96210D
45646d   ChatFrame__AddMessage+4ED
649190   Checksum
3a4dde   FrameScript__BroadcastEvent+6E
644030   sub_A44030
365d4    FrameScript__PushString+44
6e5884   
55e731   CMovement__sub_95E700+31
45f0     sub_4045A0+50
4603     sub_4045A0+63

#include <idc.idc>

static LocateFunc(dwAddr)
{
	auto szFunc;
	szFunc = GetFuncOffset(dwAddr + 0x400000);
	Message("%-8x %s\n", dwAddr, szFunc);
}

static main()
{
	LocateFunc(0x459590);
	LocateFunc(0x45184E);
	LocateFunc(0x4596D8);
	LocateFunc(0x92887);
	LocateFunc(0x80C8AC);
	LocateFunc(0x1BA7F0);
	LocateFunc(0xCBB9A);
	LocateFunc(0xD530);
	LocateFunc(0x460D);
	LocateFunc(0x55B81E);
	LocateFunc(0x3A263E);
	LocateFunc(0x238A20);
	LocateFunc(0x1CD48D);
	LocateFunc(0x427274);
	LocateFunc(0x91DF0);
	LocateFunc(0xD7D21);
	LocateFunc(0x12FA);
	LocateFunc(0x73BEC8);
	LocateFunc(0x915B0);
	LocateFunc(0x15DF40);
	LocateFunc(0x188DB0);
	LocateFunc(0x37411D);
	LocateFunc(0x42C702);
	LocateFunc(0x18989B);
	LocateFunc(0x6DFD58);
	LocateFunc(0x45F2);
	LocateFunc(0x3A1824);
	LocateFunc(0x90A30);
	LocateFunc(0x2882B8);
	LocateFunc(0xD57E2);
	LocateFunc(0x15E922);
	LocateFunc(0x17CF30);
	LocateFunc(0x180ED6);
	LocateFunc(0x43F521);
	LocateFunc(0x213843);
	LocateFunc(0x455F80);
	LocateFunc(0x56210D);
	LocateFunc(0x45646D);
	LocateFunc(0x649190);
	LocateFunc(0x3A4DDE);
	LocateFunc(0x644030);
	LocateFunc(0x365D4);
	LocateFunc(0x6E5884);
	LocateFunc(0x55E731);
	LocateFunc(0x000045F0);
	LocateFunc(0x00004603);
	return 0;
}

[Sebbe123]

Assuming of course your bot is private.

(Sorry to nitpick, but there's enough confusion as it is. Eventually you get sick of getting asked the same stupid questions, so I try to be explicit as possible.)

May I ask (sorry if it's a stupid question) what makes public bots using only memory reading detectable?

[Cypher]

May I ask (sorry if it's a stupid question) what makes public bots using only memory reading detectable?

It's not the memory reading in itself that's detectable, it's everything else. No such thing as an 'undetectable' public bot.

[-Ryuk-]

Sorry guys, have been moving house so my scanner has been offline :P

Thanks KuRIos for adding this to the Wiki, Ill make a new output function for that, with a nice layout.

Many thanks to MyWay86 & Nonowmana for making people aware of this update.

@reggggg, I like your idea, but I don't really need to know what each address is, I just make sure I don't use them.

@Sebbe123, Cypher is right

Also, seting up my scanner right now, to get the latest updated list.

EDIT:Scanning now, going bed, will add tomorrow