Trying to create a guild quest leaderboard

I'm very new to the programing/coding that's being used for these data feeds. I've been teaching myself html/xhtml/php for quite some time, but I haven't gotten into js, xml or any of the other web programming languages. I've been stumbling around looking through the stuff I can find here. I've worked out most of what I'd like to use for my guild site, but I'm still having trouble with the quest leaderboard I'd like to do.

I want to find a way to retrieve a list of the character names and quest/collection completion counts for just the members of my guild so that I can create a leaderboard of just our guild members. I've got a query that will pull up the first guild member it finds and gives me the information I'm looking for, but I can't figure out how to get the information for all of our guild members. Is this something that is possible to do?

Here is the query tha I have right now:

census.daybreakgames.com/jml/get/eq2/character/?guild.guildid=2735&c:show=name.first,name.last,quests.complete,collections.complete

Thank you for your help.

 

The query looks pretty good. Realize that, without a &c:limit= , you are only going to get the first result back.

If you want 20 results back:

census.daybreakgames.com/yml/get/eq2/cha...&c:limit=20

I would not try to do 100 or more, as the query will possibly hang. I suggest grabbing 20 at a time and paging through the results, or storing this info locally and doing updates as character records are updated.

 

Again, thank you for the answer. I will look at both of the options you suggested. Though it looks as I can only grab 5 records at a time without timing out.

 

Use guild.id instead of guild.guildid.  This is indexed, and will return MUCH faster.  Here's an example with a c:limit of 500:

Code:

census.daybreakgames.com/jml/get/eq2/character/?guild.id=1529485981&c:limit=500&c:show=name.first,name.last,quests.complete,collections.complete

 

Wow, that was MUCH quicker. Thank you.

 

That's an awesome idea Leaha.

I posted links to my own guild on our officers forum.  For the most part, we'll be using the data for a loot system.

But we're still evaluating other ideas on how we're going to use this.

@Dan

We noticed that some members will come back with 0 quests on one query and the actual amount they've done on the next.  Seems totally random.  Any idea what's going on there?

The queries we're running are:

census.daybreakgames.com/get/eq2/guild/?...mp;world=Unrest

census.daybreakgames.com/jml/get/eq2/cha...ctions.complete

 

In the first one, you're querying the guild collection (../eq2/guild/..).  The guild collection doesn't have any information about completed quests for a character.

In the secon one, you're querying the character collection (../eq2/character/..).  The character collection contains the completed quest information.

You might be interested in the resolve for the guild collection:

census.daybreakgames.com/get/eq2/guild/?name=So...tions.complete)

You can put the fields from the character collection within the parenthesis separated by commas and it will include those in the results.

Also, you may notice some characters in the guild collection when you do the resolve that have hardly any information.  Those are characters that are either hidden by their security settings or haven't logged in since the REST API came online.

Hope that helps.

 

I've reported that issue a few months ago.  Randomly, someone's quest count will revert to 0, and it will stay that way a few hours (or a few days), and then suddenly it will once again return the correct number of completed quests.  Possibly until their next zoning, I'm not sure.

On average, I usually have 1-2 characters in my "test" guild that exhibits the issue.

 

Storms.Llogwey reported this problem to me as well. As he is the 2nd top quester worldwide, you can imagine this was a key issue for him. The problem went away after zoning a few times.

 

It still appears randomly for various people.

Check out a RosterMaster Standalone install with version 5.2.5.  In the event log you will see some occasional "Quest bug workaround triggered for xxx" - those are characters who suddenly returned 0 for completed quests.  My workaround will simply refuse to change someone's quest count from "xxx" to "0", and keep the original value in the local cache, while logging the event.  That allowed me to keep track of how frequent the issue was.

 

That's a good idea.  I may look into implementing that same logic over at EQ2U.  Of course, ideally, we'd just get it fixed at the source, but until then.... 

Thanks!