The moment you've been waiting for. After spending 18 mos working on content, building functionality into our World to support spawns, items, scripts, quests and more, the EQ2Emulator Database Project is finally going to release an ALPHA version of our database and scripts.
Unfortunately, the release method is not exactly what we had hoped for. Below you will find 2 links; one to the DB, one to the LUA Scripts. It had to be done this way because the data is just too big to shove through our auto-updater. We're building a new public SVN to provide you with real-time updates to our data, but that is proving to take longer than expected - and after our poll, we realized getting data into your hands sooner was more important.
What you will find in this data is the first 10 levels of content (same data you found on TessEQ2), starting with newbie areas out to the T1 zones surrounding the cities. This might not seem like a lot of content, but rest assured it took almost 2 years in planning and providing support in the code just to pull this stuff off and make it emulate EQ2 Live as closely as possible.
There will be problems with the data!
We already know it's not perfect, and do not really need anymore feedback on that - since we still have over 50 bugs we have yet to investigate. This is an effort on our part to give you, the community, some data in the hopes of fostering some development interest in EQ2Emulator. We simply cannot survive with 1-2 developers and expect to keep making notable progress.With that, here is your Database and LUA scripts - ALPHA version!
Database
Scripts
Instructions (please follow these very closely):
- 1. Make a new, empty database in MySQL (call it `eq2` or whatever you like),
2. Unzip the eq2db SQL file and source it into that new MySQL DB- Make sure whatever MySQL account you use to run your eq2world has access to that new DB
Also, make sure your max_packet_size in your MySQL config is large (100MB or more) since the queries are very large (thank you abndrew82 for pointing this out!)
- Make sure whatever MySQL account you use to run your eq2world has access to that new DB
Technical Crap:
The `table_versions` table is stamped with today's data versions, so any structural database changes we make after this should be updated properly during the continued development cycle. This is why you must make a new DB, source the SQL in, then connect your new World to EQ2Emulator.net, in that order. Do not let EQ2World.exe build the database for you, unless you do not plan to use this DB Release or you risk being out of sync with the dev team's data.
Future Database Releases and Availability:
We're all pretty swamped right now, so we did not have time to properly setup a new SVN for EQ2Emulator + Data - but that is coming soon as we get a little more time. This post is merely a work-around to get this data to you sooner, and we'll work on the new SVN for the 0.7.0 release and beyond.
With the Sentinel's Fate expansion released, our team has decided to release this data, let you play with it, while we nuke our entire DB and start over - with SF functionality. We won't need to rebuild everything, so it should be much quicker til our next DB release (via SVN).
Also note, there may be another ServerPack released to include this data, again if I can find the time to get it done soon.
Special Thanks:
I really want to emphasize how much work was done by the Content Team to bring this data to a usable state. Nearly 90% of the content you see when you log in is the work of Scatman, who not only wrote nearly every spawn and quest script himself, but built C++ code to support most of the quest features (with the help of LE of course).
Our Spells data was provided by me, but all the functionality getting spells LUA Scripts to work properly was all done by Zcoretri.
Our Items data was collected for us by Bion (Bersus) who is no longer with us but without that effort, we never would have had 1/10th these items to play with.
We've had many community members step up to collect data and help build content through the last 2 years as well. There are many other names that could be mentioned, but these 3 guys were the core of our content team for the longest stretch. I'd be lost without them
Enjoy, and post your questions here or in a support forum.
