Outfitpoints - an outfit management toolkit

[Goblinhunter]

I've just pushed a number of updates to outfitpoints.com, my API app for outfit management statistics:

• Tag based searching
• Facility statistics and graphs
• Server names
• Per member average deviation stats
• Export to CSV
• Caching and speed improvements

I've also had quite a few people contact me by email to ask how they can query data from the API, so this is obviously something quite a few people are keen on. If you have questions on how to use the API I , and i'm sure lots of others here, would be more than happy to answer the questions.

If anyone is looking for specific code examples, I'm also happy to share them. My code is in C#, but i'm sure there are many others here with other languages.

[Ghryphen]

Looking good, the feature set is looking very familiar

[Goblinhunter]

Well most of these were added from user requests, but point taken . The aim of this site isn't to compete with what PSU offers, but to compliment this with more in depth outfit analysis, trend data and differing views on data that only a site that solely focuses on outfit management can provide.

[Dreadnaut]

Might I suggest you allow users to search via Alias as well? I honestly don't know many outfit names in game and I'm always wanting to look people up via the Alias.

Maybe that's just me, just thought I'd share my thoughts. Nice work.

[Goblinhunter]

Dreadnaut - searching by Alias/Tag is already possible either by just entering the alias to search by name and alias, or if you enclose the alias in square brackets, it will search only for the alias.

[Dreadnaut]

Originally Posted by Goblinhunter

Dreadnaut - searching by Alias/Tag is already possible either by just entering the alias to search by name and alias, or if you enclose the alias in square brackets, it will search only for the alias.

Ahhhh, nice! Thanks!

[Goblinhunter]

I'm going to be adding in historical trend statistics very soon (so you can see XP, BR, Members levels etc over time) and I've already started collecting this data in preparation for this, however I am only collecting it for outfits that use the site, so if you want historical data for your outfit, make sure you have searched for them at least once.

[Goblinhunter]

I've just published a brand new site design and updated the chart components, in preparation for new charts, and historical stats coming in the next week or so.

[Goblinhunter]

I've just published an update to outfitpoints.com, that adds in historical trend data. You can now view things like membership count, XP, Kills etc. over time to see how your outfit is improving, or not as the case may be.

I'm only collecting the data for outfits that use the site, so if your outfit has never been searched for on the site before then there will not be any data, but the act of you viewing your outfit will add it to the list to get collected, and stats will appear within 48 hours.

[EVILPIG]

I don't understand how your API reads different averages than PSUs.

[Goblinhunter]

I would imagine it is down to caching. I cache outfits for around 5 minutes to lessen the amount of requests I need to make to the API. I imagine PSU does the same, but if they don't line up the numbers will vary slightly. This will be more visible on large outfits where there is more activity and so more variance between cached versions.

Looking at the stats for the 666th currently there are small variances in the numbers of kills, XP etc, which will be down to caching, and so vary the average.

There is also a discrepancies of 1 outfit member between OP and PSU, which could be down to caching, but is more likely to do with the way we clean our outfit members list. The API outfit members list often contains a large amount of invalid, empty or just plain wrong members, which need to be pruned before the list can be used. It is likely that mine and PSU's method to prune these varies slightly.

[Ghryphen]

Our outfit pages are built using 1 query and it's cached for 5 minutes. I think the only thing I'm pruning from the results is if the player name is blank.