Combat API and its use in a Player Run Tourney

SC,

I appreciate that even in the absence of us agreeing on many points, you are willing to go ahead with the Tourney Key, so thank you.

Digioso - I'll be happy to work through the xml with you, I will message you separately.

Koda, I'm sure we will come up with something to address your concerns.

C

kodabear wrote: <span style="line-height: 16.8px;">the limited-data tournament key must include casualties doesn't matter if say what type of units but i do want the casualties as part of the Tournament </span>

Agreed. It's the troop count we object to, not the casualties.

C

I agree the the data should not be so limited that the key will only work for this type of tournament. 

The meaningful frank exchange of views gives me hope that an acceptable solution will be taken care of.  Hopefully this will herald an increasingly broader concept of "community" with the user base becoming increasingly involved in direction and development.  I think that, at present, the Illyriad gaming model requires changes to increase its stability, and these events give me hope that they will be addressed.  It is ultimately all about keeping customers happy and loyal by communicating with them and involving them.  Fingers crossed Eh? 

My suggestion would be this:

For the combat report overview (API-Key):
<combateventsapi>
    <server>
        <datagenerationdatetime></datagenerationdatetime>
    </server>
    <player id=""/>
    <playerapikey id=""/>
    <combatevents>
        <uniquecombatidentifier>
            <server id=""/>
            <combatguid id=""/>
            <troopmovementevent id=""/>
            <datacomplete id=""/>
            <personalcombatkey id=""/>
            <combatoccurrencedate></combatoccurrencedate>
        </uniquecombatidentifier>
    </combatevents>
</combateventsapi>

Here it would also be nice if you could include the X/Y coordinates as well. Not only for the tournament API but for the normal API as well.
If a tournament only happens on specific squares we can skip reading unneccessary reports.
For the tournament API this doesn't really matter because it'll only provide reports for tournament squares. But it would be nice to have for the normal API.

Fot the specific combat report:
<combatevent>
    <server>
        <datagenerationdatetime></datagenerationdatetime>
    </server>
    <personalcombatkey id=""/>
    <uniquecombatidentifier>
        <server id=""/>
        <combatguid id=""/>
        <troopmovementevent id="" occurrence_datetime=""/
        <datacomplete id=""/>
    </uniquecombatidentifier>
    <combatoverview>
        <location>
        <X></X>
        <Y></Y>
        <terrainspecifictype id=""></terrainspecifictype>
        <terraincombattype id=""></terraincombattype>
    </location>
    <datetime>
        <combatoccurrencedate></combatoccurrencedate>
        <occupationlengthsecs></occupationlengthsecs>
    </datetime>
    <stratagem>
        <armyaction id=""></armyaction>
        <feint>Yes/No</feint>
    </stratagem>
    <participants>
        <participant>
            <role></role>
            <player>
                <playername id=""></playername>
                <alliance id="">
                    <allianceticker></allianceticker>
                    <alliancename></alliancename>
                </alliance>
            </player>
        </participant>
    </participants>
</combatevent>
   
Either: total casualties for the whole battle or casualties per side:
EG Defender(s) lost x troops and Attackers lost x troops

And we need to have an identifier which side is left standing after the battle.
<winner></winner>
EG:
0 = Attacker
1 = Defender(s)
2 = Both are left (EG after a raid)