Bug hunt
Compare Planar Traveler's Manual (lucy) and Planar Traveler's Manual (eqemu)
There is a field between accuracy and factionmod1 that is somehow related to charm-slot items, possibly a formula id since all the ldon charms have the same value in that field. |
Looks very likely that we have our fields off. Do you know of any items that have a value for this mysterious field?
Here's our item struct, if we shift the faction stuff down one position, remove unknown089, and add in unknown081, everything lines up. Code:
/*080*/ sint8 Accuracy; // PoP: Accuracy + |
Here's a listing of all the items I have where that field is non-zero:
Code:
UNK ID Name |
Regarding your comment about the possible connection to charms .. does the value of this column change as the power of the charm changes? Or does the value maybe relate to the type of effect?
Examples for each of the two scenarios I am talking about: * Charm based on gold user carries, as user carries more gold, this value grows? * Charm based on gold user carries, so value is 12345. Other charm is based on PoP flag user has, so value is 12346. |
The value of the field is the item id of the first item to use that charmfile. It is a static value.
|
I think you have correctly found the "LDON ONLY" flag. It is my understanding of these charms listed that they only work (ie modify a stat) in LDON Adventures.
Nice find. 8) /envy EOF |
Nope, it's not an LDoN only flag. Quite a few of those are LoY charms - one is the charm that was introduced this summer when they made changes to what flag requirements you need in PoP.
Edit: Doing a little research - each classes Intricate Wooden Figurine uses a different item number(id field), but they all use that same unknown, 35001. |
Made this a sticky so we don't forget to implement. This change needs to be replicated to the packet collector as well as the emu code.
|
With the 10/09 patch, 4 new fields have been added at the end of the item data. The lore text field no longer begins with special characters to indicate lore, artifact, etc. The first of the four new fields is the lore flag (1 = lore), the remaining three are unknown to me.
Additionally, the field that used to be the last field holds some sort of augment item type restriction (0 = no restriction, 2 = Weapons only, 3= 1H Slash only) Code:
+-------+----------------------------------+--------+ |
Quote:
EOF |
Regarding the change to lore name and the 4 new fields:
In addition to the * symbol in the lore name that was the flag for lore items, there was also a # symbol for items that are artifacts. The # could appear in either the 1st or 2nd position, depending on whether the item was also flagged as lore. Do an item search with Artifact = Yes to see this. So I would guess that one of the 4 new fields is a flag for artifact items |
As pointed out by ric0h, elemdmgtype and elemdmgamt are reversed in the database.
|
Could you also please change the way nodrop and norent fields and make them like loreflag and artifactflag? E.g. loreflag=1|0 ?
That'll make the table much more easier to read. |
Quote:
|
ok then what is the meaning of value 255 for nodrop and norent fields and what other values they might have?
|
All times are GMT -4. The time now is 04:07 AM. |
Powered by vBulletin®, Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.