11/5 Offsets

[MQSEQ2]

[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7838464

The ZoneAddr=7838464 has been reported to work in LDoN and normal zones.

If that offset doesn't work you can use:
ZoneAddr=7055468

This address will not work with LDoN zones from what I've been told.

[Yrvaken]

dont work whit 1.9b. Map dont load. and if i open map myself it stays there for some sec and a error mess apear and map unloads

[MQSEQ2]

Ok lets try a different Zone address:

From MacroQuest:

Zoning=0076a808
Zones=0071d874
ZoneInfo=008ba82c

Lets try:

ZoneAddr=7776264

Or

ZoneAddr=9152556

[Midnight]

Ok the '9' one worked to load spawns.. but map doesnt load and the program insta crashes after spawns pop up. So others will need to be converted? This is on 1.10 + 1.54 (or whatever newest ver)

[MQSEQ2]

Edit the myseqserverc.ini file with Notepad then scroll down to the ZoneAddr line make the change then save the file.


That should do it for you. Once we get the correct settings I will post a new Ini file so everyone can download it.

[CybMax]

As i said in another thread, you cannot directly convert the ZoneAddr from Hex to Decimal and use with Myseq

There is some difference in the address, and i am pretty sure i once found some "formula" to convert this.. ie. MQ-x=Myseq sumtin or other..

Will take a look at it..

[Yrvaken]

ok whit ZoneAddr=7776264 the map did not whant to load on start up but if i loaded it up myself it did seam to work great.. and


ZoneAddr=9152556

did not work for me att all
Tested on server 1.10

[MSMage]

This offset:

ZoneAddr=9152556

Works, though i had to manually load the map :)
To add the offset, open up "myseqserverc.ini". Find the line under the header Memory Offsets titled "ZoneAddr" and change the number so that it matches the new working offset.

[Yrvaken]

ehhmm now ZoneAddr=9152556 works :eek:

[MQSEQ2]

Good job all on the testing of the offsets.

Once I get home I will be able to login into EQ and test the offsets if we don't get them resolved ahead of time. I will step thru the code to see what is beeing returnedfor the server. There could have been some EQ structure changes that may require some more work.

[CybMax]

Does not load map here at me tho.. So even tho it dont produce any error message, does not mean it work..

[MQSEQ2]

I will look into it ASAP. Does it show the Short Zone Name in the lower Right hand corner? sounds like the Short name is not coming accross right and that is what is used to open the proper map file.

I will also try to add more logging information so we can look into what's being done for those who don't have compilers.

[CybMax]

Nope.. it does not show the short name at all, so my guess is that its the wrong address.

I remember i did once take a look at old MQ adresses and old myseq offsets (working ones).. had 2-3 of them, and i found some "formula" i used.. I dont remember what i did anymore, and i have been to lazy of late to refresh that. (specially since the patches is not that often anymore)

So.. If anyone can grab some old verified myseq offsets from previous patches, and compare them with the offsets from MQ of the same date, i am sure you can figure it out..

[JustAnotherUser]

ZoneAdr=7055468 works for a friend. My install is §%/§/up though :)

[CybMax]

Verified!

[SparhawkKR]

ZoneAdr=7055468
Appears to work correctly, and completly...

ZoneAddr=9152556
Resulted in the zone short name comming up with the Targeted Mob... Just incase that helps in working out further info...

[MQSEQ2]

Can we get others to verify the following address is working fine:

ZoneAdr=7055468

[Yrvaken]

ZoneAdr=7055468 and ZoneAdr=9152556 Both works but dont load the map for me .

[Midnight]

Loads and works but it immediately crashes the server

[MQSEQ2]

That that Jag is on the Forum he can test them via the compiler ;). I have 3 hrs togo before I get to go home :(, ohh wait I'm a contractor and I can leave when I want too (just don't get paid :))

Jag can you load the server in debug mode with the offsets above and see what the Zone name is returning with them? Also what do you think you can do with the logging features in the server?

[TempLoginName]

7055468

I found this offset indepently of the other posters and can confirm it works. MySEQ is working 100% for me, however I'm using version 1.14.1 for the client. The server is finding the zone short name at this address.

Old No Name

[MQSEQ2]

Ok folks,

we've been getting reports that ZoneAddr=7055468 is working please check it out and let us know.

[Squiffy]

Works perfectly for me.

[slartibartfast]

I'm getting 2 possibles, last patch one of these didnt work for ldon zones, but I havent tried an adventure yet. I'll try one and report back


ZoneAddr=7055468
ZoneAddr=7055504

[Ratala]

Can some one please post a Copy Paist version up here for us Noobs :D

[Ratala]

Okay. NM.... I figured things out and I am up and runnin again :D

[Shiori]

Copied from another thread. These work with 1.9b AND autoload.

[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7055468



[SpawnInfo Offsets]
NameOffset=1
XOffset=104
YOffset=108
ZOffset=112
HeadingOffset=132
SpeedOffset=128
SpawnIDOffset=384
TypeOffset=364
ClassOffset=378
RaceOffset=392
HideOffset=376
LastnameOffset=65
NextOffset=316
LevelOffset=372

[GroundItem Offsets]
ZOffset=32
XOffset=36
YOffset=40
NameOffset=44
SpawnIDOffset=12
NextOffset=4

[CharInfo Offsets]
SpawnInfo=0x0d7c

[MQSEQ2]

I will check out Server 1.10 with the new offsets tonight. It sounds like 1.9b is working with the offsets above.

[slartibartfast]

Following zone address is ok for LDON zones

ZoneAddr=7838464

[MQSEQ2]

These offsets work fine with 1.10 Server, maps loads with no problems when zoning.

[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7055468

Food for thought:
Look like we might need to create a new LDoNZoneAddr=7838464 so we can keep them separated if the 7838464 number does not work for regular zones. If we start splitting then we will need to check for a flag for LDoN try one to see if it worked then try the other if it didn't.

[CybMax]

ZoneAddr=7838464 seem to work with regular zones as well.. I did not verify this in LDoN now (1:30 am here.. hehe), but if someone will, and post a positive, i think my "theory" below could be interesting.

After taking a look at old working offsets, it seem like the zonename can be in different places, not all working with ldon i guess..
But one thing that is the same for those that work with ldon is that the zoneaddr is a higher address than the "rest" so to speak.. If you look at the Itemsaddr, charinfo, charaddr, targetaddr.. they all are in the same address space (this time in the 74610xx space somewhere).. And if you look at diff "fixes" from the last 9/10 offsets for ldon, the zoneaddr number was at first a LOWER number than theese, but was later found working with LDoN at a higher address..

And when you compare this with MQ offsets, you find sumtin interesting.. Ie... none of the "zonexx" addresses from mq work at all.. so i guess some manual findings is needed (posted on thread in the general section.. sorry no link for it).

All in all.. if you take the MQ address for "Zoning" and convert this to decimal, then add the number 62000 you are close..
Fire up your favorite memory viewer, and search for the zone short name, and if you get a hit around that number you got from MQ+62000 you should be getting close :)

Dunno if this was of some help, but at least i think i am aiming at something here :) I will see if i get some time to do some memory scanning tomorrow, but if someone wanna test this theory, it would be much welcome.

[MQSEQ2]

I will try to look at MQ some for so I can find the Zone offset off the main ZoneAddr address. this is just like the SPAWNINFO structure where you hase the base SPAWNAddr then different offsets for what ever you are looking for.

[SurfAngel]

Originally posted by Midnight
Loads and works but it immediately crashes the server
I'm running into this problem as well, using:

[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7838464

[edit]

Hmmm, might not be an offset problem afterall. Tested it with 1.15.4 client against 1.9b server, works fine there. Might be the 1.10 server.

[Fidd]

Looks like the 1.10 server can't run with just the memory offsets.

If I remove SpawnInfo, GroundItem, and CharInfo offset, the client hangs, if I got em all, the server crashes shortly after its started.

/Fidd

[showme1]

same as surf and fidd, with just the basic offsets and hangs. with the full set it crashes

[minigirl]

same results as Fidd above me stated

EDIT: However 1.9b runs smooth as silk with latest client aswell.


I have to say ..if MySeg continues as good as it is showing with these latest clients...I may stop using ShowEQ at some point. I do love ShowEQ with a passion and will continue to keep the server updated...but..just one day I may end keeping it up to date.


Nice work to so may of you..mainly the coders...you know who you are.

[MQSEQ2]

Thanks for the support :).

I loved ShowEQ but I have forgotten to much Linux and I just never got into looking at the source code of ShowEQ. I will try to keep the momentum going with MySEQ by adding more options. The cool thing about MySEQ is it's forcing me to learn C# even tho I could have rewritten the project in VB and have it alot future along than where it is now, but it's a community project so we will continue on the same path. I will just have to step up to the plate and learn more C# hehe. Thanks guys for that.

Everyone has done an excellant job (not just developers) with the project. Remember without testers we will never figure out all the bugs. Keep up the good work.

[CybMax]

Used 1.10 server and ZoneAddr=7838464 for a couple of hours.. did not notice any hangs or any problems.. Still not tested LDoN tho, but zoned several times around pok, pot, bot, pov.. ++ did not notice any problems.

The 1.54.4 client also seems very fast and sturdy. I like the "targetinfo" box where it picks up what i click at and display info in the myseq window..

just gotta say : Proggers! GREAT JOB!! :)

[gmiller]

Please let me know what I am missing.

I've done this on both my windows2k machine and my WindowsME machines. (until this last patch I was using myseqclient 1.12 and myseqserverc1.9b)

#1 deleted previously installed myseqclient and myseqserverc folders.
#2 unzipped myseqclient 1.9b and myseqserverc 1.151, 1.152, 1.152exe, 1.153, and 1.154 folders.
#3 Unzipped the maps into the myseq/maps folder.
#4 replaced myseqserver.ini or myseqserverc.ini with latest offsets will list all I have tried below.

After Launching server then client, then clicking "GO" I get the following error message on my Win2k machine...

Could not connect to the server: A connection attempt failed because the connected party did not properly respond after a period of time, or estabilished connectoin failed because connected host has failed to respond.

After closing the server and client, I then ...
#1 Delete my client folder.
#2 Installed 1.14 client

When trying to run the 1.14 client, I received the same error message as the 1.154 client.

I then unzipped into the 1.14 client installation the contents of all the folders from 1.151 to 1.154 but again received same error.

I then deleted the 1.9b server installation and installed 1.10 server. Again same error.

Here are the offsets I've tried in ever instance of each installation...

#1
[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7055468



#2

[Memory Offsets]
GroupCountAddr=7454208
GroupAddr=7454536
SpawnHeaderAddr=7460984
ItemsAddr=7460988
CharAddr=7461040
CharInfo=7461048
TargetAddr=7461052
GuildsAddr=7479052
ZoneAddr=7838464



Please help.

*edit*
I also tried installing 1.14 client then unzipping only the 1.154 folder into it as a friend of mine had done and said it worked for him but I got same error as previous attempts.

[MQSEQ2]

Check your port settings. If you are using Server 1.10 it's in the Ini file. If you are using 1.9b it's hardcoded to 5555. Make sure your Client is using the same port as the Server.

[Mixy!]

MQSEQ2, are the offsets on the front page the correct ones? Also, is server 1.10 working properly now? Last i tried it crashed immediately.
Do i have to replace the offsets below the [MEMORY OFFSETS] section to get 1.10 to work? And if so, with what?
-Des!

[MQSEQ2]

I've been getting mixed results on the Server 1.10. I do believe the offsets on the front page are the correct ones. Those should work for 1.9b and 1.10. If you are still having issues with 1.10 try using 1.9b. There not alot of new features in 1.10 vs. 1.9b, I was getting prepared to major changes so I wanted to introduce a smaller converted version before making major changes.

I'm currently rewriting the Server so it will support being a SysTray icon and will introduce the major changes in this version.

[datadog]

Originally posted by MQSEQ2
Edit the myseqserverc.ini file with Notepad then scroll down to the ZoneAddr line make the change then save the file.

That should do it for you. Once we get the correct settings I will post a new Ini file so everyone can download it.

Did a .ini file ever get posted? I got crosseyed looking for one, and trying to make sense out of which offests to use.

I have tried several variations of client/server/offsets, but the best I can do is get the client to connect to the server, but no map or spawns. No crashes.. just no data.. kinda leads me to believe my offsets may be wrong.

Could someone confirm a set of offsets, and a client/sever set that works with 98 ?

Much appreciated

Thanks.

[MQSEQ2]

The Ini file is the one for the Server and the offsets posted here should work for you.

[slartibartfast]

If you want MySEQ to work in LDON zones use

ZoneAddr=7838464

- it works for both normal + LDon zones.

All others offsets return a short name like

mmca_262

in LDON zones which will prevent the maps from autoloading.

[owned]

i tried the new offset yesterday after server up and it worked well for me. but i couldnt connect to the server today. :(

[gmiller]

changed server ini file to use port 5555 which was what client prefs file showed it was using.

Still same error message ...

Could not connect to the server: A connection attempt failed because the connected party did not properly respond after a period of time, or estabilished connectoin failed because connected host has failed to respond.


I even manually loaded the map of the zone my character was in at the time then clicked go but no luck.


My setup is simple 1 computer dual boot win2k and winME with dialup connection. Never had problems running 1.12 client and 1.9b server until this patch. Now I can't get 1.10 server and 1.54 client to work.

[MQSEQ2]

Try and use Server 1.9b and Client 1.15.4 with the offsets posted on the front page.

[Dark]

I'm having a strange problem.
Just gone back to MySEQ and the client is talking to the server but the screen is blank and no mobs listed.

I Downloaded the latest build and using the exe.


I tried 1.10 and 1.9b same result.

I guess its offsets. Is there an updated offset file?

[MQSEQ2]

Modify your Ini file for the server with the offset on page 1 of this thread.

[Dark]

That fied that. No spwan movemnet though.
got updates set to 250ms

[Dark]

Found out why no movement. Server is Dr Watson erroring.

[MQSEQ2]

Use 1.9b with the Offsets and it should work.

[Taleriana]

Originally posted by JustAnotherUser
ZoneAdr=7055468 works for a friend. My install is §%/§/up though :)

This works for me as long as I manually open the map... the bottom right corner says "ORD" and at first I was getting some kinda map error with "ORD<BOX>.map" as the culprit... this zoneadr doesn't do that, but still no maps automatically (btw, if you open the wrong map manually - it looks really funny, hehe :p ).

- Taleriana

P.S. Server is 1.9b and not sure what client is... too late tonight to check, I'll check again in the morning - hubby went to bed without me !

[deda]

ZoneAddr=7838464
This works with server 1.9b and client 1.15.4
Both old and ldon zone maps get loaded automatic.

[Taleriana]

Originally posted by deda
ZoneAddr=7838464
This works with server 1.9b and client 1.15.4
Both old and ldon zone maps get loaded automatic.


Aye, I can confirm that this works now with both old and ldon. with server 1.9b and client 1.15.4 - my only problem was I had the map background as black and the map lines were black! As soon as I turned it to gray, it worked fine.

I AM running into a strange problem.. when I turn "players off" in the spawn list, it just starts duplicating all the players in the list over and over and over (so I was forced to leave that on and then it would pick up players not in my zone). Wrong offset somewhere maybe? I wanted to just see the mobs in the zone, no players.

- Taleriana

[gmiller]

Heh I figured out my lil problem, it was so simple I am kind of embarrassed. I kept forgetting to change the IP ID in the client prefs.

Server 1.10 and Client 1.15.4 are now working like a charm with the offsets from the first page.

[MQSEQ2]

I'm going to add some code to check Map lines if they are same color as Map Background if so then change the color. This should take care of the lines not being seen for any map file.

[slartibartfast]

MQSEQ2 - the line colour checking code was in version 1.14.2

- I was planning on extending it so that users could customise the colour mapping. So that you can use the same map as EQ, but with a different colour background and the maps look good in both places.

[MQSEQ2]

Cool, I will check in 1.14.2 and pull out that code and add it in.

I will also look at my VB code I wrote that displays the Maps and see if there is anything I can use to help clean up and/or make the Map drawing more optimized (It may already be already that way now).

[Pit Boss]

I am using ZoneAddr=7838464 and LDoN maps are not loading. I get an error message.

[undeadorc]

been getting where it says Race: #here then Out of Range

[MQSEQ2]

Check your Race.txt file in the Cfg directory. You can add a few more at the end of the file like Unkown## (##is the next line number), etc. Then once you get the body type figured out with what race, post it here and we can update the Race.Txt

[Pit Boss]

Ok. I was mistaken. LDoN maps are working except for Mir. So there may just be a problem with it.

[jag111]

It's less likely a problem with Mir, and more likely a problem with your particular Mir maps that are giving the error...or even 1 particular Mir map for that one dungeon you happened to be in when you got the error.

[Pit Boss]

Yes. That's what I'm thinking.

[MQSEQ2]

I think the 1st Mir map is messed up. If you try to load it while stepping through the code I think it with throw an exception error.

I was looking at one that didn't have enough Tokens in the line so during the parsing it wasn't there, so a null can't be converted to an int.