2018. Project1999 ShowEQ Status

[mamapete]

Thank you for all your work Slippery. I had a quick question as I am getting traffic but it does seem like the offsets are correct as I am getting garbled data. I was going to reload everything and try again just to see if it was my screw up following the guide. I didn't know if something server side was changed that might require new offsets. Thanks again for all the work and assistance.

Further code changes are required to get SEQ working. What you see is a result of the encryption that was implemented. Search for another post with details on this change.

[slippery_slope]

Final part of my series here getting ShowEQ working. Thanks again BlueAdept.

https://medium.com/@Packet99/decrypt...s-7248acb1797b

[BlueAdept]

That was a great write up. I actually learned quite a bit from it. I wish I had the time to learn more about it. I never did learn about the op codes. I could do the struct changes in the past. It was pretty easy to do a dump and see the changes.

So the key is only introduced when you log on and doesn't change when you zone? For a little while, Sony had added something similar to EQ except when you zoned, it gave a new key. They used to have to decrypt it and then backfill the spawns in SEQ. The issue for EQ was that it was causing some additional lag along with some other issues and then during one patch, they just got rid of the whole thing. I believe that was during luclin era.

I would welcome any guides or tips you can do. It seems you have a pretty in depth knowledge of how SEQ works and of the EQ packets.

I do have a lot of questions for you, but most of them are more curiosity than substance. I am going to start a new thread with some questions for the whole SEQ community regarding its future. Have a look and see if any of it peaks an interest.

[slippery_slope]

The key is sent whenever you receive a OP_SendLoginInfo packet. These packets happen on first log in, but also when you zone. I've seen the key change sometimes too, but generally it's the same for an entire session.

Interesting you mention the other encryption, I did see references to a decode key in the ShowEQ code base, however I couldn't figure out where it was used. Makes sense if the functionality was removed.

Feel free to PM me any other curiosities

[BlueAdept]

Unfortunately I dont have the libeq.a files from back then nor do I have the source for the libeq.cpp for the decryption back then. I did not have that kind of access back then. The SVN should have source from that era, but the decryption routines were pulled out.

[charlie.darwin]

Final part of my series here getting ShowEQ working. Thanks again BlueAdept.

https://medium.com/@Packet99/decrypt...s-7248acb1797b

Damn, thought at the end of the article I'd have the details on how to get this working.... Kinda disappointing since I'm not a code writer to find a tease....

[BlueAdept]

The last time people got it working with p99, they kept changing it since they really didn't want people using SEQ with it. Slippery_Slope wasn't sure he wanted to share the fix at all since the last time they kept breaking it until they abandoned the project. We both came up with a solution of a guide, without giving the exact fix, with enough information to get it working if a person really wanted it. I think he did a wonderful job of explaining it and, with a bit of work and a bit of coding, I think almost anyone could get it working.

He didn't have to do anything for anyone, but he wrote an outstanding article about it to help those who help themselves. I am sure p99 noticed this thread and, as far as I know, have not elected to change the encryption even after this was published.