EQ2Emulator ServerPack

[Cynnar]

This server pack is not being updated at this time
I have very little time to put into updating the server pack, and have chosen to end the updates as a result.
Support will also be limited or lacking due to lack of updates, and limited time to help.
I may resume progress at a later date if RL will allow, but for now head over to the SVN for source and binaries

Live client is not suppoted. Please use a backup copy of CoE or look for the DoV box set.]

This ServerPack is an updated version of John's ServerPack Release. Thanks John for getting this together in the beginning.

What's Included?

• EQ2LoginServer (minilogin) v1.04
  EQ2Emulator Release 0.7.3-dev with World server (32-bit and 64-bit* binaries for Windows)
  EQ2Emulator Database Milestone 2 including current LUA Scripts (ongoing development)

What's New?

• built from latest source (12/15/2016)
  Has mass world pop dabase

EQ2Emulator ServerPack 1.8 Release

EQ2Emulator ServerPack 1.8

Bugs and Support
Ony Questions about the server pack should go here.
All other questions should go to their respective forums.

[Cynnar]

eq2ls database and eq2world database have been merged together into the eq2world database. This merger eliminates the following duplicate tables.

• appearance
  bugs*
  opcodes
  visual_states
  zones

All of these tables are identical except the bugs* table. I used the bugs table from the world server database. In fact I used every duplicate table from the world server database. Started the server and was able to login to both login server and world server just fine.

This now eliminates having to update opcodes in the eq2ls database after running the database patcher on the world server. Once world server gets done updating the opcodes your login server will be ready to go.

If you would prefer to use the old eq2ls database for your login server you can find a eq2ls-current.sql in the database folder. You will then have to edit the login_db.ini file located in the loginserver folder and change database=eq2world to database=eq2ls before the login server will use the old eq2ls database.

[Chrisworld]

Really wish I would have caught this post sooner. I am on client 12284 now.

[Cynnar]

Really wish I would have caught this post sooner. I am on client 12284 now.

I will look into updating the latest client. Hopefully I can get the client after the Tuesday patch as well.
Connect to the db patcher to get the latest opcodes to allow 12284L to connect to your server.

[Chrisworld]

Sorry, I haven't been able to find the time lately to get this set up so I apologize if I missed it.

Is there any place I can look up a complete list of assets (furniture, objects, npc ) etc. to spawn in the world? I remember on an older version I had a list and was able to basically spawn anything in the entire game I wanted. My idea was to create an awesome setup like a guildhall or house anywhere, using all the resources available.

[Jabantiz]

Is there any place I can look up a complete list of assets (furniture, objects, npc ) etc. to spawn in the world?

The appearances table in the DB is all the models ID's you can use with /spawn to spawn whatever you want. That table should contain everything up to the last expansion, no one has worked on the new expansion yet as far as I know.

[Chrisworld]

Really wish I would have caught this post sooner. I am on client 12284 now.

I will look into updating the latest client. Hopefully I can get the client after the Tuesday patch as well.
Connect to the db patcher to get the latest opcodes to allow 12284L to connect to your server.

Well I followed the guide to download the latest OP codes, but my client still throws the mismatched version error when I try to log in. I think it's updated a little beyond 12284 now but I have a backup copy of the version I'm trying to use now so I won't be able to lose this particular version.

I believe it's 12377L

I will hold on to it incase the opcodes get updated for this version.

[Jalister]

It's frustrating when I miss getting the correct version by one day.
It looks like a small patch. I don't know how often the opcodes change, but is there a chance the opcodes are the same, and the allowed version is all that needs to be changed.

[Cynnar]

It's frustrating when I miss getting the correct version by one day.
It looks like a small patch. I don't know how often the opcodes change, but is there a chance the opcodes are the same, and the allowed version is all that needs to be changed.

I was able to check opcodes on the client after Tuesday's patch. It was just a version bump. I have sent the info to Jab so he can get the changes pushed to the server. Then you can connect with the db patcher to grab them.

If you cannot wait you can change the version_range2 from 60160 to 60162 in the opcodes table. Then you will be able to connect. I must warn that structs are off and some things don't work, and there is random crashes.

[Jalister]

I was able to check opcodes on the client after Tuesday's patch. It was just a version bump. I have sent the info to Jab so he can get the changes pushed to the server. Then you can connect with the db patcher to grab them.

If you cannot wait you can change the version_range2 from 60160 to 60162 in the opcodes table. Then you will be able to connect. I must warn that structs are off and some things don't work, and there is random crashes.

Thanks for the reply. It's been a long, long time since I ran the emulator. I would really like to get it up and running again.

Will the structs be updated when the opcodes are updated?
I read the docs on how to update the opcodes and structs, will it be mentioned if/when that happens?

[Cynnar]

Will the structs be updated when the opcodes are updated?
I read the docs on how to update the opcodes and structs, will it be mentioned if/when that happens?

The structs are updated separately than opcodes because on every patch the opcodes will require at least a version change, and structs do not always change with a patch. Unfortunately the patch that took place a few weeks ago had some packet structure changes. Add that on top of the fact that structs past the CoT clients are very incomplete means structs needs some work. Jab is our man on structs, and I am starting to learn them, and structs are low priority right now.

Oh and Jab correct anything if I got it incorrect.

As for mentioning the there is updates I will add to the main post when opcodes are up on db patcher, and when new structs, and exe's are ready I will post a update.zip with just the necessary files so the server pack does not have to be redownloaded every time.

[Jalister]

The structs are updated separately than opcodes because on every patch the opcodes will require at least a version change, and structs do not always change with a patch. Unfortunately the patch that took place a few weeks ago had some packet structure changes. Add that on top of the fact that structs past the CoT clients are very incomplete means structs needs some work. Jab is our man on structs, and I am starting to learn them, and structs are low priority right now.

Oh and Jab correct anything if o got it wrong.

As for mentioning the there is updates I will add to the main post when opcodes are up on db patcher, and when new structs, and exe's are ready I will post a update.zip with just the necessary files so the server pack does not have to be redownloaded every time.

Thanks to those involved with this project. Hopefully I will get re-familiar with it all again.

I also wonder if there was another small patch. When I try to connect to my server, LoginServer reports bad version 60173.
I've also tried looking at the opcodes table using MySQL Workbench. I don't see any value there with anything close to these values. I'm still poking around though.

I have all the box versions, I think. Is there a better version to run than the live version?

[Cynnar]

Thanks to those involved with this project. Hopefully I will get re-familiar with it all again.

I also wonder if there was another small patch. When I try to connect to my server, LoginServer reports bad version 60173.
I've also tried looking at the opcodes table using MySQL Workbench. I don't see any value there with anything close to these values. I'm still poking around though.

I have all the box versions, I think. Is there a better version to run than the live version?

I believe so the last version I worked on was 60162. You can try changing the version_range2 to 60173 and see if you can log on.

You might try hediSQL. That is what I use, and it's free.

As for boxed versions the only one that really has any kind of support at all is DoV, and it will not work well with those revamped zones.

[Jalister]

I believe so the last version I worked on was 60162. You can try changing the version_range2 to 60173 and see if you can log on.

You might try hediSQL. That is what I use, and it's free.

As for boxed versions the only one that really has any kind of support at all is DoV, and it will not work well with those revamped zones.

Sounds like I will stick with getting Live working then.

I was able to find the data with HeidiSQL, after I selected to load all rows. Thanks for the tip on HeidiSQL, it seems easier to use.

Changing version_range2 only still gave me a version error. When I also changed version_range1 to 60173, I was able to connect, login, and load the admin character.

I'm not able to create any characters though. All races are greyed out with the DB logo by each one. Is that how it is right now, or is that an opcode issue? I also get am not receiving the third quest when I click accept. Still, it's cool to see this so far.

[Cynnar]

Sounds like I will stick with getting Live working then.

I was able to find the data with HeidiSQL, after I selected to load all rows. Thanks for the tip on HeidiSQL, it seems easier to use.

Changing version_range2 only still gave me a version error. When I also changed version_range1 to 60173, I was able to connect, login, and load the admin character.

I'm not able to create any characters though. All races are greyed out with the DB logo by each one. Is that how it is right now, or is that an opcode issue? I also get am not receiving the third quest when I click accept. Still, it's cool to see this so far.

They are not suppose to be greyed out. Try restarting both minilogin and world. If that does not work then Jab will have to jump in and tell us what is wrong.