Tournament Square Update!

Dung - yes, you're spot on.

I believe there is an easy way to do this (for the Devs).

The existing mechanism for accessing the API (i.e. the bit of code on the Illy servers) requires two parameters (other than the server name) - these are a Key_Type and the API_Key.

The API_Key is the long string that identifies the player's data that is requested - and is specific to each Key_Type.  The Key_Type is a shorter string (e.g. COMRP) for Combat Reports, that defines the content of the data requested.  A player must generate an API_Key for each type of Key_Type.

Presumably, the actual API accessed on the Illy servers is the same API regardless of the request - it's just a case of filtering/authenticating to determine what data is passed back to the requester.

Therefore, this model supports the introduction of additional Key_Types (for example "Tourney Combats": TCOMRP).  By calling the API with this Key_Type, and an associated valid API_Key, the API could pass back the required data - which in this case should just be a subset of the data returned under the COMRP Key_Type.

In development terms, the API (or API broker service if used) would need a small code change to handle the new Key_Type.  This would be very similar to the code for handling the COMRP call, but with a few data fields deleted - the XML schema would not need to change, neither would the core API logic.  Further code could be added to just return reports from combats on the set of tourney square co-ords - but that would just be icing on the cake.

A UI change would also be required to add a fourth button to the API Key screen, labelled something like "Tourney Combat Reports" - but that would mostly just copy the logic/code from the other three buttons.

I expect that accommodating this type of change request with little effort is exactly why the API was designed this way in the first place....

Cilcain