1. Can I run my cron job every 3 or 5 minutes instead of your suggested frequency of 10 minutes?
It makes for a very boring experience on the ladder right now, since activity is low. Also, I'm pretty sure I don't have bugs with the amount of games I'm querying for, and I am also deleting "stale" games. (In short, responsible developer :P)
2. I would like to show the clan icon of every player who plays on the CLOT. The api returns the clan name. Is there any way for me to retrieve the clan icon too? (One hack I can do, is to store all the icons manually for each clan as resources and display the appropriate icon based on clan name returned by the api -- But I would prefer not to do this due to there being a chance of me being out of sync with clans on WL)
1) I think his directions say not to shorten it unless you are doing RT. So no reason you could not check 3-5 minutes, you just want to make sure you are not pounding the server (that everything works correctly first).
2) Hmm, I have no idea how you would store the icon. The Wiki says the JSON contains "their names, color, their state, etc." (what is the "etc."?)
Yes, your method would be out of sync if a clan changes their icon for sure. There must be a way to query their profile though as Fizzer clearly does it for his ladders.
1. Quoting Fizzer """For real-time games, you can set this as low as 10 minutes."""
Hence my question, if I can reduce it further.
2. This will return the following fields about the player whose token you provided:
tokenIsValid: This simply tells you that the token does belong to a WarLight player. name: The player's WarLight nickname. isMember: True if the player has purchased a WarLight membership. level: Their current level. color: The player's preferred WarLight color. tagLine: The tagline the player has set up to display on their profile page. clotpass: See CLOT Authentication createPlayerLimit: The maximum game size that they can create. lowestUsableLuckModifier: The lowest setting they can specify for the luck modifier when creating games. levelForMapUsage: The level the system considers them when determining what maps they can use. If their level is 5, but their levelForMapUsage is 10, they can use maps that unlock at 6-10, even though their level isn't techincally high enough. featuresUnlocked: What features they've unlocked, either from leveling up or purchasing a membership.
