Page 1 of 1

Version 1.22

PostPosted: Tue Jul 30, 2013 2:25 am
by Daniel
In V1.22 the NaiveAgent has been switched to fast-shooting; the change can be tracked down to the class ClientMessageEncoder. Message names "cshoot" and "pshoot" suggest safe shooting but the MID "cFastshoot" and "pFastshoot" are send. What is the reason behind this change? I think participants using the Java framework should be made aware of this.

After the time-limit has been reached the server responds with the code byte [2]. This is actually a valid response from the server for some of the queries (e.g. check state, where 2 == EPISODE_MENU). This is not a very safe way of doing things and hard to catch on the client side.

Looking forward to the competition!
- Daniel

Re: Version 1.22

PostPosted: Sat Aug 03, 2013 4:42 pm
by Jochen
Hi Daniel,

thanks for your suggestions. We just released version 1.23 and included some of the points you mentioned.

However, we did not change byte [2] as it is too late now to change the protocol.
While [2] is a valid return value of other commands, it should be easily possible to recognize it for all commands for which it is not a valid return value. After all you have 3 minutes to detect it.
Sorry about that.

See you soon,