The Myra database:

[Darkwaters]

I'm not the Dev or Admin so I'm not speaking for them in any of my posts or this one. Obviously take a pill and relax. It would be a complete waste of time when item structures etc change, would you like to manually search each line and there are 28731 in just the items table and thats prior to dropping some in the newdumpeditems.sql file which only contains 19881 in the items table. There are 140 fields per each of those lines now thats either 4022340 populated fields or 2783340 populated fields. You would literally have to compare these tables and verify that the data is essential and not dropped due to changes with regards to SOE live code. I really think you need to burn off energy in some other fashion, try reading the packet collection thread. It would be more benefitial to have all the new items added in the proper context than to finally complete an update and find the structure and items have changed yet again.
WOW, I'm not flaming and you can take it as such, nm I'll flame WTF are you smoking???
Darkwaters

[Ace]

Wow, you seem to be somewhat bi polar.

I believe that you are completely missing the point here. Your fallacious logic doesn't seem to be registering the fact that Yes, I would be willing to do this by hand.

Calm down, people your age get heart attacks easily.

[Darkwaters]

Then figure it out I'm not your babysitter nor will I walk you through it at this point. Obviously you don't know enough to do it yourself from what I can see.
Darkwaters

[Melwin]

If one had the structure differences between the two tables, one could write a script to make them compatible with one another.

[Ace]

Then figure it out I'm not your babysitter nor will I walk you through it at this point. Obviously you don't know enough to do it yourself from what I can see.

Darkwaters, you would benefit from the timeless adage of, "Act your age, not your shoe size." There is no reason for you lower yourself to an immature level, as I have been nothing but calm, collected and mature since the beginning of this thread.

I never asked explicitly for your advice, you voluntarily posted in this thread and provided it by yourself. I never asked you to babysit me, nor would I deem you mentally fit to babysit a child. I would appreciate it if you would remove yourself from reducing the legitimacy of this thread with your illiterate vitriol.


Melwin, thank you so much for the constructive response. I expected this was the case, and if my search for a private updated database comes to an end, I will definitely be making one and providing it for the community.

[Darkwaters]

Here's my two cents again to implement the fixes and I'd post the updated items table but SBC homepages is down atm so no where to post the small zip file.

Here Ace,
If you plan on only using MW_57DR2_alpha_1.sql and newdumpeditems.sql and following the tutorial posted elsewhere.
There are 7 unique table fields missing from newdumpeditems.sql's "items" table [unknown004, 070, 076, 077, 099, 107, & 108] add these entries listed in the code snippet below to this table.
There are 30 missing fields in the MW_57DR2_alpha_1.sql's "items_" table [not manually listing them just verify you alter your table properties to match the information below in the code snippet].

# MySQL-Front 3.0  (Build 28.10)

# Items and Items_ updated by Darkwaters
# ------------------------------------------------------
# Server version 4.0.20a-nt

#
# Table structure for table items
#

CREATE TABLE `items` (
  `id` int(11) NOT NULL default '0',
  `minstatus` smallint(5) NOT NULL default '0',
  `Name` varchar(64) NOT NULL default '0',
  `aagi` int(11) NOT NULL default '0',
  `ac` int(11) NOT NULL default '0',
  `accuracy` int(11) NOT NULL default '0',
  `acha` int(11) NOT NULL default '0',
  `adex` int(11) NOT NULL default '0',
  `aint` int(11) NOT NULL default '0',
  `artifactflag` tinyint(3) unsigned NOT NULL default '0',
  `asta` int(11) NOT NULL default '0',
  `astr` int(11) NOT NULL default '0',
  `attackbonus` int(11) NOT NULL default '0',
  `augmentrestriction` int(11) NOT NULL default '0',
  `augslot1type` tinyint(3) NOT NULL default '0',
  `augslot2type` tinyint(3) NOT NULL default '0',
  `augslot3type` tinyint(3) NOT NULL default '0',
  `augslot4type` tinyint(3) NOT NULL default '0',
  `augslot5type` tinyint(3) NOT NULL default '0',
  `augtype` int(11) NOT NULL default '0',
  `avoidance` int(11) NOT NULL default '0',
  `awis` int(11) NOT NULL default '0',
  `bagsize` int(11) NOT NULL default '0',
  `bagslots` int(11) NOT NULL default '0',
  `bagtype` int(11) NOT NULL default '0',
  `bagwr` int(11) NOT NULL default '0',
  `banedmgamt` int(11) NOT NULL default '0',
  `banedmgamt2` int(11) NOT NULL default '0',
  `banedmgbody` int(11) NOT NULL default '0',
  `banedmgrace` int(11) NOT NULL default '0',
  `bardtype` int(11) NOT NULL default '0',
  `bardvalue` int(11) NOT NULL default '0',
  `booktype` int(11) NOT NULL default '0',
  `casttime` int(11) NOT NULL default '0',
  `casttime2` int(11) NOT NULL default '0',
  `charges` int(11) NOT NULL default '0',
  `charmfile` varchar(32) NOT NULL default '0',
  `classes` int(11) NOT NULL default '0',
  `color` int(11) NOT NULL default '0',
  `combateffects` varchar(10) NOT NULL default '0',
  `combatskill` int(11) NOT NULL default '0',
  `combatskilldmg` int(11) NOT NULL default '0',
  `cost` int(11) NOT NULL default '0',
  `cr` int(11) NOT NULL default '0',
  `damage` int(11) NOT NULL default '0',
  `damageshield` int(11) NOT NULL default '0',
  `deity` int(11) NOT NULL default '0',
  `delay` int(11) NOT NULL default '0',
  `dotshielding` int(11) NOT NULL default '0',
  `dr` int(11) NOT NULL default '0',
  `effecttype` int(11) NOT NULL default '0',
  `elemdmgtype` int(11) NOT NULL default '0',
  `elemdmgamt` int(11) NOT NULL default '0',
  `endur` int(11) NOT NULL default '0',
  `factionamt1` int(11) NOT NULL default '0',
  `factionamt2` int(11) NOT NULL default '0',
  `factionamt3` int(11) NOT NULL default '0',
  `factionamt4` int(11) NOT NULL default '0',
  `factionmod1` int(11) NOT NULL default '0',
  `factionmod2` int(11) NOT NULL default '0',
  `factionmod3` int(11) NOT NULL default '0',
  `factionmod4` int(11) NOT NULL default '0',
  `filename` varchar(15) NOT NULL default '0',
  `focusid` int(11) NOT NULL default '0',
  `fr` int(11) NOT NULL default '0',
  `gmflag` int(11) NOT NULL default '0',
  `hastepercent` int(11) NOT NULL default '0',
  `hasteproclvl` int(11) NOT NULL default '0',
  `hp` int(11) NOT NULL default '0',
  `hpregen` int(11) NOT NULL default '0',
  `icon` int(11) NOT NULL default '0',
  `idfile` varchar(30) NOT NULL default '0',
  `itemclass` int(11) NOT NULL default '0',
  `itemtype` int(11) NOT NULL default '0',
  `ldonpointcost` int(11) NOT NULL default '0',
  `ldonpointtheme` int(11) NOT NULL default '0',
  `ldonsold` int(11) NOT NULL default '0',
  `light` int(11) NOT NULL default '0',
  `lore` varchar(80) NOT NULL default '0',
  `loreflag` tinyint(3) unsigned NOT NULL default '0',
  `magic` int(11) NOT NULL default '0',
  `mana` int(11) NOT NULL default '0',
  `manaregen` int(11) NOT NULL default '0',
  `material` int(11) NOT NULL default '0',
  `maxcharges` int(11) NOT NULL default '0',
  `merchantprice` int(11) NOT NULL default '0',
  `mr` int(11) NOT NULL default '0',
  `nodrop` int(11) NOT NULL default '0',
  `norent` int(11) NOT NULL default '0',
  `pendingloreflag` tinyint(3) unsigned NOT NULL default '0',
  `pr` int(11) NOT NULL default '0',
  `proc_rate_mod` int(11) NOT NULL default '0',
  `races` int(11) NOT NULL default '0',
  `range` int(11) NOT NULL default '0',
  `reclevel` int(11) NOT NULL default '0',
  `recskill` int(11) NOT NULL default '0',
  `reqlevel` int(11) NOT NULL default '0',
  `sellrate` float NOT NULL default '0',
  `shielding` int(11) NOT NULL default '0',
  `size` int(11) NOT NULL default '0',
  `skillmodtype` int(11) NOT NULL default '0',
  `skillmodvalue` int(11) NOT NULL default '0',
  `slots` int(11) NOT NULL default '0',
  `spellid` int(11) NOT NULL default '0',
  `spellshield` int(11) NOT NULL default '0',
  `strikethrough` int(11) NOT NULL default '0',
  `stunresist` int(11) NOT NULL default '0',
  `summonedflag` tinyint(3) unsigned NOT NULL default '0',
  `tradeskills` int(11) NOT NULL default '0',
  `tribute` int(11) NOT NULL default '0',
  `weight` int(11) NOT NULL default '0',
  `unknown002` int(11) NOT NULL default '0',
  `unknown003` int(11) NOT NULL default '0',
  `unknown005` int(11) NOT NULL default '0',
  `unknown006` int(11) NOT NULL default '0',
  `unknown007` int(11) NOT NULL default '0',
  `unknown018` int(11) NOT NULL default '0',
  `unknown019` int(11) NOT NULL default '0',
  `unknown020` int(11) NOT NULL default '0',
  `unknown061` int(11) NOT NULL default '0',
  `unknown067` int(11) NOT NULL default '0',
  `unknown069` int(11) NOT NULL default '0',
  `unknown081` int(11) NOT NULL default '0',
  `unknown105` int(11) NOT NULL default '0',
  `unknown122` int(11) NOT NULL default '0',
  `unknown123` varchar(11) NOT NULL default '0',
  `unknown124` varchar(11) NOT NULL default '0',
  `unknown125` varchar(11) NOT NULL default '0',
  `unknown126` varchar(11) NOT NULL default '0',
  `unknown127` varchar(11) NOT NULL default '0',
  `unknown128` varchar(11) NOT NULL default '0',
  `unknown129` varchar(11) NOT NULL default '0',
  `unknown130` varchar(11) NOT NULL default '0',
  `unknown131` varchar(11) NOT NULL default '0',
  `unknown132` varchar(11) NOT NULL default '0',
  `unknown133` varchar(11) NOT NULL default '0',
  `updated` datetime default '2004-06-20 00:00:00',
  `comment` varchar(255) NOT NULL default '0',
  `unknown008` int(10) unsigned NOT NULL default '0',
  `unknown004` int(11) NOT NULL default '0',
  `unknown070` int(11) NOT NULL default '0',
  `unknown076` int(11) NOT NULL default '0',
  `unknown077` int(11) NOT NULL default '0',
  `unknown099` int(11) NOT NULL default '0',
  `unknown107` int(11) NOT NULL default '0',
  `unknown108` int(11) NOT NULL default '0',
  UNIQUE KEY `ID` (`id`)
) TYPE=MyISAM;

After making appropriate changes to both "items" and "items_".
Remove the dupes in the "items_" table compared to "items". This can be done easily enough using the following information in MySQL's SQL Editor Window:

DELETE FROM items_ USING items_, items WHERE items_.id=items.id;

Source the left over original items into "items" the [newdumpeditems.sql's "items"] you'll find you now have 147 table fields for items and 28,810 items in your table. The "items_new" has only 140 table fields and 19,881 items in the table versus "items_orig" which has only 117 table fields yet 28,731 items in the table.

Darkwaters

[Darkwaters]

BTW take that information and apply the general walkthrough or snippets to whatever database it is your trying to use with current EQEmu. It's your time and I was just trying to help until you repetitively asked so why hasn't this been done. As I've stated I don't work as anything but a poster here, but I have many years in IT it just seemed you were being rude asking me again and again why such and such hasn't been implemented when its not mine to say why (like I stated).
Darkwaters

[Ace]

Ah, good show Darkwaters, nicely played.

I understood your position as a poster, and I was simply asking for your opinion as an experienced EQEMu user.

Do you mean that you've updated the table already? If you can get it up, or need a host, give me a shout.

As it stands, great work, and as it's quite a bit later than I expected to stay up, I will absorb this tomorrow. If I can get it into an updated database, would you be against me using the information you have added to provide the community with this database? I'm sure we could all benefit from a fully updated database; at least until the new client comes out.

Thanks again for rising above and beyond what I expected from anyone posting.

[sotonin]

uhm.. did i somehow get lost here, but wasn't the actual question how to get the myra's database compatible.... not the items table.

if thats all he wanted i could of supplied him with a zip containing old and new items dumped into a single current emu compatibile table....

[Darkwaters]

I have created a group on MSN groups called "Darkwaters" go there and download just my version of the Items.sql in zip format this file contains only the Merged version of MW_57DR2_alpha_1 and newdumpeditems the only difference is using the added items not from newdumpeditems means you are not getting the 30 fields of populated data related to the new table. It does make them available on you character and usable as far as their flagged data is concerned, again until the db is populated with all the items from a packetcollector point of view the merged data is not as accurate and will need to be replaced later.
*As Is and I'm not going to be responsible for it. I will however help whatever db team needs it if they'd like older db's merged with newer ones, that is DB Admin's could send me the DB's they wish merged I will do this to help the community.

http://groups.msn.com/Darkwaters

Darkwaters

[sotonin]

if you want the most complete items table available just download my merged version of olddump and new dump.

http://www.peqserver.com

allitems.zip or whatnot. gotta register to download

[Darkwaters]

Sotonin,
It is what he asked but since I did not have that data I was showing him how to do it himself. I was using items as an example but I appreciate the offer for the allitems.zip.

I'd like to find NPC's that are actually spawned to the proper locations using NPC data from govtcheese4 or 5 I still end up with unpopulated zones (Gukta primarily a few others I do not recall atm) and most locations all spawned NPC's end up in a huge rugby pile in one location of the zone. If I had that fixed I'd be really happy.
Darkwaters

[Darkwaters]

If there is a location that says this is what we have and do not have in the most up to date db, I'd go out and work on what we do not have.
Darkwaters

EDIT: Sotonin is there a way to get as much data is available but not released I'll take a shot at comparing the databases and working with the Myra versus what is posted thusfar with MW_57DR2_alpha_1 plus added sql's. Hell I'll take anybody's idea at this point and put the effort to make it compatable with 57DR6 if someone would be kind enough to give me what they have and feel used to be fairly complete.
Darkwaters

[Ace]

In reply to Sotonin, just to get remove all confusion, what I'm looking for is a database compatible with one of the most recent CVS releases that has boss mobs like CT, Xeg, PoFire bosses, Vex Thal, etc populated and working. I believe Myra's database has these things, but it's no longer updated. I plan to take the time to create this database (if it ends up that one doesn't exist).

[sotonin]

Basically. the current release is admittedly far from complete. but that's all there is for now.

I know Ace exactly what you want, thats why i was confused as hell what darkwaters was doing with the items table for you.

We are working hard here to insure all future releases will be very complete, to the point of pullnig my hair out with collecting every night =p and recollecting bad collects.

I can't help at all with myra's it has not been updated for as long as ive been in the project. nobody makes databases anymore except for projecteq. Feel free to do it yourself manually. Although it would be in vain because we'd release our exact to live db's in time.

But when we get around to luclin. (about to start on kunark now. by start on i mean source in all the zones, we've got all through velious already collected with enough logs, and most of luclin and pop)

Our process is we source it in to our test server.. people play it for a while, we remove bad items from vendors, we tweak zones, recollect zones where needed, then fix faction. Then we release that as it is, and source in the next expansion. and so forth.