Offset Patterns?

[wowsc4p3]

Hello, This is regarding the offset finder.
Would somebody mind making the pattern of this address(es) for me?
3.3.5: 0x005191D2
3.3.3: 0x007199B2
3.3.2: 0x004BE422
Also if possible find the 4.0.6 one? (Not necessary)
OH: Forgot to say, these are all the same address but different versions.
Thanks.
IMPORTANT: READ!
Results have been given, WARNING: Use on live servers will cause you to be owned by warden. Use of any character moving commands will lead to instant dc, Luckily on trial! Thanks for all the help guys.
Oprime:
4.0.6a: 0x82C702 (WON'T WORK, FIND BY PATTERN BELOW)
pattern: 74 ? 83 F9 ? 77

[Thunderofnl]

Could you please tell which offset this is? ¬¬

[wowsc4p3]

It is the LUA Unprotected one.

[Jadd]

Be careful of Warden with unprotecting Lua, Blizzard really hate it (look at LuaNinja for example).

If you get the updated addresses, have a look here before you go off using them: http://www.mmowned.com/forums/world-...gth-bytes.html

[wowsc4p3]

I guessed.

[Azzie2k8]

shouldnt the 4.0.6 pattern work for the previous versions as well or did something change in that function ?

Btw I might try if you give me the 4.0.6 address

[wowsc4p3]

The pattern I could find myself if I knew the 4.0.6 address

[oprime]

4.0.6a: 0x82C702

pattern: 74 ? 83 F9 ? 77

edit: obviously no need for the ? at the end..

[-Ryuk-]

4.0.6a: 0x82C702

pattern: 74 ? 83 F9 ? 77 ?

This isnt rebased....

Using your pattern I found

0x42C702

This address is correct. (Just tested)

Change the first byte from 0x72 to 0x71 then type

/run CastSpellByName("Attack");

In the chat box and press enter, It will attempt to cast the spell.

However you still get the

"A macro script has been blocked from an action only available to the Blizzard UI"

But this should be ok

WARNING: THIS IS DETECTED!

--------------------------------
Offset: 0x42C702
Length: 7
Bytes: 116 101 131 249 24 119 96

[oprime]

This isnt rebased....

as the op didnt use rebased offsets, i assumed it is correct to post the new version offsets in the same manner

Change the first byte from 0x72 to 0x71 then type

you mean from 0x74?

[-Ryuk-]

as the op didnt use rebased offsets, i assumed it is correct to post the new version offsets in the same manner


you mean from 0x74?

well 0x71 works for me

[oprime]

well 0x71 works for me

yes , but i'm talking about the original byte is 0x74 not 0x72 as you have mentioned above (quoted it in my post before)

btw, yes 0x71 is working. however in my opinion the nice way is to change it to an unconditional jump (jmp 0xEB)

[wowsc4p3]

I didn't know they weren't rebased. However, Why is neither of them working?

[oprime]

its working for me, and reading Ryuk posts its working for him too. i tried it on a trial account, and jumping/moving/etc. worked perfectly. did not get any disconnect was online for atleast an hour.
try it the most basic way, use a process memory editor and search for the pattern, make sure you write to the correct offset.

btw, dont yell warden because of a simple disconnect

[-Ryuk-]

WARNING: THIS IS DETECTED!

--------------------------------
Offset: 0x42C702
Length: 7
Bytes: 116 101 131 249 24 119 96