Offsets: Nov 9th patch

Code:

---

[File Info]
Patchdate=11/8/2012

[Port]
port=5555

[Memory Offsets]
ZoneAddr=0xd4dcb4
SpawnHeaderAddr=0xdd20e8
CharInfo=0xd40740
TargetAddr=0xd40758
ItemsAddr=0xd3d2a8
WorldAddr=0xd40710


[WorldInfo Offsets]
WorldHourOffset=4
WorldMinuteOffset=5
WorldDayOffset=6
WorldMonthOffset=7
WorldYearOffset=8

[SpawnInfo Offsets]
NextOffset=0x4
PrevOffset=0x8
LastnameOffset=0x38
XOffset=0x64
YOffset=0x68
ZOffset=0x6c
SpeedOffset=0x7c
HeadingOffset=0x80
NameOffset=0xa4
TypeOffset=0x125
SpawnIDOffset=0x148
OwnerIDOffset=0x1c8
HideOffset=0x27c
LevelOffset=0x2a9
RaceOffset=0xea0
ClassOffset=0xea4
PrimaryOffset=0xfa8
OffhandOffset=0xfbc


[GroundItem Offsets]
PrevOffset=0x00
NextOffset=0x04
IdOffset=0x08
DropIdOffset=0x0c
XOffset=0x70
YOffset=0x74
ZOffset=0x78
NameOffset=0x1c

---

Tested and working.

Awesome. Thanks for the updated offsets.

Razzle

Thank you iluvseq.

Can't find any info on it. Must have been an emergency patch?

Hey guys. I thank you for trying but I am afraid these do not work for me :( Are these 100% good for you all? What can I be doing wrong if they do not work for me? o.O

Have you upgraded to version 2.2.8 yet? It was released to address issues after last weeks 1st patch on the 7th. I don't think older versions currently run on Live.

Removed isntalled and updated offsets still only the First zone map loads and nothing else. Doesn't load any other maps other than the initial map loaded shows no spawns does not track player or anything/anyone inside zone/Shows nothing in the zone only shows litterally the Map ouitlines, and never refreshes when zoning to a new zone.

Windows 7 64b

I just spent some time playing around with it since I had never tried zoning since the last update & I am not able to reproduce the problem. Working fine for me.

I've got the Newest Server, Newest Client and Newest Offsets yet still nothing but static map with nothing on it.

ZoneAddr Matches.
SpawnHeaderAddr Offset Not Identified.
CharInfo Offset Not Identified.
ItemsAddr Matches.
TargetAddr Offset Not Identified.
WorldAddr Offset Not Identified.
[Memory Offsets]
ZoneAddr=0xd4dcb4
SpawnHeaderAddr=0x0
CharInfo=0x0
ItemsAddr=0xd3d2a8
TargetAddr=0x0
WorldAddr=0x0

happens everytime i've loaded it for some reason

Quote:

---

Originally Posted by Phantom_Skie

ZoneAddr Matches.
SpawnHeaderAddr Offset Not Identified.
CharInfo Offset Not Identified.
ItemsAddr Matches.
TargetAddr Offset Not Identified.
WorldAddr Offset Not Identified.
[Memory Offsets]
ZoneAddr=0xd4dcb4
SpawnHeaderAddr=0x0
CharInfo=0x0
ItemsAddr=0xd3d2a8
TargetAddr=0x0
WorldAddr=0x0

---

What is this the output of? The offset finder? It isn't working right now...

Looks like the offset finder output. Need to stop using that for now & manually change the offsets listed in the 1st post above (copy them & overwrite the same section in the myseqserver.ini file). There is an Edit Offsets button in the main server window to help you manually change them. The offset finder fix is waiting for the next release.

It was originally from the offset finder which i then edited to the offsets above, when i shut down for the night and came back the next day the offsets were back to the finder settings even without running them.
I "think" i have it fixed now but for some reason the offsxets kept getting re-writen over by the wrong ones.

Btw anyone notice that PoTranq crashes the Client when zoning into it?

Quote:

---

Originally Posted by Phantom_Skie

It was originally from the offset finder which i then edited to the offsets above, when i shut down for the night and came back the next day the offsets were back to the finder settings even without running them.
I "think" i have it fixed now but for some reason the offsxets kept getting re-writen over by the wrong ones.

Btw anyone notice that PoTranq crashes the Client when zoning into it?

---

Offsets can not magically over-write. It takes positive user action to change offsets, unless you have some left over gremlins from Halloween hiding in your computer.

I tested zoning to PoTranq and it does not crash me.

The offset finder you were running was only finding 2 offsets. So if you did have it write out values, it would not have written the 0x0's. The two it was finding were correct. You may be running the offset finder, pointing to an eqgame.exe, which is not the current one on live. Maybe one in a different folder, that was not getting patched.

Not really sure exactly what you are doing.

Were you trying to run this on Beta? The secondary offsets are not up to date on Beta, and it will not work.

Razzle

Not sure about the Offsets to be honest and no it was on live, not test/beta.

The way i run it is on 2 machines Server on 1 machine and the client on a network connected machine. The Client often crashes on entering PoTranq.
I went there with 2.2.9.0 today and again PoTranq crashes, Both Server/Clients are the newest ones.
The Old client i rarely had issues with PoTranq crashing just the newer clients are doing it for some reason.
The Crash is a 100% freeze up on the machine where it requires a forced shutdown.

Quote:

---

Originally Posted by Phantom_Skie

The Old client i rarely had issues with PoTranq crashing just the newer clients are doing it for some reason.
The Crash is a 100% freeze up on the machine where it requires a forced shutdown.

---

Very odd. Could be the map being used. Could be a stray mob way out of range, causing weird stuff to be sent. I had put checks in for this before, but that doesn't mean they are working now. Which server is this happening on?

If that is the only zone you have seen that problem in, I would definitely test the map file it is trying to use for PoTranq. Just renaming the map file it is trying to use before zoning in, or connecting the MySEQ client should be enough as it runs fine without maps.

Just posting this in case others have an issue. After Windows patching/rebooting on Nov-15, for some reason, was having trouble using MySEQ 2.2.8.

So I downloaded 2.2.9 on both client and server, used default offsets etc. and had trouble... but noticed now the Offset Finder is working as before (I knew it was being worked upon, but I failed to read that 2.2.9 repaired it). Had to use the Offset Finder, it did find new offsets for me, updated the .ini file (was that button always there? I had been doing it my hand) and tasty skittles returned.

Again, not sure if this was just my wacky issue, or someone else experienced it, but if it helps even one person it was worth posting.

Level 1 Moss Snake MySEQ'er

Does sound odd. Did you notice what patch date it listed for the offsets that did not appear to be working? 2.2.9 worked fine for me and I haven't had to change anything.

My guess is they are updating while the server is running. That would explain the odd behavior.

Razzle

Quote:

---

Originally Posted by Hidron

Does sound odd. Did you notice what patch date it listed for the offsets that did not appear to be working? 2.2.9 worked fine for me and I haven't had to change anything.

---

You know, Hidron, once I installed 2.2.9 I could have sworn the patch date was 11/8/2012. Which I thought was a little odd -- perhaps I somehow had an older INI file in there by mistake.

It's still odd that 2.2.8 stopped working suddenly for me on 11/15/2012 after the Windows patch and subsequent reboot, but unless others post with the same issue, I'd rather chalk it up to something stupid I may have done. But I know I've read this board ("Lurker!") enough times to see someone post an issue with a fix and have it help me, no matter how odd it was. :)

I can say though the work you guys put in really rocks, and I speak for the masses with a big "Thanks!", for every one of me or others who post that, there are dozens more that appreciate what you do, and all the work you've put in.