Page 1 of 1

another state machine restriction

Posted: 29 April 2013, 07:16
by ddyer
It appears that having multiple meta-variables in the state message strings doesn't work, and
results in uninformative errors. Ie;

clienttranslate('${actplayer} must play a stone')
clienttranslate('${you} must play a stone')

are ok, but

clienttranslate('${actplayer} or ${you} must play a stone')

is not

Re: another state machine restriction

Posted: 30 April 2013, 19:46
by sourisdudesert
Hello,

Well, it depends :)

In your case, what you need is a multiplayer game state. And when the game state type is multiplayer, actplayer has no meaning and should not be used.

Cheers,

Re: another state machine restriction

Posted: 01 May 2013, 00:26
by ddyer
sourisdudesert wrote:Hello,

Well, it depends :)

In your case, what you need is a multiplayer game state. And when the game state type is multiplayer, actplayer has no meaning and should not be used.

Cheers,
The undocumented rules don't bother me much, I can find those as I go.
I'm more disturbed by the fact that the error that this causes is totally uninformative and nonspecific.