c:limit on c:resolve

Hi All

Am having some issues with using the API to do some heavy lifting.

So its a PS2 query, but i assume its the same for EQ.

Basically I am getting an outfits data, and then using c:resolve to grab the player data at the same time, so i just need to do one query, And this works fine for smallish outfits, as can be seen here

http://x8-decisive-sylph-m.appspot.com/?outfit=PUGZ

but if I pick a big outfit, I invariably get time-outs or some other error, due to the size of the data. (Sorry SOE for the error message, its often not true, i should fix that sometime )

http://x8-decisive-sylph-m.appspot.com/?outfit=G0DS

So what I wanted to do was to split this up into a few calls to the soe server, each getting about 100 characters. I currently use the following call

http://census.daybreakgames.com/s:mb/get/ps2-...s.last_login),member_online_status&c:limit=10

But the c:limit only affects the number of outfits in the return, not the number of characters in the members list.

Code:

{     "internal": false,    "outfit_list": [ <<<<< This list is limited I think >>>>>        {            "id": "37511770385198092",            "name": "PublicUtilityGroupZealots",            "alias": "PUGZ",            "leader_character_id": "5428013610484427313",            "member_count": "66",            "members": [ … ],  <<<<< This is still the full number >>>>>            "time_created": "1.362683819E9"        }    ],    "returned": 1,    "timing": {        "character-ms": 34,        "characters_online_status-ms": 12,        "outfit-ms": 4,        "outfit_member-ms": 7,        "total-ms": 275    } }

So my question is, is there any way to limit the number of members that are returned, and where the start point is like c:limit and c:start.

Cheers

Mark

 

As far as I know, the only thing you can control in a resolve is which fields are returned, and you're already doing that.

 

Ah, thats a little annoying,

I guess I can get the player ID's from this list, and then get a list of the more specific info in a separate call to the API.

Cheers for the answer though, I was just hoping I was wrong

K1

 

Oh foolish me, there is a separate outfit_members query which you can limit appropriately.

a good case of rtfm there, sorry all.