View Full Version : *** New Offset 04.12.02 ***
speedphreak
12-04-2002, 05:35 AM
eqgame.exe MD5: A7BEB886E0155AA42D4ECC88EDFB8AEB
new key offset: 0x78BCB8 (formatted as 0x0078bcb8 for keyring)
Has a cursory glance over for anti-sniffing changes and can't see anything obvious, but no promises!
No other DLL/EXE was updated with the patch
LordCrush
12-04-2002, 07:17 AM
Ty :D
Fletch
12-04-2002, 07:17 AM
Will update when I get home.
Molly
12-04-2002, 10:36 AM
i updated the keyring and the stealth code with this new offset, but it is not decoding for me. anyone else having any luck?
edited for spelling
baelang
12-04-2002, 11:11 AM
Originally posted by Molly
i updated the keyrind and the stealth code with this new offset, but it is not decoding for me. anyone else having any luck?
for keyring the offset needs to be specified as:
0x0078bcb8
note the leading zeros and lower case letters.
EDIT: I have logged on and can verify that 0x0078bcb8 and keyring works perfectly. I edited the config file. there may still be problems when using the command line to specify the offset.
Molly
12-04-2002, 11:46 AM
yup, thats how i have it set. it worked yesterday with the old offset, just not working today :(
speedphreak
12-04-2002, 11:54 AM
Is the stealth sniffer working with this offset? I don't have access to try it out, but I've checked exe again and the offset I gave certainly appears to be where the key is.
Wondering if something else has changed....
Jel321
12-04-2002, 11:58 AM
Maggot boys sniffer is working with this offset.
baelang
12-04-2002, 12:06 PM
It looks like there is a bug with command line options with keyring. if everything is in the config file, it works properly. if you specify more than one option (that takes and argument) on the command line, it pukes. i will work on fixing that.
Fletch
12-04-2002, 12:12 PM
Originally posted by speedphreak
Is the stealth sniffer working with this offset? I don't have access to try it out, but I've checked exe again and the offset I gave certainly appears to be where the key is.
Wondering if something else has changed....
Checked it at home and it is working just fine.
paulbc
12-04-2002, 12:23 PM
just wondering (im still busy RTFM on this as i cant get it to work)
but just wondering all the same if there isnt some way to sniff out the key on one location and publish it to a website or location the program can pool up for..
this would reduce the risk of getting banned for having sniffers on the same computer and make the program just a tad more userfriendly..
or am i just nucking futz
Molly
12-04-2002, 12:25 PM
i believe the memory address changes from patch to patch but the session key is unique to the zone YOU are in. publishing someone elses session key does you no good.
im running keyring, all options in config, no command line variables, still no luck.
Molly
12-04-2002, 12:27 PM
well, ill be damned, just zoned and its working great :P
Jel321
12-04-2002, 12:28 PM
I've seen a similar problem Molly. Normally it will fire up right away but once in a while i need to zone once to get it to kick in.
flobee
12-04-2002, 12:30 PM
The key that is generated is not static for any zone in particular. It is generated at random and will be different if you revisit that zone. Unless you get unimaginablly lucky.
seqmage
12-04-2002, 11:10 PM
Hi, I am using uncle ben's code with the config file. Adding the new offset and its running just fine.
Powered by vBulletin® Version 4.1.9 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.