Clarify that at client connection server may give multiple game-state events

This mode is convenient for clients that aren't expecting to jump into
some mid-game state without having transitioned through each state
along the way.

With this change we increment the protocol version to 0.6.

diff --git a/api.text b/api.text
index b1a8f798175a7e89d644c2165a8225c7ff75a62c..26f0a4d92f4e40ecf330b1832a5932208434a197 100644 (file)
--- a/api.text
+++ b/api.text
@@ -1,6 +1,6 @@
 Empires Game Protocol
 =====================
-Version: 0.5
+Version: 0.6
 
 For a specific game the following API endpoints are defined.
 (Note: Only the trailing portion of the API URI is provided here.
@@ -53,7 +53,7 @@ For a specific game the following API endpoints are defined.
 
        WHEN: When client first connects and whenever game state changes
 
-       VALUES: Event gives both the old and new state. Game state
+       VALUES: Event gives both the old and new state.
                Each will be one of the following:
 
                none: Pseudo-state used as old_state when game is started
@@ -61,6 +61,12 @@ For a specific game the following API endpoints are defined.
                 reveal: Character names are being revealed to players
                 capture: Players are guessing characters in capture attempts
 
+       NOTE: When a client first connects, it may see multiple
+             game-state transitions, to transition step-by-step from
+             the initial state to the state of the current game. See
+             the example below which would be presented to a client
+             joining a game that is already in the "reveal state.
+
        EXAMPLES:
 
                event: game-state