First!

Image, naturally I have a problem getting Minilogin to work. If I source in your supplied database, and set up way more configuration than is in your Readme (grin), I can get EQ2MiniLogin.exe to run on localhost (127.0.0.1) just fine. I have hack apart my EQ2World's LoginServer.ini to get it to work at all, but I finally got my world to connect to the LoginServer (1 World, 0 Clients in Minilogin's cmd window).

Originally, when I would connect my client, I got the invalid version 939. I guess you didn't update the opcodes to run with the most current SVN. So I tried dropping my EQ2World (and struct xmls) back to 0.6 release, for both World and Minilogin, but that too did not work.

My last effort was to update the structs for both Minilogin and World to the latest SVN, and source (copy) the opcodes table from my live server to both Minilogin and my World databases... now, Minilogin starts, World connects, and when the client attempts to connect, I crash the client and I am unable to connect. I noticed a lot of tables in eq2logindb.sql are empty. When I create a character (male / barbarian), after the crashed login attempt, he is a 0,0,0 colored female Erudite everytime. I even tried sourcing in all the appearances, visual states, zones, and other missing data to no avail.

While I am very happy with the release, I think a TON more documentation needs to be supplied, which I will be happy to write once I figure out all the mysteries to getting Minilogin working perfectly. It is not a simple unzip/run/magic, that is for sure.

Any additional advice on getting this set up? Thanks again for Minilogin!


Edit: Just found this in the log_message table, not sure if it tells you what's crashing:

Please try not using 127.0.0.1 if you are using that for the login server. You will need to use your LAN ip address at the very least, EQ2 does not like localhost/127.0.0.1

Also you would be probably better off just adding the tables that don't already exist in your world server.

I did not expect this release to be easy since I did not have anyone to test it

I would hope eventually LE would automatically send the tables on the auto updater in some fashion.

Oops, ok. I won't use localhost then. Thanks for the heads up. I will try this again when I get back from holiday with the folks, and I'll let y'all know how it turns out.

I'm getting version 939 errors also and I'm using LAN IPs and Domain Names, no luck.

Well first, for the incorrect version errors, you need to just use the opcodes that your world server uses, or just set them manually in MySQL.

Eg.

update opcodes set version_range1=0,version_range2=940;

(version_range1 = min, version_range2 = max).

But I highly suggest using the opcodes table from LE.

As for the other errors I will gladly help you with them; just let me know.

John Adams wrote:My last effort was to update the structs for both Minilogin and World to the latest SVN, and source (copy) the opcodes table from my live server to both Minilogin and my World databases... now, Minilogin starts, World connects, and when the client attempts to connect, I crash the client and I am unable to connect.

That's a no. Doesn't work either. Now that I am back home, I will start more testing this week. I'd like to get this ironed out, if anyone else has been able to get it to work. Of course it works perfectly for the guy who wrote it.

Okay so the December 2nd client doesn't work as the OPCodes are incorrect with what the Minilogin has. Technically you should use LE's update tables for the OPCodes, then copy the OPCodes from your EQ2Emu Server to the MiniLogin, I'm going to try that next.

I just tested with 5280L and I am not having any crash issues... Can you guys put up your alertlog.txt or eq2_crash.txt whatever is available.

Note that there are two versions of the 939 client. The opcodes are for the original 939 only. Basically, SOE screwed up. They didn't update the version number properly when they changed opcodes, so even if you have the 939 client it might still crash on logging into the World.

Ah you are crashing into the world server, thought you mean't the login server... Shouldn't have anything to do with the LS

Looks like a compression issue... unfortunately I don't get a eq2_crash log with it

5016L works for me all the way into the game, not sure if we really support the Dec 2nd patch.

I am using 5280L, which is the Dec 2 client and I believe the original 939 data structures (before the mess-up on the 9th/10th). I will fiddle with this more today, but the client that connects to EQ2World.exe just fine does not do so using EQ2Minilogin.exe as my login server, and that is using 3 different sets of opcodes - 1) that came with the minilogin DB, 2) from LE's loginserver data, and 3) sourcing whatever is shipped via 9102 updates to my public Emu. I did post the log entry from the minilogin's log table, if that's what you are looking for. See above.

I no longer have a copy of 5016L (unless that is tSO box?) as I thought we moved beyond that client entirely as a project. Isn't it a matter of opcodes/struct files that keeps the compatibility going? If not, we should consider making that the case, because the public LS is going to change. Copying xml's and opcodes tables to the Minilogin setup would be the best option.

I don't see how this can be an issue with the Login Server, the eq2 client disconnects with the LS long before this crash occurs; the crash seems to occur somewhere between loading entities...

From my alert log:
build="SOEBuild=5280L" version="SOEVersionString=2008/12/2 16:02:18" build_type="USER OPTIMIZED" ls_address="none" zone="tutorial_island02" loc="-17.24 -5.40 223.20" performance="7" alert="E:\live\eq2\game\gamecommon\client\CompressedXOR.cpp(243): Bogus compressed data. This is normally caused by mismatched client and server."