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

item.modifiers and character.equipmentslot_items quantifiers

Discussion in 'Census: General Discussion' started by Dedith, Jan 17, 2013.

  1. Dedith

    Dedith Guest

    1. Any chance we can get any form of an index against item modifiers?  I'd suggest for at least the attribute modifiers, but all would be nice.  This would be handy when searching for item upgrade options. 

    Example, census.daybreakgames.com/jml/get/eq2/ite...=displayname,id

    2. Any change we can get any form or way of searching the contents of an item slot?  Example, something to facilitate the quandry of what do all priests on a specific server wear in their chest slot?  Or, what do my guildmate scouts use for primary or secondary weapons? 

    Granted, the second example is not to bad to loop/iterate through for most guilds, depending upon size, but it's still a brute data parse using a lot of bandwidth.  I'd rather not pull down and cache the entire item and character collections like some sites are doing.

     
  2. Dethdlr

    Dethdlr Guest

    Not sure why you're including modifiers.agility twice in that query.

    If you're looking for agility, you don't need to say &modifiers.agility.displayname=agi.  It will always equal agi since the node is the agility node.

    If you're looking for an agility value greater than a certain number, you should just need to say modifiers.agility.value=]163 or whatever number you want.  Example:

    census.daybreakgames.com/jml/get/eq2/ite...=displayname,id

    But I could be missing something.

     
  3. Dedith

    Dedith Guest

    No, you're not.. it was a data query to find items with agility expanded to then show them greater then a certain value.  Yes, the name part was redundant and I had thought about it later, after I already posted..

     
  4. Dedith

    Dedith Guest

    It was brought to my attention that the second request is a bit unweildly, and with the current setup and configuration of the data.. I won't disagree.

    The idea is to allow for a search for the id's of what other folks are weilding in what slot.  Granted, if I pulled down mass data dumps nightly, I would have no issues handling this myself, but that is harsh to my hosting policies and bandwidth usage of Census.

    Without altering the equipmentslot_list to an associated array, I can only see a tweak or expansion or hidden aspect of c:show.  Basically, get c:show to allow defining attributes to limit the fields as well..  example, only show me equipmentslot_list entries and limit those to where the id is 0.  From what I can tell, the ID has been the index in the equipmentslot_list array, so is there maybe a way to identify this within c:show parameter?  I've attempted c:show=equipmentslot_list(0), c:show=equipmentslot_list[0], c:show=equipmentslot_list{0}, and c:show=equipmentslot_list.0 all to no avail.

     

Share This Page