Any fix for 1-20-2021 patch?

[Zyxi]

I tried the codes posted by cn187 for the 1/12 Patch on test and they aren't working for me on the live servers. Is this just something I did wrong in the patching and compiling, or are the codes on live after the patch today different than what was on test and in that post?

[fransick]

Typically they are different and we have to adjust opcodes and structs on live. Thankfully, CN and Newby are quick and efficient and patches are uploaded pretty quickly. In fact, an update is already posted in the ShowEQ News section!

[cn187]

FYI, there are some minor issues with the patch in the News section. I rushed to get it done after the servers came back up and didn't get a chance to adequately test because I had to leave. I'm told skittles are working in general, but there are some minor oddities (intermittent map load, self spawn showing up as other player). I won't be able to address it until later tonight when I get back, so if someone else wants to give it a look, please do. Otherwise I'll get it sorted out as soon as I can.

[fransick]

I saw that after I replied. Mine tends to seg fault right away and I didn't have time to to check the obvious opcode/struct stuff. Been a very busy new year work-wise so tough to even find time to play despite being in lockdown. Work from home seems to mean a lot more work than ever, haha

[kkmonte]

Yea I'm having the same issue, of course this is a brand new centos 7 laptop I built about 3 hours ago and installed packages and trying to get it working, i'm able to make and build it without any errors, i can launch it, but when I do either detect next session or specify ip address, and zone, i get pages of eqpacket: unhandled net opcode ... then a warning op_zoneentry doesn't match and finally a seg fault core dump. Let me know if other people are getting it to work, maybe its an issue with my new machine. Thanks.

[tearofsoul]

Same here. any help would be apperciated

[kryshael]

ok....I am a complete noob here. I have always copied/pasted the offsets into MySEQ config and was done. I read the instructions on the new 6.0...and quite frankly dont have a friggin clue on what to do...FML

[kkmonte]

ok....I am a complete noob here. I have always copied/pasted the offsets into MySEQ config and was done. I read the instructions on the new 6.0...and quite frankly dont have a friggin clue on what to do...FML

This is for SEQ (linux version), MySEQ is for windows version. Other part of the forums.

[kkmonte]

I just tried the patch file offsets on my version 5 old laptop and it patched fine, built fine, but does the same seg fault core dump when I zone to detect it.

[cn187]

There was a change to the test server earlier this month that altered one of the structs, and I fixed it there, but forgot about it, so that's sort of my fault. As I said, I was feeling a little rushed.

Interestingly, when I first saw it on test, I also got segfaults immediately, but when I logged in to live this evening, I didn't get segfaults, just some unexpected values in the spawn list. Luck of the draw I guess...

I just committed the fix to SVN. I'm tracking down another issue (related to intermittent map loading), and as soon as I find/fix that I'll cut another release/tarball and post another announcement.

Thanks for your patience.

[kkmonte]

Still not working for me, now I just get:

Warning: Op_ZoneEntry (0x68f8) (dataLen: 92) doesn't match: size of (ClientZoneEntryStruct):88

Seg Fault

[Newby]

BTW, I'm not doing patches for seq anymore. The past few patches, it seems like I was competing (read: racing) with CN to get the fix out and that's not something I'm in to. CN needs to do it so he can work on his other plans for seq, and I'm more than happy to let him do it.

[cn187]

kkmonte - that warning has been there for a while and should be harmless. Everything seems to be working fine here. If you didn't already, can you please do a make clean, and then try building again? If you already did, or that doesn't help, could you please send me a core dump? Before you run showeq, run


ulimit -c unlimited


then run showeq as usual. When it crashes, it should leave a core file in the same directory. If you can send that to me at [email protected], I'll take a look.

[cn187]

Newby, I'm sorry it seemed that way to you - I didn't mean for it to seem like a race. I know early on, I said something about beating you, but that was really in jest, as I was still struggling to figure out how to do certain things and couldn't have beaten you at that point if I tried. The past few releases, I'll admit I've been trying to do them super quickly because I was trying to coordinate the RC releases to be ready at the same time as the 5.x releases. Tonight was the same but moreso since it was the first official 6.x release, and I knew I was going to be out of pocket for a bit tonight, so I wanted to get it done. Now that 6 has been released and 5 is being EOL'd, that should take a lot of the pressure off. Please don't let me and my anal tendencies discourage you from contributing.

[everquestbuddy]

ive never had to post here for years but i take it windows 10 users can no longer copy paste the offsets like its been happening for the last decade ? If no disregard this message

[cn187]

ive never had to post here for years but i take it windows 10 users can no longer copy paste the offsets like its been happening for the last decade ? If no disregard this message

This part of the forum is about ShowEQ. If you're running Windows 10 and using offsets, you want the MySEQ forums further down the page.

[kkmonte]

kkmonte - that warning has been there for a while and should be harmless. Everything seems to be working fine here. If you didn't already, can you please do a make clean, and then try building again? If you already did, or that doesn't help, could you please send me a core dump? Before you run showeq, run


ulimit -c unlimited


then run showeq as usual. When it crashes, it should leave a core file in the same directory. If you can send that to me at [email protected], I'll take a look.

Thanks cn, i just sent my core dump. this is a new linux install that i was getting ready for seq6 so i'm not sure if i missed anything but it appears to make and build fine. I did a make clean, and when i did it again, i think i saw a newer 1140 version whereas before was 1138, but it still crashes on me. Thanks again.

[kkmonte]

ok so making a little bit of progress, i got it to not crash, doing another make clean and remaking and building. so i'm on my new centos 7 machine, using the new seq6 and now it loads the map, and shows my circle, but it doesn't update or show mobs moving at all. and when I zone, i get pages and pages and pages in my console of the warning eqpacket unhandled net opcode messages, then they finally stop and it doesn't seem to update anymore. Is anyone else having that issue?

[cn187]

ok so making a little bit of progress, i got it to not crash, doing another make clean and remaking and building. so i'm on my new centos 7 machine, using the new seq6 and now it loads the map, and shows my circle, but it doesn't update or show mobs moving at all. and when I zone, i get pages and pages and pages in my console of the warning eqpacket unhandled net opcode messages, then they finally stop and it doesn't seem to update anymore. Is anyone else having that issue?

The only opcode warning I get is the one about the OP_ZoneEntry size mismatch (which I should really get around to fixing, but it seems harmless enough at the moment). Based on your description, it sounds like a decoding issue, like zoneopcodes.xml is partially wrong. Can you post (or send me, if you'd prefer) some of the warning messages you're seeing?

[kkmonte]

The only opcode warning I get is the one about the OP_ZoneEntry size mismatch (which I should really get around to fixing, but it seems harmless enough at the moment). Based on your description, it sounds like a decoding issue, like zoneopcodes.xml is partially wrong. Can you post (or send me, if you'd prefer) some of the warning messages you're seeing?

So last night the weird thing was i was having those issues i described in POK, and I zoned into steamfont and qeynos and still the same thing. I went back to field of scale to work on missions and that zone was working perfectly. I was in that zone for 2-3 hours and went to bed. I just logged in today and now everything appears to work in pok and steamfont. Weird, not sure what the problem is but seemed to have gone away. thanks again for the terrific support cn187 and everyone!

[kkmonte]

The only opcode warning I get is the one about the OP_ZoneEntry size mismatch (which I should really get around to fixing, but it seems harmless enough at the moment). Based on your description, it sounds like a decoding issue, like zoneopcodes.xml is partially wrong. Can you post (or send me, if you'd prefer) some of the warning messages you're seeing?

sending you an email with the warning messages i'm seeing, seems to be sporatic as i used it all day and now all of a sudden i'm getting these errors from the text doc i'll email you.

[kkmonte]

Ok just so everyone knows, everything is working good. Per CN187's suggestion, i turned on session tracking and it seems to have done the trick on making it act weird.

[BlueAdept]

Newby, don't feel slighted. There will be times that CN187 misses something or you figure out something that CN187 doesn't or when he is not available. Your contributions ARE greatly appreciated. It is also good to have 2 people that know how to do this stuff. I would really love if you would continue and also your input on direction on things would be appreciated.

I thank both of you for helping with SEQ. You are both needed. I asked him to run the code because of my health issue and I should have seen the conflict that this would have brought but I had other things on my mind. I am sorry for that.