Deprecated Darkstar fourms

I have added a few mIDs to items that weren't in the database yet, and I made sure that they were added in both item_armor and item_basic, but when I add them in game I am unable to equip them. They show up in my inventory and they appear white as if I could equip them, but when I click on them nothing happens.

I also checked the #Define_Max_Item_ID value to make sure it was high enough and it appears to be, is there something that I am missing or is it a glitch currently?

Appreciate the help!

did you put in the right jobs/level/slot in item_armor?

yeah, strangely enough if I un-equip/re-equip another piece of gear or zone I'm able to add the items.

huh, that's weird

my suggestion is to run in debug and step through the equip function in charutils to see where it skips out

I've seen this happen before, are those armors you're trying to equip the new LV99 pieces by any chance?

I found the problem, the current item_armor values for any of the items added in the last few official updates are incorrect. They're half of the value that they should be.
For example: the item "Karieyh Morion" has a value of 10689, when it should be 21378. I'll go through and correct what I can find, but just keep in mind that many of the values are off. The easiest way to double check the values is to export the Item Data to an .xml from POLUtils and then convert the Hexadecimal value for the "jobs" field to decimal and be sure that the numbers match up.

Fixing the IDs appeared to work for the new armor pieces, but not the new weapons.

babblebab wrote:I found the problem, the current item_armor values for any of the items added in the last few official updates are incorrect. They're half of the value that they should be.
For example: the item "Karieyh Morion" has a value of 10689, when it should be 21378. I'll go through and correct what I can find, but just keep in mind that many of the values are off. The easiest way to double check the values is to export the Item Data to an .xml from POLUtils and then convert the Hexadecimal value for the "jobs" field to decimal and be sure that the numbers match up.

oh, the jobs equippable number... the thing is, every armor has the number half of what the POL utils value is (see: twilight set, askar set, phorcys set, etc.). the only set that's 21378 is mikinaak, and it shares the same usable jobs as askar/karieyh/twilight/phorcys/ogiers etc (so i'm pretty sure that's wrong). reason being: i don't know, i guess it was decided halving them all was possible because the last bit would never ever be 1 (since that's reserved for unknown/invalid job)

maybe when the EquipArmor function was written, it was not under the assumption tools would be used to dump dats to sql? (since you have to manually find model ids anyways)

ah, okay. that makes sense, because it ended up breaking more than it fixed when I started changing numbers around.