Hey everyone. I went and unpacked a fresh copy of 6710L, downpatched it to 6118L and set it to connect to the eq2emulator servers. So far I've been able to log in and run around, interact, etc....

For some reason though I still don't have any 'maps'. Well, I mean they "work" but there is no background, they're all black. I went and looked in my directory and saw that I was using eq2map from whenever this client was (title is Halas Reborn, originally version 6710 at time of packing into 7zip archive). So what I did was I deleted EQ2MAP and redirected the eq2.ini file to point to Default, yet I still don't have any map backgrounds.

Once I can get this resolved, my game client should be a 100% perfect match for eq2emu as it stands now.

Hmm, I usually run EQ2Maps updater for any client I run, and my maps work for every game UI that it recognizes (some are No Map, but never black) - so maybe it's that you cannot back-patch that far? 6700-6118L is a pretty large jump. Did you try the 6563L client? I know it's not fully supported, but you should be able to get into the game.

I think Xinux once extracted the proper maps for our clients. The problem is likely the Halas Reborn UI is different enough where the files don't line up anymore.

The issue i think is going to be your UI folder give me a few i'm currently reinstalling my SF and TSO client and i'll zip up and host my UI folder and see if that fixes it for you.

Here is the UI folder for 6118L give it a try just rename your old UI folder first just incase.

PM'ed you

Appreciate the PM Xin, I used that UI folder but my maps are still showing up black. John is most likely right, too far backpatched. Why oh why does it have to be something. I really wish I had 6118 when it was live and archived that one. But I'm still glad to have a working one even if it's 6710. I've been using 6710 backpatched to 6118 for a LONG, LONG time on the Server Pack 1.2 and since then been messing with stuff trying to learn about the server and trying to learn to fool with SQL, but I can't for the life of me figure out how to make SQL even work right (like not timeout when adding an SQL file to a DB)... sigh. It's the small things that keep me away from the project that people know as second nature.

Was hopeing it was a easy fix could be a issue with the pak files or something really easy do me a favor and post up the following for me you should have a alertlog and a ui text document in your main folder. You can also log in and camp out and arrange your files by date modified.

I might have found something, here have a look at what ui.log has to say:

Shoot me a pm on where you got the client from.

Chrisworld wrote:I can't for the life of me figure out how to make SQL even work right (like not timeout when adding an SQL file to a DB)... sigh.

Most likely your problem is that stock MySQL comes with a default max_packet_size of 16mb. You should jack that up to 200MB or even 1GB if you have the RAM, and are importing datasets like ours, which are exported using "Bulk Inserts".

Bulk Inserts basically sents 1 single Insert Into command, followed by a very large string of VALUES (...) instead of insert values, insert values, insert values on every line (makes the SQL file huge). Bulk inserts are very fast, but memory hogs.

MySQL 16M packet size is an anti-hack method, but if it's your own private DB at home, no one's gonna hack you. Jack that sucker open to 200-500MB if you like. That should stop "MySQL from going away..."