1. I have corrected the e-mail settings so that outgoing e-mails from these forums should be sent now. If you tried to Register or Reset your Password, please try again!
    Dismiss Notice

Constants values for slot IDs and item's use of slot IDs don't match

Discussion in 'Census: General Discussion' started by Quicktiger, Oct 27, 2012.

  1. Quicktiger

    Quicktiger Guest

    Item //census.daybreakgames.com/jml/get/eq2/item/4022135446 has a slot ID of 23, with a name of "Cloak", but the contants data at //census.daybreakgames.com/jml/get/eq2/constants/ says id 23 is "Drink", and 19 is "Cloak."

    I was hoping I did not have to store strings for slot IDs, but I fear I may.  There are other misuses of IDs, like tradeskill IDs and adventure IDs overlapping, so I have to store the actual class name there as well.

    There is also an alphanumeric equavalent to the slot id value, which is included in the constants table.

    Is it possible that items use a different table than the one I am thinking I should be using, since there would be no such thing as two slots for rings, two for ears, two for wrists, and two for charms?

     
  2. Zoltaroth

    Zoltaroth Guest

    Yah... our slot system is special.  I will add the "perm_id" to constants to give you a lookup against this. 

     
  3. feldon30

    feldon30 Guest

    Nice. :) We looked at SlotID when we started getting item data, saw it was totally bonkers, and just wrote our own list. ;)
     
  4. Quicktiger

    Quicktiger Guest

    I did the same, w.r.t. slots.  I currenty use a mapping table to translate between equip slots and item-type slots.  Having a way to avoid this is really, really good, since it will remove about 40 lines of code.

     

Share This Page