- Prestige Scrap: 75 Prestige, 75 Mana, 75 Research, 1 Giant Rat Heart, 1 Pyrestone, 1 Sharproot
- Prestige Parchment: 200 Prestige, 200 Mana, 200 Research, 1 Wild Dog Heart, 1 Claristrine, 1 Silverthorn
- Prestige Page: 500 Prestige, 500 Mana, 500 Research, 1 Wolf Heart, 1 Deepsilver, 1 Furzion Seedpod
- Prestige Scroll: 850 Prestige, 850 Mana, 850 Research, 1 Brown Bear Heart, 1 Rainbowstone, 1 Brownback Moss
- Prestige Codex: 1200 Prestige, 1200 Mana, 1200 Research, 1 Giant Scuttler Heart, 1 Trove, 1 Suntree Haft
- Prestige Book: 1850 Prestige, 1850 Mana, 1850 Research, 1 Scritcher Heart, 1 Svelaugh Sand, 1 Vistrok Flower
- Prestige Tome: 3250 Prestige, 3250 Mana, 3250 Research, 1 Scaled Charger Heart, 1 Earthblood, 1 Ironstem Root
You can also see the server’s daily heart beat or ebb and flow of player demands (this is over a week). The later half of the graph increases in requests per second as you (the players) activate the Heart of Corruption and then in response start sending thousands upon thousands of missions to it and the corrupted temples.
CHANGES TO IMAGE, CSS & SCRIPT HOSTING
MAIL NEXT & PREVIOUS ITEMS
The next and previous buttons are category aware, so if you are in a subcategory e.g. sent or trade they will just navigate you through available mails in that subcategory.
Players can pass their Combat API key to third parties (such as alliance techies, or killboard website operators) and these third parties can then query this page on behalf of the player, and retrieve the individual combat reports for every combat this player has been involved in.
ISSUING & REVOKING YOUR COMBAT API KEY
Go to your Account & Preferences page and click on the API submenu:
Account sitters can generate and/or revoke API keys.
USING THE API KEY TO GET AN XML LIST OF AVAILABLE COMBAT REPORTS – A PROGRAMMERS’ GUIDEIf you’re not a programmer, then the following is probably not relevant, and you can skip over the next couple of sections!
This helps you identify which server to query (we currently only have elgea) and what page to query with the key.
A sample full combat API key for elgea might look like this:
This identifies this key as being good for pulling data from Server [elgea] for Combat Reports [COMRP], and the remainder of the key is an encrypted piece of data that identifies the player to us (twinned with the rights he has given to this key).
To query a key for the first time, call the following page:
http://elgea.illyriad.co.uk/external/combatreportsapi/[insert player's full Combat API Key including the server and keytype here]
and so, using the example above, your query would be:
WHAT DOES THE PAGE RETURN?
</server> <player id="1"/><playerapikey id="elgea-COMRP-AQAAABoolkA8l0qQ7kL5Vpxmk-LwCjrv0qh5f9uB6M10saMBnAi01_ 0IiV4a-pnxWDUF5UcAhtw1SNQ2n0XGbgvb6gw="/> <combatevents>
Breaking it down, you have:
- The standard Server Identification snippet, followed by
- The PlayerID who this Key belongs to, and the exact key you just used
- A list of combat events that this player has been involved in, along with the <personalcombatkey> identifier so you can then go off and query the specific event for the full details, using:
http://elgea.illyriad.co.uk/external/combatreport/[insert <personalcombatkey> here]
HOW TO CHOOSE WHAT EVENTS YOU NEED TO QUERY
1. You may already have the report from another player
- You already have a combat report with this <server id> and
- You already have a combat report with this <combatguid id> and
- You already have a combat report with this <troopmovementevent id>
- This new report has a less than or equal to ( <= ) <datacomplete id> than the one you currently have:
WHEN TRUE (YES, YOU HAVE THIS “NEW” REPORT ALREADY AND THE VERSION YOU HAVE IS AS GOOD AS, OR BETTER THAN, THE NEW REPORT) THEN
- Don’t query this report – you already have everything you need
WHEN FALSE (NO, THIS “NEW” REPORT HAS MORE ACCURATE DATA THAN THE REPORT YOU CURRENTLY HAVE) THEN
- Query this report using the <personalcombatkey id> and replace your existing report with this one
- This is a new report and you should import it
The reason we have the datacomplete flag is because different players can get slightly different versions of the same combat report (eg “Your army was completely destroyed and you heard nothing of its’ fate” vs “You completely whupped that guy, here’s the report”).
2. You don’t need to query the complete player history every time, to decide what’s new
Obviously we don’t want you to be querying a complete player history every time you pull the API key.
So there is an additional parameter we’d like you to use when you subsequently query view_combat_reports_api.asp – this parameter is called [since]. [since] is based on the actual combat occurrence date, not the date that the army was originally sent, so it should be a historic record.
This should be set to the most recent <combatoccurrencedate> for the <player ID> whose key you are using.
If you don’t have any data for this player so far, then please do not provide the [since] parameter.
Because there is a chance that you might have two combat events from the same player occurring at the same second, we will return the event(s) you already have at that datetime stamp, so please be prepared to ignore the first couple of events returned – as you may already have them (see above for how to decide).
The [since] parameter is in the same format it was provided in originally in the <combatoccurrencedate>field of the last report you have from this player, such as: 2014-08-06T03:09:10
The Date Time format is YYYY-MM-DDTHH:MM:SS
So, a first API Key query might look like this:
… and a subsequent one might look like this:
… which will only return those combat events related to the player since (and including) the event that occurred on the [since] timestamp.
HOW OFTEN CAN I QUERY A PLAYER’S API KEY?
For the purposes of development, we haven’t yet set a limit.
However, we will probably impose a limit for a particular key query (from the same querying source) at some point in the future, simply to preserve server resources and bandwidth. It all rather depends on how you player-programmers choose to use the API key system!