Collector Ran Fine. Question on structure.

[Zewt]

I ran the packet collector last night and it worked perfectly, I even took a stroll through the bazaar to load it up with items.

We have alot of players in PoT (not I though), and I will see about grabbing some of that data.

I was looking at the DB sql and noticed some fields that I was not familiar with and was wondering if it is possible to get a DB structure posted with explanations.

Some of the fields new to me were:

minstatus smallint(5) NOT NULL default '0'
avoidance int(11) default NULL
accuracy int(11) default NULL
combateffects varchar(10) default NULL
cost int(11) default NULL
sellrate float default NULL
shielding int(11) default NULL
spellshield int(11) default NULL
strikethrough int(11) default NULL
stunresist int(11) default NULL

Thanks for the great work.

[LothanEQ]

avoidance int(11) default NULL
accuracy int(11) default NULL
shielding int(11) default NULL
spellshield int(11) default NULL
strikethrough int(11) default NULL
stunresist int(11) default NULL

Pretty sure all of these are focus effects on PoTime items.

cost int(11) default NULL
sellrate float default NULL

These have something to do with the base cost/sellrate on items to/from merchants before the economy formula is added to them I think? They've been in the structure a looong time.

minstatus smallint(5) NOT NULL default '0'
combateffects varchar(10) default NULL

Not sure what these are.

[Merth]

The above is correct, plus:

minstatus smallint(5) NOT NULL default '0'
combateffects varchar(10) default NULL

combateffects belongs in the list of focus items from potime. minstatus is not sent in a packet to the client, so this is unique to eqemu only - it specifies the minimum user status required to be able to use the item.

With the exception of minstatus, none of the above stats are coded into EQEMu yet. It just looks purty!

[ksmith]

combateffects should be an int. See item 5760 - Earring of Xaoth Kor

[Merth]

combateffects should be an int.

It was initially, but then we ran across an item that had non numeric data in it.

After we've collected a huge sampling of items, we'll come back to address this issue. It may be that we're not parsing the data correctly.

[ksmith]

I'm curious as to which items had non-numeric data in combateffects.

[Merth]

Here's the IRC log between Doodman and I, reprinted here without permission (ha!)

The item in question is "Combine Horn"

[13:19] <Doodman> http://doodman.homeip.net/eqemu/itemparse-out.txt
[13:20] <merth> excellent!
[13:21] <Doodman> Might depend on the item type or such..
[13:21] <merth> i'm still fuzzy on the end of the packet
[13:21] <merth> i noticed this: unknown107=0|0
[13:21] <Doodman> Yup.. I was right on the structure
[13:21] <Doodman> Hmm.. I'll check it.
[13:22] <merth> how about this one too:
[13:22] <merth> combateffects=0 -
[13:22] <merth> dude, looks like you've got this thing pegged, though

<snip>

[14:11] <Doodman> Btw, that Combat effects that looks funny? It's like that in the packet: 10.000000|0|-1|0|0|0|0 - |0|0|0
[14:11] <merth> oh, interesting
[14:11] <merth> heh parser did its job
[14:11] <Doodman>
[14:12] <merth> i can never remember all the mysql stuff required for new users
[14:13] <Doodman> Fixed the unknown107=0|0 tho
[14:14] <Doodman> Well, wonder what we should do about combateffects.. "0 - " won't load in a int fields.
[14:14] <Doodman> ls -lrt
[14:14] <Doodman> Whoops.
[14:16] <Doodman> Hmm.. One place has it and one doesn't.. The '0 - '
[14:17] <merth> i wonder if it's a bug in their code and nobody notices it - who pays attention to combat effects?
[14:17] <Doodman> What is combat effects?
[14:17] <merth> no clue, one of the new stats for potime items
[14:17] <merth> i think the only one people are certain about is spell shield
[14:17] <Doodman> K.. Lets make that field a string then, so we can save what they send.
[14:18] <merth> sounds good

<snip>

[15:25] <merth> combateffects -> changed datatype to varchar(10)

[ksmith]

Curious. I'll have to pick one up and take a look at it.