Patch 26 august

[slartibartfast]

Following Offsets stolen from macroquest. Unfortunately it looks like there has been some structure changes so MySEQ currently broken :(

[Memory Offsets]
ZoneAddr=7751112
CharAddr=7375288
SpawnHeaderAddr=7375232
TargetAddr=7375300
ItemsAddr=7375236

[slartibartfast]

The spawninfo structure has changed, the following offsets seem to get the basics working again.

[SpawnInfo Offsets]
NameOffset=1
XOffset=72
YOffset=76
ZOffset=80
HeadingOffset=100
SpeedOffset=96
SpawnIDOffset=328
TypeOffset=308
ClassOffset=322
RaceOffset=336
HideOffset=320
LastnameOffset=248
NextOffset=228
LevelOffset=316

[suziwon]

Anyone able to discern from the macroquest info if the ground item offsets need to be changed, and if so, what the changes need to be?

I love my ground spawns!:p

Thanks in advance!

Suz

[slartibartfast]

Ground Spawn Info Structure was changed as well new offsets:

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

[Lance]

are the character info offsets the same as before?

[slartibartfast]

The version of MySEQ i use doesnt show or use the xp + aaxp values so i havent bothered to look...

There is a good chance they have moved tho...

[cavemanbob]

Well done, I still can't test them myself, but I'll post them in news anyway. Don't worry about hte XP and AAXP offsets, they aren't being used quite yet. The char information structure that myshoweq uses should be identical to the mob one so it should be ok.

[KaL]

Used the posted offsets today; works great!

[Jono]

These new offsets don't work for me.

With Server 1.9b on Windows 98SE and client 1.2 or 1.3 on Win2K SP3 all I get are overflow errors on the client.

Was working fine with the previous offsets before the patch.

Any suggestions?

[slartibartfast]

Does it always crash out - or only when u zone?

- I have seen a problem when the server is on win 98 machine caused by it sending invalid packets during zoning.

[Jono]

With previous offsets I did have the problem with it crashing during a zone. I just got used to pressing the stop button before zoneing.

With the current offsets I get the overflow error as soon as I start the client. It brings up the list of mobs on the left then I get the big red cross on the screen and an overflow error.

Perhaps because of the new structure the bug that was effecting zoneing on Win98 based servers is now effecting all operations of the program?

I hope this can be resolved as I do miss MySEQ.

[GD_EQ]

I also get the the "Crash on Zone" bug with WinME.

[Jono]

GD_EQ is MySEQ working for you with the 26 august offsets? If so I'm probably wrong about my problem being related to the "overflow on zone" bug.

[GD_EQ]

These are the offsets I use, don't recall what date they are from.



[Memory Offsets]
ZoneAddr=7751112
CharAddr=7375288
SpawnHeaderAddr=7375232
TargetAddr=7375300
ItemsAddr=7375236

[SpawnInfo Offsets]
NameOffset=1
XOffset=72
YOffset=76
ZOffset=80
HeadingOffset=100
SpeedOffset=96
SpawnIDOffset=328
TypeOffset=308
ClassOffset=322
RaceOffset=336
HideOffset=320
LastnameOffset=248
NextOffset=228
LevelOffset=316

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

[Jono]

Yes those are the same 26th August offsets that don't work for me.

So they are working for you GD_EQ?

[GD_EQ]

Yes, they do work for me.

[SchwannyT]

If you are running the server on a win98 machine you will get the overflow error. I also get the crash when zoning but that is a "Number to large or small to be an int32" error. I dont understand why it would only effect win98 machines and only after using the Aug. 26 offsets (worked fine before). Any ideas?

[GD_EQ]

BTW, I run both the Client and Server on the same WinME box.