MW_057DR2_alpha_1 RELEASED!!
 

you wanted it, well it's up and out. head to www.projecteq.net and grab it from the downloads section!

DB has some incomplete info. ie merchants, base factions, etc

Description: new collected database, with pathing(149 zones) you will need to change EMUsharemem/NPCTypes.h from 200000 to 400000 and recompile it. if you do not parts of the database will not work..

like what it has? please go to www.projecteq.net/logdump to see how you can assist with filling the other zones.

*Bows to the powers that be*
Thank you, thank you! Going to get it now to try it out )

Awesome job, like always.
Thanks.

Great work guys, I can't wait to try it out...now if I can just get some free time!

I just confirmed with TCS that the 2 updates I wrote (loot and faction) were included in this release, so you do NOT need to source them.

im looking through the commands to see if there is a way to update the lines. wich will overwrite whats already in the database.

But i cant seem to find a mysql command to do this if you know how or the command to take the old alpha stuff out please let me know thanx :)

create a new db.. then change the db you have listed in db.ini to the new one.

I HIGHLY advise correcting your .sql file with the below fixes and resourcing the sql.

FYI, when I sourced I got he following output:

To fix these errors, you have to change the following lines:

Delete (in inventory table):

and replace with:

Delete (in items table):

and replace with:

Delete (in sharedbank table):

and replace with:

Not sure if these errors were causing the inventory stuff before, but no more errors when sourcing :)

I fixed those errors and uploaded the repaired version.
For some reason when I dump the DB info with MySql-Front it puts the Unique and Key fields into seperate lines.

*Note to self- check these on every dump* :)

Hope you all enjoy the new DB.
As always , a BIG THANKS to the Team , and our group of collectors for a Job Well Done :)

For some reason Potimeb only has 2 mobs in it and Sleeper is completely empty, these zones were populated in the previous releases.

this is a new db, with only collected data.. more people collect the more zones that will be populated

Thanks a bunch EQEMU dev team!! Woot this is so fuxxoring awesome man, i remember back in 4.4 when it was a wee baby.

Now!! Its 5.7 DR2 !! Holy dont make me say it!

I run a server that uses the MW55 alpha 1 and 2 db. I checked this db out on another one of my boxes and think its wonderfully done. I would really love to update my server to use this db instead of the ones I have been using, but the thing is I have put alot of work into the MW55 db, ie adding/changing loot and mobs. So to get to my question....I know there must be a way from me to grab that info from my old database, but I havent a clue how. :? So if anyone could clue me in on how to transfer my tweaked mobs and loot from my old db to this new one I'd be extremely grateful:D

-astro

Sorry to say, AstroKitten, but the new release is a completely new DB, meaning all npcID's have changed.
The only way to get your custom info into it, will be to re-add them by hand.
We are working on getting a complete collected DB together, including all mechants and pathing for all zones.

In your new database is there anything else to source other then the tables.sql that is listed on projecteq.net and your new file?

In the cvs I see tons of sql files, are those not needed?

Our Releases generally are complete DB's with ALL fixes/updates added.
Should only need to source the sql from the D/L and, if there are any updates after release, the update sql/s that are listed with the release.
No other sql's needed.

Ok, so just for clarification the dumps that edgar is doing has nothing to do with your db and shouldnt be sourced in? I am good with code however database stuff is rather new to me and am trying to get the hang of it without screwing things up.

Thanks for this release(even though I havent used it yet) and your previous releases + everyone that has contributed it makes for an awesome eqemu experiance.

Thanks for clueing me in that its not possible to do with this db. Least now I won't be ripping my hair out trying to figure out how to do it :lol:

I am slowly but surely taking all the quests that were in the old Perl_quests.zip and renaming them to the spawnid's used in this DB. I have a couple of zones done. Some zones of course there is I can't match any NPC names obviously zones no one has submitted yet like there are no npc's that spawn in airplane in this DB so i am skipping that zone since i don't know what the ID's will be.

Right now i have the West Freeport done and the akanon almost finished. Of course within these zones there are several NPC's missing that I have the quests for.

Was pretty much just doing it for myself. but once i get a little furthur along i'll prolly throw them up on some webspace as i get zones done if people are interested enough in them.

I think you have 2 maybe 3 zones mixed up as far as spawns in the DB.

erudsxing
erudnint
erudnext


erudnint is the palace you have no spawns for that zone so that may be correct

erudnext is erudin itself but it seems to contain the spawns for erudsxing

erudsxing seems to have the spawns for erudnext, when i zone to erudin there are no spawns.. one time i zoned in and got put in the "box" and all the NPC's were stacked on top of each other in the box.

when i zone into erudsxing which is also known as willowwisp island i can see all the npc's far off in the distance up in the air over the water.

I started looking on allakhazams and sure enough the spawns you have in erudsxing belong in erudnext and vice versa not sure if you have any of the palace spawns thrown in there yet..

Only figured it out cause i was redoing the quests in erudnext but the spawnid's for what zone they were in kept coming up in erudsxing.

Not sure what the easiest way is to fix the database itself is, but i am going to verify the zones the NPC's are supposed to be in that i have quests for and leave them in that zones quest folder.

We are aware of the problem with Erudin, it was a problem with the conversion tool, should be fixed in next release.

is the problem that guildmasters arent training a db issue or server code issue?

Looking at the NPC tables if i had to guess it looks like the class column is set to 0 for the guildmasters. I am pretty sure each class of guildmaster has a unique class number to tells the client its a trainer.

I'm going to experiment with that sometime today

GM Trainers are working as of the 5/20/04 CVS.

does anything have to be sourced into the database? I am running the 5/20/04 code but didnt see any sql updates. So the trainers were server code related in this instance?

it appears so, i didn't change anything in my database regarding them and they are working fine now.

Cool, thanks much

After doing some testing from what I can see it has to be the database, I am running 5-20-04 and when I use my older database the trainers work fine, when I turn the new database back on(which I have made 3 seperate ones to make sure I didnt mess up) the trainers dont work. I switch back to my old one and they work again. Any thoughts?

Also, when switching to the new database did you just drop your old one(create a new one) or just source the MW57DR2 over your old database?

Actually I am using the old database. mw055alpha1 and alpha2. But it is custom, all the NPC's are custom.

You need to create a new one. You can then copy over your player's data and it will work as intended. Sourcing any DB over another will cause problems and is a Very Bad Thing <tm>.

Hmm, I sourced in mw055_alpha1, then sourced in mw055_alpha2, then sourced in MW_057DR2_alpha_1 and the database is fine, haven't found any issues at all.

Ok, I didnt source the other 2 just the 5.7dr2_alpha1 and the tables. I will try it with the other 2 in there, thanks again Jez.

I dont know what I am doing wrong, but I get errors even on the first 2 databases. I create a whole new database, source 55alpha1 in fine, no errors. I source in 55alpha02 and I get lots of duplicate entry errors. And of course that means I get lots of duplicate entry errors sourcing in 57dr2. What am I doing wrong? Is there a command line I am missing? I am just typing use eq then source [filename.sql] once thats done I am typing source [next filename.sql]

thats normal when you source databases over each other.

57dr2a CANNOT be done over another DB.. it has a whole new npc setup. you will end up[ with dup mobs missing mobs and god knows how many other errors..

granted there might be a couple bugs in it, we were under the gun getting it out. the next release will be functioning better

Ya. sourcing the 55 alpha1 + alpha2 together in itself is HORRID.

if you do this and go to a eastern wastes for example, (this zone was bad in my experiences) you will see every orc at the orc fort has TWO orcs in its spawn points....

It creates serious problems to source those 2 together.