Patch on Tuesday, August 26th

[LordCrush]

FYI


Scheduled Update
On Tuesday, August 26th, at 3AM Pacific, (-7:00 UTC), all EverQuest worlds will be brought down for a scheduled update. The estimated downtime is 7 hours.

The SOE Game Operations Team

[whiteviperx]

Do we know what the patch is going to cover?

[guice]

What ever it be - SEQ is broken.

[Hendrix_Morton]

Im stuck at work for another 7 hours....Did today's patch bork us ?

[Cheshire_Dragon]

Well the servers are down for another 10min according to the SOE team....I have learned from past experience that when an update is usually longer then a few hours SEQ gets junked. Of course, I can't test this theory for about another 6hrs. I hate my job.

*runs off to re-write resumè and find a new job*

heh heh heh

[uRit1u2CBBA=]

the Status page now shows the ETA to be 10:45 PDT - that is about 20 minutes from the time of this post.

[serberus]

ShowEQ is broken as of the 26/08/03 patch. It doesn't recognise what zone you are in and the player entity is way off to the side making it zoom out by a huge amount.

There are "unknown" spawns appearing on the map and they are moving, they don't appear to bare any relation to anything in particular, doesn't look like a standard NPC configuration.

Serberus

had to crop the image to 800 pixels high for the message board.

[hhh]

as above, except that it is also jumping around very crazily. Kind of amusing somewhat.

Also, not suprisingly, getting a lot of warnings playerposcode is the wrong length, 0x013a, 0x0125.

Im certainly no expert but looks alot worse than a simple opcode fix :)

[ieatacid]

some of what i'm getting:

WARNING: PlayerPosCode (0022) (dataLen:32 != sizeof(playerPosStruct):20)!
error: size > left (size=228, left=111, opcode=0x013a)
WARNING: BeginCastCode (0016) (dataLen:217 != sizeof(beginCastStruct):14)!
error: size > left (size=199, left=149, opcode=0x013a)
error: size > left (size=241, left=19, opcode=0x0125)
error: size > left (size=185, left=51, opcode=0x013a)
error: size > left (size=230, left=9, opcode=0x013a)
error: size > left (size=241, left=84, opcode=0x013a)
error: size > left (size=245, left=29, opcode=0x0125)
error: size > left (size=219, left=52, opcode=0x00fa)
error: size > left (size=236, left=18, opcode=0x013a)
error: size > left (size=117, left=9, opcode=0x013a)
error: size > left (size=93, left=35, opcode=0x00ec)
error: size > left (size=246, left=74, opcode=0x0125)
error: size > left (size=247, left=56, opcode=0x0125)
error: size > left (size=247, left=62, opcode=0x0125)
error: size > left (size=112, left=9, opcode=0x013a)
WARNING: PlayerPosCode (0022) (dataLen:32 != sizeof(playerPosStruct):20)!
error: size > left (size=248, left=131, opcode=0x0125)
error: size > left (size=229, left=15, opcode=0x00ec)

[Zaphod]

Im certainly no expert but looks alot worse than a simple opcode fix


Haven't tried yet, but it is probably just a bunch of structure organization changes. Shift things over a byte or four and SEQ looks real wacky.

Enjoy,
Zaphod (dohpaZ)

[LordCrush]

WOOOOOOOOOOOOOOOOOOOOOOOOT Zaphod
/cheeeeer


Nice to see a post of you /wave


Busted on German Server tooo :(

[Booboo]

Well I always hate asking the dumb question but can someone post exactly what they changed to get SEQ working again? Zaphod seems to know.. LordCrush seems to know.. I don't know, I always get confused =)

hehe please help,

booboo

Edit- or maybe I just read this all wrong... man I am still confused..

[LordCrush]

No i dont know .. broken and thats that what Zaphod said

i am no developer and have no clue of the EQ-Protocol ... i need updates from someone who knows that and takes his time to find it too :/

Just was happy to see a post from Zaphod =)

[S_B_R]

Nah, Zaphod was just saying a small change can make SEQ look very messed up. And LordCrush's excitement was due to the fact that we haven't seen Zaphod post in quite some time. Mr. Beeblebrox is a notable figure in the history of SEQ ;)

[Booboo]

After reading your post over again I realised it was simply a "WOOT" to say hello.. and not a WOOT thanks for fixing it. hehe

like I said I am still confused and now I have confused you all. I will go now..

booboo

[fester]

Looks like someone needs to dump the new decode.cpp table.
It is very likely that this table needs updating every single patch. I would consider a patch that did not require this step to be very rare. It is a DEAD giveaway when you see the errors like "size > len" pop up because (if you have forgotten) the decode.cpp table deals with the size of the opcodes that do not carry with them their size.

I may look at this tomorrow (Weds) if no one else does.

[fuqjak]

Not sure if it matters or now but it looks like the MySEQ people have theirs working again - just from Spawn Offset and Memory Offset changes. Might not be as complicated a change as we might think it is?

[fester]

Someone less lazy than I, can create the decode.cpp from this:
.text:004256F5 push edi
.text:004256F6 push 4
.text:004256F8 mov ecx, 3FFh
.text:004256FD or eax, 0FFFFFFFFh
.text:00425700 mov edi, offset dword_7558A0
.text:00425705 pop edx
.text:00425706 repe stosd
.text:00425708 push 6
.text:0042570A mov dword_755D70, edx
.text:00425710 pop ecx
.text:00425711 mov dword_755C88, 1Fh
.text:0042571B push 3
.text:0042571D mov dword_756154, ecx
.text:00425723 pop eax
.text:00425724 mov dword_756158, ecx
.text:0042572A push 8
.text:0042572C mov dword_7560FC, eax
.text:00425731 mov dword_756100, eax
.text:00425736 pop eax
.text:00425737 mov dword_7558FC, eax
.text:0042573C
.text:0042573C loc_42573C: ; DATA XREF: .rdata:005A59D4^Yo
.text:0042573C mov dword_755C0C, 17h
.text:00425746
.text:00425746 loc_425746: ; DATA XREF: .rdata:005A5AE8^Yo
.text:00425746 mov dword_755D34, 9
.text:00425750 mov dword_755928, 12h
.text:0042575A mov dword_755984, 0Ch
.text:00425764 mov dword_755D88, eax
.text:00425769 mov dword_755C84, 88h
.text:00425773 mov dword_755B90, eax
.text:00425778 mov dword_755C50, edx
.text:0042577E pop edi
.text:0042577F retn
.text:0042577F sub_4256F5 endp

[LordCrush]

spanish, greek, chineese :p

i would love to lear this, but have not enough time :(

[Zaphod]

Booboo said:


like I said I am still confused and now I have confused you all. I will go now..


To which I say: "All Hail Eris, goddess of discord!"

fester said:


Someone less lazy than I, can create the decode.cpp from this:

I would, but alas I'm not familiar with the new decoding and implicit length stuff since it occurred during my sabatical from ShowEQ. So without having the old dissasembly to compare against the old implicitlen() function's contents it is not immediately obvious to me what to do with the dissasembly you gave. I'll give it a go, but all assistance is appreciated.

Once the new implicitlen stuff is taken care of it shouldn't take me too long to figure out the new opcodes and structure reorganizations.

I had already started the process of bringing the SEQ codebase back up to snuff, including being more current with the protocol as it existed prior to the 8/26 patch. From that I've gotten a bunch of good reference data from 8/25 to compare against the 8/26 protocol changes. In fact I've got some of the major opcodes already.

Once I have a viable version of SEQ again I'll do a CVS commit. Which should make life easier for most. Any and all help towards that goal is greatly appreciated.

To LordCrush, S_B_R, etc., All I can say is thanks for the warm welcome back.

Thanks and Enjoy,
Zaphod (dohpaZ)

P.S. He's baaaack.... ;-)

[hhh]

as above, except that it is also jumping around very crazily. Kind of amusing somewhat.

Also, not suprisingly, getting a lot of warnings playerposcode is the wrong length, 0x013a, 0x0125.

Im certainly no expert but looks alot worse than a simple opcode fix :)

[gruefood]

Zaphod said:


P.S. He's baaaack.... ;-)

I've been a lurker here since long before I ever registered a user on these boards so I don't usually have much to say.

But THIS is a GOOD THING.

We've missed ya. Welcome back!

[sea4th]

I have been doing more coding and really appreciate the background work you saved me when I fired up the kdevelop gui and was tickled to see a project file already in the ShowEQ directory. I will remember your name for a long time since the kdevelop gui brings an organizational structure to the files, classes and structs that are showeq in a graphical easy to review manner. What had taken me many hours before to begin to understand the showEQ structure was placed before me in seconds ... I know I am going to learn more now that you are back. Learning Linux and a new C++ QT flavor and the MOC has taken chunks of time but progress is unavoidable.

[Velium_hound]

Could someone change the status to red so people can easily see when the Skittles are available?