Post by daver on Jul 7, 2015 3:24:26 GMT -8
Just wondering if someone could clarify what the format of the "info" message should be in the comms protocol. It seems that Tiltyard and the competition game masters are inconsistent in their requirements. From this link: games.stanford.edu/index.php/communication-protocol it states that:
This seems fairly clear! A minimal player that returns the string "available" should work, while a more verbose player that returns "((name me) (status available))" should also work.
Unfortunately, returning "available" works for tiltyard but fails for the competition player checker (http://gamemaster.stanford.edu/playerchecker.php)
Conversely returning "((name me) (status available))" works for the competition player checker but fails for tiltyard. Note: I also tried a few other combinations, for example, the simpler "(status available)" also works for the competition player checker but again fails for tiltyard.
So does anyone know what will work for both game masters?
Thanks,
Dave
Upon receipt of an info message, a player is expected to return available if it is ready to receive messages. Otherwise, it should return busy. It may also return arbitrary information about itself as a sequence of pairs of type and value, e.g. ((name egghead) (status available)).
This seems fairly clear! A minimal player that returns the string "available" should work, while a more verbose player that returns "((name me) (status available))" should also work.
Unfortunately, returning "available" works for tiltyard but fails for the competition player checker (http://gamemaster.stanford.edu/playerchecker.php)
Conversely returning "((name me) (status available))" works for the competition player checker but fails for tiltyard. Note: I also tried a few other combinations, for example, the simpler "(status available)" also works for the competition player checker but again fails for tiltyard.
So does anyone know what will work for both game masters?
Thanks,
Dave
