The one that includes Desert of Flames, Kingdom of Sky, and Echoes of Faydwer, and just patch up to the appropriate version, or will I have to get Shadow Odyssey? If it does work, how would I go about patching it to the right version?

It should work without having to do any patching.

ROK and TSO. That's it.

John Adams wrote:ROK and TSO. That's it.

Just to clarify John's answer, RoK and TSO are the only boxed sets that work without having to patch.
Hope that makes it more clear.

Karoko wrote:The one that includes Desert of Flames, Kingdom of Sky, and Echoes of Faydwer, and just patch up to the appropriate version, or will I have to get Shadow Odyssey? If it does work, how would I go about patching it to the right version?

I purchased this and then used an "eq2emu patcher" i found in the 3rd party tools forum to patch my client version

Sony recently came out with EverQuest II: The Complete Collection box set. This is basically all expansions/adventure packs plus Game Updates 51 and 52. Since we supported game update 52, there is a good chance this box set would work as well, however we haven't tested it out specifically.

I already have a working client, but I thought I would try the EQ2 Complete Collection since I have it. When I try to login I get the message "Login rejected: The client's version does not match the server's. Please re-run the patcher."

The SOEBuild is 5848.

I'm not sure if this client is close enough to a working one or not. If it is, maybe it can be allowed to access the login server?

EDIT: This is a clean installation, no updates were applied.

Well, that version is below our maximum allowed version so it shouldn't be too hard to add. Any chance you could do this LE?

If memory serves, it's not the client version that is the problem. It's the opcode versions. If that particular client version had a data version we do not yet have (which seems likely the case), then no, we cannot go back in time and collect data for it from SOE to verify the data structures.

However, if it's simply a bump to an existing range with only a couple changes, we just widen the range of one of the closest opcode ranges and see if it works. You can test this on your own Minilogin server, or wait for LE to get back from holiday to try it. I agree it would be nice to support this box set, too.

ZexisStryfe wrote:Well, that version is below our maximum allowed version so it shouldn't be too hard to add. Any chance you could do this LE?

We could probably get it working. What is the data version? IE 996

Jalister wrote:...
The SOEBuild is 5848.

Can you tell me what the date of your EverQuest2.exe file is?

LethalEncounter wrote:We could probably get it working. What is the data version? IE 996

I'm not sure what you mean by this.

This is the title bar of my client window...
"EverQuest II (Aug 26 2009 23:19:57) USER OPTIMIZED: SOEBuild=5848

And the file properties for EverQuest2.exe
14,612KB 8/27/2009 8:20 AM

Let me know if you need anything else.

Jalister wrote:

LethalEncounter wrote:We could probably get it working. What is the data version? IE 996

I'm not sure what you mean by this.

This is the title bar of my client window...
"EverQuest II (Aug 26 2009 23:19:57) USER OPTIMIZED: SOEBuild=5848

And the file properties for EverQuest2.exe
14,612KB 8/27/2009 8:20 AM

Let me know if you need anything else.

With that date, the data version should be 987, but need to determine which 987 version haha

EDIT: looks like its the 987 version where we don't have to mess with the opcodes
refer to this post here http://www.eq2emulator.net/phpBB3/viewt ... 671#p15671

Zcoretri wrote: EDIT: looks like its the 987 version where we don't have to mess with the opcodes
refer to this post here http://www.eq2emulator.net/phpBB3/viewt ... 671#p15671

Is this something I can check for you? Or is it just something we gotta try?

I think Lethal has to allow that client into the login server. Then you can test your client