NEWS: MySEQ Open 2.3.0 Released

Announcing the release of MySEQ Open 2.3.0. The installer can be downloaded from the files section on sourceforge.

Release Version 2.3.0</SPAN>
Dated 11 February 2013</SPAN>

Server Changes</SPAN>

1. Added some optimizations to server code. The server code is not very cpu intensive already, but this saved 20-40% when testing. </SPAN>
2. Fixed a bug that would cause the client/server to get out of sync. </SPAN>
3. Changed how server/client interact when switching characters between multiple EQ sessions. This requires both the client and server to be updated to 2.3.0 or higher to work correctly. This fixes an issue that caused the client/server connection to be lost while switching characters. </SPAN>
4. Improved the detection for a running eqgame.exe process. This should require less stopping and restarting the client connection to maintain a MySEQ session operating. </SPAN>

Client Changes</SPAN>

1. The positions.xml, which stores the docking windows locations and positions, will now be stored in the application data folder. </SPAN>
2. The prefs.xml and myseq.xml will also be stored in the application data folder now too. </SPAN>
3. Timers will no longer be loaded or saved for certain zones like guild lobby, nexus, poknowledge. </SPAN>
4. The character selection in the pull down menu should now show the correct character checked. </SPAN>
5. Fixed a bug that would cause the character selection menu to not list all the characters available to select. </SPAN>
6. Fixed a bug that would cause the data stream between the client/server to become corrupted when switching characters. </SPAN>
7. Removed the refresh list from the character selection menu as it is updated when the menu is pulled down automatically. </SPAN>
8. Added to the options menu the ability to show the current character name in the application title right after the map name. </SPAN>
9. Changed the way the server/client interact when running multiple clients and switching between them. This requires using the new server version to work correct. </SPAN>
10. The level override in the options is no longer limited to having a max value of 85. </SPAN>
11. The zone name in the window title will now come from what is looked up in the zones.ini file, when the map is loaded.

</SPAN>

Razzle

Something for you do update, mate.

Code:

---

[File Info]
Patchdate=12.02.2013

[Port]
port=5555

[Memory Offsets]
ZoneAddr=0xd665f0
SpawnHeaderAddr=0xdeaa28
CharInfo=0xd59078
TargetAddr=0xd59090
ItemsAddr=0xd55be0
WorldAddr=0xd59048


[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=0x46c
HideOffset=0x3cc
LevelOffset=0x478
RaceOffset=0xea8
ClassOffset=0xeac
PrimaryOffset=0xfb0
OffhandOffset=0xfc4

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

---

Thanks Fireblade.

Razzle

Btw, the server debug mode could use a little overhaul. Sometimes I like to verify some offsets and use the debug mode for that.
For example to confirm spawnheader offset the "wt" command finds some items in the spawn list but the scan at the end to get the offset pointer does not produce any result.

I never had a look at your source code so not sure if it would be an easy fix and I would like to avoid messing with it. :D
It's not something that stopped working recently only, it stopped working long time ago iirc.
Maybe you get around to fix it sometime. ;)

The debug code does need an overhaul. I am not sure who wrote it originally. But it for sure needs some work.

Razzle

Been working some on the secondary offset patterns for the offsetfinder.
However I was running into some issues I couldn't really explain myelf at the start till I found the connection. :P

I have been using the offsetfinder that's built into the server and was puzzled why I did not find some offsets while I was 100% sure that there should be a result. Well, then I noticed that for finding secondary offsets you reference to the config file instead of grabbing them directly with the routine for primary offsets and directly using those results. :)
I guess both alternatives have their ups and downs. Would be great to have the option to use either way! ;)

Something you could also check since I think it is not working correctly:

• x,y,z offset routine seems to be incorrect, it returns a DWord Value instead of the expected byte value.
  y offset routine did not produce a result at all even tho I am sure that there should have been a result considering the used Pattern/Mask.
• as suggested above I recommend to include primary offset routine to deliver the results internally for the secondary search (optionaly)

It's not complete yet but this is what I think should produce some results. More to come (I hope... :) )

Code:

---

[SpawnInfoXOffset]
Start=0xFF000
Pattern=\xA1\x78\x80\xD5\x00\xD9\x40\x6C\x83\xEC\x0C\xD9\x40\x68\xD9\x40\x64\xD9
Mask=xooooxx?xx?xx?xxtx

[SpawnInfoYOffset]
Start=0xFF000;
Pattern=\xA1\x78\x80\xD5\x00\xD9\x40\x6C\x83\xEC\x0C\xD9\x40\x68\xD9\x40\x64\xD9
Mask=xooooxx?xx?xxtxx?x

[SpawnInfoZOffset]
Start=0xFF000;
Pattern=\xA1\x78\x80\xD5\x00\xD9\x40\x6C\x83\xEC\x0C\xD9\x40\x68\xD9\x40\x64\xD9
Mask=xooooxxtxx?xx?xx?x

[SpawnInfoNameOffset]
Start=0x3F000
Pattern=\xA1\x58\xEA\xA4\x00\x05\xA4\x00\x00\x00\x8D\x54\x24\x50\x2B\xD0\x8D\x9B\x00\x00\x00\x00
Mask=xooooxtttt?x???xxxxxxx

[SpawnInfoTypeOffset]
Start=0x120000
Pattern=\xA1\x78\x90\xD5\x00\x85\xC0\x0F\x84\xEC\x05\x00\x00\x80\xB8\x25\x01\x00\x00\x00\x0F
Mask=xooooxxxx???x??ttttxx

[SpawnInfoSpawnIDOffset]
Start=0x7F000
Pattern=\x8B\x0D\x78\x90\xD5\x00\x8B\xB0\x48\x01\x00\x00\x8B\xB9\x48\x01\x00\x00\x74\x6C
Mask=xxooooxx????xxtttt??

[SpawnInfoHideOffset]
Start=0xAF000;
Pattern=\x3B\x0D\x78\x90\xD5\x00\x0F\x85\x9D\x00\x00\x00\x8B\x91\xCC\x03\x00\x00
Mask=xxooooxxx????xtttt

[SpawnInfoLevelOffset]
Start=0xF000
Pattern=\x74\x33\x00\x00\xA1\x24\xEF\xC6\x00\x88\x90\xA4\x0E\x00\x00\x8B\xCE\xE8\x22\xF9\xFF
Mask=????xooooxxttttx?

[SpawnInfoRaceOffset]
Start=0x13F000
Pattern=\x8B\x0D\x78\x90\xD5\x00\x8B\x91\xA8\x0E\x00\x00\x8B\x80\x70\x33\x00\x00\x83\xFA\x0C\x7E
Mask=xxooooxxtttt?????????x

[SpawnInfoClassOffset]
Start=0xF000
Pattern=\x8A\x4C\x10\x49\x8B\x15\x78\x90\xD5\x00\x88\x8A\xAC\x0E\x00\x00\x8B\x8F\x24\x02\x00\x00
Mask=xxx?xxooooxxttttx???xx

---

Did you find some time to check into this yet?

Not yet. I was trying to make some time today but barely opened code and got called away. Tomorrow is looking positive for getting something done.

Code I used in server was not set up to find a byte. Was always looking for a dword. So it always assumed mask had "tttt" in it rather than one "t". It has to do with some template code I changed that would not compile.

I was rather crude, but rather than change templates and hard code each offset, i made it check the mask. 1- t and makes it retrieve a byte, 2 a word and 4 a dword. Works and changing mask does not require change in code.

Razzle

Quote:

---

Originally Posted by Razzle

I was rather crude, but rather than change templates and hard code each offset, i made it check the mask. 1- t and makes it retrieve a byte, 2 a word and 4 a dword. Works and changing mask does not require change in code.

Razzle

---

Great, that's the way it should be. ;)

Agreed. I thought about fixing the templates. But I quickly realized that letting the mask dictated the type was better. Now my crude fix doesnt feel so crude.

Razzle

Sounds like you're making some good progress Razzle, and avoiding "hard coding" is almost always the best approach in good quality software development.

Hey Razzle,
seems you have been pretty busy lately but could you push out another release for the Server code with fixed secondary offsets finder?

rgds
FB

I will put out new version with finder changes. Busy is an understatement.