<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://en.doc.boardgamearena.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Volker78</id>
	<title>Board Game Arena - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://en.doc.boardgamearena.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Volker78"/>
	<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/Special:Contributions/Volker78"/>
	<updated>2026-11-19T10:07:53Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.11</generator>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6111</id>
		<title>Gamehelprage</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6111"/>
		<updated>2020-11-09T21:45:16Z</updated>

		<summary type="html">&lt;p&gt;Volker78: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rage ==&lt;br /&gt;
&lt;br /&gt;
Rage is a bidding trick taking game from Amigo games.&lt;br /&gt;
&lt;br /&gt;
== Goal ==&lt;br /&gt;
&lt;br /&gt;
The game ends after 10 rounds, highest score wins; most correct bids breaks ties&lt;br /&gt;
&lt;br /&gt;
== Cards in play ==&lt;br /&gt;
&lt;br /&gt;
There are 110 cards:&lt;br /&gt;
* 96: There are six (6) suits (Yellow Orange Red Purple Green &amp;amp; Blue) each with cards numbering 0-15&lt;br /&gt;
* 14: There are 5 (gray) action cards&lt;br /&gt;
** 2 (+5) - player taking the trick gets +5&lt;br /&gt;
** 4 Change Trump (❗) - randomly changes trump color&lt;br /&gt;
** 2 (-5) - player taking the trick gets -5&lt;br /&gt;
** 4 No Trump (🚫) - no trump this trick, random trump chosen for the remainder of tricks&lt;br /&gt;
** 2 Joker (Jester hat) - makes this card the highest number of whatever color the player wants (incl. trump)&lt;br /&gt;
&lt;br /&gt;
== Rules summary ==&lt;br /&gt;
&lt;br /&gt;
Each round starts with each playing bidding for how many tricks they will win (total may (far) outnumber available trick count)&lt;br /&gt;
&lt;br /&gt;
Each trick starts with a player leading a color, each other player follows suit, or, if they cannot, plays Action or any other color&lt;br /&gt;
Highest card following suit or highest trump card played wins the trick.&lt;br /&gt;
Player that won the last trick leads the next trick.&lt;br /&gt;
&lt;br /&gt;
At the end of the round, scoring is as follows:&lt;br /&gt;
&lt;br /&gt;
* +1 for each trick you won&lt;br /&gt;
* +/-5 for each Bonus you took&lt;br /&gt;
* -5 for missing your bid number&lt;br /&gt;
* +10 for bidding exactly the number of tricks correctly&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6092</id>
		<title>Gamehelprage</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6092"/>
		<updated>2020-11-07T21:20:54Z</updated>

		<summary type="html">&lt;p&gt;Volker78: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rage ==&lt;br /&gt;
&lt;br /&gt;
Rage is a bidding trick taking game from Amigo games.&lt;br /&gt;
&lt;br /&gt;
== Goal ==&lt;br /&gt;
&lt;br /&gt;
The game ends after 10 rounds, highest score wins; most correct bids breaks ties&lt;br /&gt;
&lt;br /&gt;
== Cards in play ==&lt;br /&gt;
&lt;br /&gt;
There are 110 cards:&lt;br /&gt;
* 96: There are six (6) suits (Yellow Orange Red Purple Green &amp;amp; Blue) each with cards numbering 0-15&lt;br /&gt;
* 14: There are 5 (gray) action cards&lt;br /&gt;
** 2 (+5) - player tacking the trick gets +5&lt;br /&gt;
** 4 Change Trump (❗) - randomly changes trump color&lt;br /&gt;
** 2 (-5) - player tacking the trick gets -5&lt;br /&gt;
** 4 No Trump (🚫) - no trump this trick, random trump chosen for the remainder of tricks&lt;br /&gt;
** 2 Joker (Jester hat) - makes this card the highest number of whatever color the player wants (incl. trump)&lt;br /&gt;
&lt;br /&gt;
== Rules summary ==&lt;br /&gt;
&lt;br /&gt;
Each round starts with each playing bidding for how many tricks they will win (total may (far) outnumber available trick count)&lt;br /&gt;
&lt;br /&gt;
Each trick starts with a player leading a color, each other player follows suit, or, if they cannot, plays Action or any other color&lt;br /&gt;
Highest card following suit or highest trump card played wins the trick.&lt;br /&gt;
Player that won the last trick leads the next trick.&lt;br /&gt;
&lt;br /&gt;
At the end of the round, scoring is as follows:&lt;br /&gt;
&lt;br /&gt;
* +1 for each trick you won&lt;br /&gt;
* +/-5 for each Bonus or Mad Rage you took&lt;br /&gt;
* -5 for missing your bid number&lt;br /&gt;
* +10 for bidding exactly the number of tricks correctly (+5 if you bid 0)&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6091</id>
		<title>Gamehelprage</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelprage&amp;diff=6091"/>
		<updated>2020-11-07T21:19:46Z</updated>

		<summary type="html">&lt;p&gt;Volker78: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Rage ==&lt;br /&gt;
&lt;br /&gt;
Rage is a bidding trick taking game from Amigo games.&lt;br /&gt;
&lt;br /&gt;
== Goal ==&lt;br /&gt;
&lt;br /&gt;
The game ends after 10 rounds, highest score wins; most correct bids breaks ties&lt;br /&gt;
&lt;br /&gt;
== Cards in play ==&lt;br /&gt;
&lt;br /&gt;
There are 110 cards:&lt;br /&gt;
* 96: There are six (6) suits (Yellow Orange Red Purple Green &amp;amp; Blue) each with cards numbering 0-15&lt;br /&gt;
* 14: There are 5 (gray) action cards&lt;br /&gt;
** 2 Bonus Rage (+5) - player tacking the trick gets +5&lt;br /&gt;
** 4 Change Trump (❗) - randomly changes trump color&lt;br /&gt;
** 2 Mad Rage (-5) - player tacking the trick gets -5&lt;br /&gt;
** 4 Out Rage (🚫) - no trump this trick, random trump chosen for the remainder of tricks&lt;br /&gt;
** 2 Wild Rage (Jester hat) - makes this card the highest number of whatever color the player wants (incl. trump)&lt;br /&gt;
&lt;br /&gt;
== Rules summary ==&lt;br /&gt;
&lt;br /&gt;
Each round starts with each playing bidding for how many tricks they will win (total may (far) outnumber available trick count)&lt;br /&gt;
&lt;br /&gt;
Each trick starts with a player leading a color, each other player follows suit, or, if they cannot, plays Action or any other color&lt;br /&gt;
Highest card following suit or highest trump card played wins the trick.&lt;br /&gt;
Player that won the last trick leads the next trick.&lt;br /&gt;
&lt;br /&gt;
At the end of the round, scoring is as follows:&lt;br /&gt;
&lt;br /&gt;
* +1 for each trick you won&lt;br /&gt;
* +/-5 for each Bonus or Mad Rage you took&lt;br /&gt;
* -5 for missing your bid number&lt;br /&gt;
* +10 for bidding exactly the number of tricks correctly (+5 if you bid 0)&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelphaiclue&amp;diff=5869</id>
		<title>Gamehelphaiclue</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelphaiclue&amp;diff=5869"/>
		<updated>2020-10-14T21:18:21Z</updated>

		<summary type="html">&lt;p&gt;Volker78: Created page with &amp;quot;== Setup == &amp;#039;&amp;#039;&amp;#039;1. Put down the cards and tokens.&amp;#039;&amp;#039;&amp;#039; Shuffle the cards and place the deck face down in the center of the table. Pour out the scoring tokens next to the cards....&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Setup ==&lt;br /&gt;
&#039;&#039;&#039;1. Put down the cards and tokens.&#039;&#039;&#039; Shuffle the&lt;br /&gt;
cards and place the deck face down in the center&lt;br /&gt;
of the table. Pour out the scoring tokens next to&lt;br /&gt;
the cards.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Make four stacks of word tiles.&#039;&#039;&#039; On one side&lt;br /&gt;
of the table, line up four cards, one of each color.&lt;br /&gt;
Next to each card, make a stack of random word&lt;br /&gt;
tiles. All the tiles should be white-side up. Each&lt;br /&gt;
stack should have the following number of tiles:&lt;br /&gt;
2 players (cooperative): 2 tiles per stack&lt;br /&gt;
3-5 players: 3 tiles per stack&lt;br /&gt;
6-8 players: 2 tiles per stack&lt;br /&gt;
9-12 players: 1 tile per stack&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;3. Distribute word tiles.&#039;&#039;&#039; Each player draws&lt;br /&gt;
15 random word tiles from the box and lays&lt;br /&gt;
them out in front of them, white-side up.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;4. Distribute guessing tiles.&#039;&#039;&#039; Each player takes&lt;br /&gt;
four guessing tiles, one of each color.&lt;br /&gt;
&lt;br /&gt;
== Each Round ==&lt;br /&gt;
&#039;&#039;&#039;1. Draw a card.&#039;&#039;&#039; Each player draws a card from&lt;br /&gt;
the deck, privately looks at it, and then puts&lt;br /&gt;
it face down in front of them. The card shows&lt;br /&gt;
which of the four target words (the words on top&lt;br /&gt;
of the stacks) belongs to the player.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. Make a clue.&#039;&#039;&#039; Simultaneously, each player&lt;br /&gt;
uses their word tiles to make a clue about their&lt;br /&gt;
target word. Clues must contain at least two&lt;br /&gt;
word tiles. When you finish your clue, rotate it&lt;br /&gt;
so the other players can easily read it, and then&lt;br /&gt;
flip over the extra tiles that you did not use in&lt;br /&gt;
your clue.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;3. Read and guess.&#039;&#039;&#039; When everyone has&lt;br /&gt;
finished making their clues, the youngest player&lt;br /&gt;
reads out loud the clue of the player to their&lt;br /&gt;
left. Each player then secretly guesses which of&lt;br /&gt;
the four target words is suggested by the clue&lt;br /&gt;
by placing a guessing tile face down near the&lt;br /&gt;
center of the table. The author of the clue does&lt;br /&gt;
not guess.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;4. Score.&#039;&#039;&#039; When everyone is ready, each player&lt;br /&gt;
reveals their guess, and the author reveals their&lt;br /&gt;
card. Each player who guessed correctly takes&lt;br /&gt;
a 1-point token from the center. The author of&lt;br /&gt;
the clue takes one point for each correct guess.&lt;br /&gt;
After scoring, the author discards their card.&lt;br /&gt;
In a two-player game, you keep score as a&lt;br /&gt;
team. The team earns one point each time a&lt;br /&gt;
player guesses correctly.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;5. Repeat.&#039;&#039;&#039; Going clockwise, each player reads&lt;br /&gt;
the clue of the player to their left, and the&lt;br /&gt;
guessing and scoring process repeats.&lt;br /&gt;
&lt;br /&gt;
== Between Rounds ==&lt;br /&gt;
&#039;&#039;&#039;1. After a white round, flip.&#039;&#039;&#039; After playing a&lt;br /&gt;
round with the white side of the word tiles, flip&lt;br /&gt;
over the four tiles on top of the stacks so that&lt;br /&gt;
they are black-side up. Each player then flips over&lt;br /&gt;
the tiles in their clue, so that all word tiles in play&lt;br /&gt;
are black-side up, and a new round begins.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;2. After a black round, discard, flip, and pass.&#039;&#039;&#039; &lt;br /&gt;
After playing a round with the black side&lt;br /&gt;
of the word tiles, discard the tiles on top of the&lt;br /&gt;
stacks to reveal four new target words. Each&lt;br /&gt;
player then flips over the tiles in their clue so&lt;br /&gt;
that all word tiles in play are white-side up.&lt;br /&gt;
Finally, each player passes their 15 word tiles to&lt;br /&gt;
the player to their left, and a new round begins.&lt;br /&gt;
In a two-player game, the players swap word&lt;br /&gt;
tiles instead of passing them to the left.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;3. When the stacks are empty, the game is over.&#039;&#039;&#039; &lt;br /&gt;
When all of the word tiles in the stacks&lt;br /&gt;
are discarded, the player with the most points&lt;br /&gt;
wins. If there is a tie, all of the tied players win&lt;br /&gt;
together.&lt;br /&gt;
In a two-player game, the team must score six&lt;br /&gt;
points to win. Eight points is a perfect score.&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Practical_debugging&amp;diff=5284</id>
		<title>Practical debugging</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Practical_debugging&amp;diff=5284"/>
		<updated>2020-08-16T11:15:05Z</updated>

		<summary type="html">&lt;p&gt;Volker78: Description was wrong/not working&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Studio_Framework_Navigation}}&lt;br /&gt;
&lt;br /&gt;
This page gives you practical tips to debug your game during development. Don&#039;t hesitate to share your difficulties with us so that we can improve this section.&lt;br /&gt;
&lt;br /&gt;
== Tools ==&lt;br /&gt;
&lt;br /&gt;
To work on BGA Studio, we recommend that you use [http://www.google.com/chrome Google Chrome] as it&#039;s currently the fastest browser for the BGA platform, and it&#039;s available for all OSes.&lt;br /&gt;
&lt;br /&gt;
Another reason to use Chrome is that it embeds all the tools you need to work on BGA Studio. You can see them by pressing &amp;quot;F12&amp;quot; or from the menu (&amp;quot;Tools &amp;gt; Development tools&amp;quot;).&lt;br /&gt;
&lt;br /&gt;
A good practice is to use a second browser to develop the game, in order to verify that your game is working fine on this browser too.&lt;br /&gt;
&lt;br /&gt;
To debug with Firefox browser, we advise you to use these 2 extensions:&lt;br /&gt;
* [https://addons.mozilla.org/firefox/addon/firebug/ Firebug]&lt;br /&gt;
* [https://addons.mozilla.org/firefox/addon/web-developer/ Web developer]&lt;br /&gt;
&lt;br /&gt;
To debug with other browsers (IE, Edge, Opera), we advise you to use one of the most recent versions. Latest versions of the browser will likely have better development tools than the previous ones...&lt;br /&gt;
&lt;br /&gt;
== General tip for debugging ==&lt;br /&gt;
&lt;br /&gt;
In general for debugging, think of using the &#039;[[Tools_and_tips_of_BGA_Studio#Save_.26_restore_state|save &amp;amp; restore]] state&#039; functionality. It enables you to save the state of your game just before the issue you are investigating, then come back to that point with one click as many times as needed to understand what is going wrong.&lt;br /&gt;
&lt;br /&gt;
You can save up to 3 different states.&lt;br /&gt;
&lt;br /&gt;
== Debugging my game when it cannot start ==&lt;br /&gt;
&lt;br /&gt;
If your game won&#039;t start because of an error, you are probably in one of these situations:&lt;br /&gt;
* There is a SQL error in your dbmodel.sql file.&lt;br /&gt;
* You have a syntax error in your PHP file.&lt;br /&gt;
* Your PHP &amp;quot;setup&amp;quot; - or any method used during the game initial states - generates an exception.&lt;br /&gt;
&lt;br /&gt;
If the error is not explicitly displayed when you click on &amp;quot;Express start&amp;quot;, you should check the &amp;quot;Gameserver error log&amp;quot; as per [[Studio logs]].&lt;br /&gt;
More cases of why game can&#039;t start are described on the [[Troubleshooting]] page.&lt;br /&gt;
&lt;br /&gt;
== Debugging my PHP game logic (or my view) ==&lt;br /&gt;
&lt;br /&gt;
Most of the time, debugging PHP is quite easy. Here&#039;s what I do when I want to develop/debug some game logic that is triggered by some game action:&lt;br /&gt;
&lt;br /&gt;
* At first, I make sure that I can reproduce the needed game situation with one click. To do this, I use the &amp;quot;[[Tools_and_tips_of_BGA_Studio#Save_.26_restore_state|save &amp;amp; restore]]&amp;quot; function.&lt;br /&gt;
* Another possibility for this is to place a &#039;&#039;&#039;die(&#039;ok&#039;);&#039;&#039;&#039; PHP statement right after the PHP I am developing/debugging. This way, I make sure that every request will fail and then nothing will be committed to the database.&lt;br /&gt;
* Then, I use the &#039;&#039;&#039;var_dump&#039;&#039;&#039; function to dump PHP variables and check what&#039;s wrong, until it works.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
// (...my code to debug)&lt;br /&gt;
&lt;br /&gt;
var_dump( $my_variable );&lt;br /&gt;
die(&#039;ok&#039;);&lt;br /&gt;
&lt;br /&gt;
// (...my code to debug)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Add traces to your code ===&lt;br /&gt;
&lt;br /&gt;
You can use the following functions in your game to add server side logging:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;self::dump( &#039;name_of_variable&#039;, $variable );&#039;&#039;&#039;  // dump variable, like var_dump but in the log debug level logging, goes to [[Studio_logs|BGA request&amp;amp;SQL logs]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;self::debug( $message );&#039;&#039;&#039;  // debug level logging, goes to [[Studio_logs|BGA request&amp;amp;SQL logs]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;self::trace( $message );&#039;&#039;&#039;  // info level logging, goes to [[Studio_logs|BGA request&amp;amp;SQL logs]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;self::warn( $message );&#039;&#039;&#039;   // warning level logging, goes to [[Studio_logs#BGA_unexpected_exceptions_logs|BGA unexpected exceptions log]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;self::error( $message );&#039;&#039;&#039;  // error level logging, goes to [[Studio_logs#BGA_unexpected_exceptions_logs|BGA unexpected exceptions log]]&lt;br /&gt;
&lt;br /&gt;
Check [[Studio logs]] for more details on how to access your logs.&lt;br /&gt;
&lt;br /&gt;
This can be useful when you need to follow the flow of your code and not just stop it to see how it goes at some point.&lt;br /&gt;
&lt;br /&gt;
Only the error log level will appear in production. This level should be used only for critical problems. &lt;br /&gt;
Other levels will show only in the development environment and can be used as you see fit.&lt;br /&gt;
&lt;br /&gt;
== Debugging my HTML/CSS layout ==&lt;br /&gt;
&lt;br /&gt;
Example situations&lt;br /&gt;
&lt;br /&gt;
* Why doesn&#039;t my game element show up in the interface?&lt;br /&gt;
* Why hasn&#039;t my CSS property been applied to this element?&lt;br /&gt;
* Why is this game element displayed at this position?&lt;br /&gt;
&lt;br /&gt;
A useful tip when an element does not show up in the interface is to give it a red background:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#my_element {&lt;br /&gt;
  ... some CSS definitions ...&lt;br /&gt;
  background-color: red;&lt;br /&gt;
}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This way, you know if the element is not visible because of some CSS property or because of something else.&lt;br /&gt;
&lt;br /&gt;
Another tip: sometimes, changing a CSS property has no visible effect on your interface. In that case, add a &amp;quot;display:none&amp;quot; property. If your element does not disappear, the bug probably comes from your CSS selector and not from your CSS property.&lt;br /&gt;
&lt;br /&gt;
Using Chrome &amp;quot;Elements&amp;quot; tab (the first one), you can:&lt;br /&gt;
* See the CURRENT HTML of your page. Remember that the classical &amp;quot;show page source&amp;quot; is inefficient with BGA as you are modifying the page source with your Javascript code.&lt;br /&gt;
* Using the &amp;quot;magnifying glass&amp;quot;, you can click on any part of your game interface and check its HTML code and associated CSS styles.&lt;br /&gt;
* You can even modify directly some CSS properties and see how it looks immediately in the game interface.&lt;br /&gt;
&lt;br /&gt;
=== Debugging my Javascript game interface logic ===&lt;br /&gt;
&lt;br /&gt;
Compared to PHP debugging, Javascript debugging can sometimes be painful.&lt;br /&gt;
&lt;br /&gt;
Here are some tips to make your life easier while developing and debugging Javascript:&lt;br /&gt;
&lt;br /&gt;
=== Do complex things on the PHP side ===&lt;br /&gt;
&lt;br /&gt;
The most frequent case is the following: you want to compute possible moves in a game situation. Doing it in Javascript is a nightmare. Do it in PHP, and transfer the results to your client interface using the &amp;quot;args&amp;quot; game state property.&lt;br /&gt;
&lt;br /&gt;
Note: See the Reversi tutorial for an example.&lt;br /&gt;
&lt;br /&gt;
=== Add traces in your code ===&lt;br /&gt;
&lt;br /&gt;
You can use the following:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;console.log( variable_to_inspect )&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It will give you the object structure of the variable in the Javascript console, without blocking the execution.&lt;br /&gt;
&lt;br /&gt;
It&#039;s often a good idea to precede this call with a console.log( &#039;### HERE ###&#039; ); to find more easily the appropriate line in the console log.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;alert( variable_to_inspect )&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
It will popup what you wish and pause the execution until you click ok.&lt;br /&gt;
&lt;br /&gt;
This won&#039;t be useful for complex structures; only native types will be plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.&lt;br /&gt;
&lt;br /&gt;
=== Use Browser Debugger (e.g. Chrome) ===&lt;br /&gt;
&lt;br /&gt;
Modern browsers also allow you to put breakpoints in your js code. &lt;br /&gt;
&lt;br /&gt;
This will stop code execution on that line and will launch the JavaScript debugger.&lt;br /&gt;
&lt;br /&gt;
In Chrome, to add a breakpoint: add a line to your .js file&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;debugger; &amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Refresh the page F5, and make sure you have the Developer tools window open, press F12. &lt;br /&gt;
When the break-point is hit you can then step through your code and visualise variables, etc.&lt;br /&gt;
&lt;br /&gt;
== Online format checkers ==&lt;br /&gt;
Copy and paste code for a quick code sanity check like the right number of brackets.&lt;br /&gt;
&lt;br /&gt;
PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]&lt;br /&gt;
&lt;br /&gt;
JS:  [http://esprima.org/demo/validate.html http://esprima.org/demo/validate.html]&lt;br /&gt;
&lt;br /&gt;
== Some frequent errors ==&lt;br /&gt;
&lt;br /&gt;
See [[Troubleshooting]].&lt;br /&gt;
&lt;br /&gt;
== Get the database matching a bug report ==&lt;br /&gt;
&lt;br /&gt;
For a way to automate the below steps, see this post: https://boardgamearena.com/forum/viewtopic.php?f=12&amp;amp;t=16454#p63167&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:&lt;br /&gt;
* Create a table in the studio with the same game and number of players as the table for which the report has been written. Launch this table.&lt;br /&gt;
* Open another tab on the studio and go to &amp;quot;Manage game&amp;quot; page for your project (you have to be admin for this project)&lt;br /&gt;
* In the &amp;quot;Errors in production&amp;quot; section, fill up the fields &amp;quot;Bug report ID&amp;quot; (this is the ID of the bug report in production) and &amp;quot;Studio table ID&amp;quot; (this is the ID of the table you created above) then click the &amp;quot;⇨ Load bug report state into this table save slot #1&amp;quot; button.&lt;br /&gt;
* If the snapshot is correctly retrieved, you see a &amp;quot;Done!&amp;quot; message.&lt;br /&gt;
* Go back to the tab with your studio table and click &amp;quot;Load 1&amp;quot;.&lt;br /&gt;
* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We&#039;ll need to update them.&lt;br /&gt;
** &#039;&#039;&#039;Important note:&#039;&#039;&#039; if you see a &amp;quot;Done!&amp;quot; message but clicking &amp;quot;Load 1&amp;quot; doesn&#039;t bring any change, it&#039;s that the snapshot is unfortunately not available (most likely because the bug report was declared too long after the game ended and the database had already been garbage collected to reclaim space).&lt;br /&gt;
* Click on the &amp;quot;Go to game database&amp;quot; button&lt;br /&gt;
* For each table using player_ids, you&#039;ll need to update the player_ids from the production to use the player_ids from the studio. You can see the player_ids from the table page before entering the game by hovering over the player names.&lt;br /&gt;
* Tables to update:&lt;br /&gt;
** player&lt;br /&gt;
** global (value with ID 2 is the active player)&lt;br /&gt;
** stats&lt;br /&gt;
** tables specific to your schema that use player_ids&lt;br /&gt;
* If your changes to player_ids are not taken into account, it may be a cache problem: use the &amp;quot;Clear PHP cache&amp;quot; button on your &amp;quot;Manage game&amp;quot; page.&lt;br /&gt;
* Then you should be able to play with the same state of the game as when the report was created in production.&lt;br /&gt;
* If the game has ended, you can place it again in the game state you want to debug by setting the value with ID 1 in the global table to the appropriate state value, and the value with ID 2 to the player you want active).&lt;br /&gt;
*&lt;br /&gt;
* Below is an example php function you may want to make. You can call this function from the chat window: LoadDebug()  &lt;br /&gt;
* change instances of 2308257, and 2308258 to you own BGA Studio logins YourLogin0 and YourLogin1&lt;br /&gt;
* change $id0 and $id1 to the player_ids from the table you want to debug, and have recently imported.&lt;br /&gt;
* Before you load Slot1, open a second tab with the table, because after loading the slot, that tab will be unusable. In the second tab you can call LoadDebug() in the chat window&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
	public function LoadDebug()&lt;br /&gt;
	{&lt;br /&gt;
		&lt;br /&gt;
		// These are the id&#039;s from the BGAtable I need to debug.&lt;br /&gt;
		$id0 = &#039;85268563&#039;;&lt;br /&gt;
		$id1 = &#039;85278138&#039;;	&lt;br /&gt;
		&lt;br /&gt;
		//player&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE player SET player_id=2308257 WHERE player_id = &#039;&amp;quot; . $id0 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE player SET player_id=2308258 WHERE player_id = &#039;&amp;quot; . $id1 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		&lt;br /&gt;
		//global &lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE global SET global_value=2308257 WHERE global_value = &#039;&amp;quot; . $id0 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE global SET global_value=2308258 WHERE global_value = &#039;&amp;quot; . $id1 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		&lt;br /&gt;
		//stats&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE stats SET stats_player_id=2308257 WHERE stats_player_id = &#039;&amp;quot; . $id0 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE stats SET stats_player_id=2308258 WHERE stats_player_id = &#039;&amp;quot; . $id1 . &amp;quot;&#039;&amp;quot; );			&lt;br /&gt;
		&lt;br /&gt;
		// &#039;other&#039; game specific tables. example:&lt;br /&gt;
		// tables specific to your schema that use player_ids&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE card SET card_location_arg=2308257 WHERE card_location_arg = &#039;&amp;quot; . $id0 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
		self::DbQuery(&amp;quot;UPDATE card SET card_location_arg=2308258 WHERE card_location_arg = &#039;&amp;quot; . $id1 . &amp;quot;&#039;&amp;quot; );&lt;br /&gt;
          }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelpturnthetide&amp;diff=5013</id>
		<title>Gamehelpturnthetide</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelpturnthetide&amp;diff=5013"/>
		<updated>2020-07-18T20:09:50Z</updated>

		<summary type="html">&lt;p&gt;Volker78: Undo revision 4990 by Volker78 (talk)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Objective =&lt;br /&gt;
Score the most points by playing cards that will keep your tide level low and your life preservers afloat through the rounds.&lt;br /&gt;
There are as many rounds as there are players.&lt;br /&gt;
The player with the most points at the end of the rounds wins the game.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Gameplay =&lt;br /&gt;
Twelve hands make up one complete round. Your number of life preservers is determined by what cards you have in hand. The distribution of life preservers may seem unfair. However, the players with more life preservers have a higher concentration of Weather cards that are more difficult to play.&lt;br /&gt;
&lt;br /&gt;
Each player chooses one Weather card from her hand. When all players have selected their cards, everyone simultaneously turns their chosen card face up and compares numbers.&lt;br /&gt;
&lt;br /&gt;
The player who played the highest number Weather card must take the lower Tide Level card from the two face up next to the deck. That Tide Level card is then placed face up in front of him so that all of the other players can see it.&lt;br /&gt;
&lt;br /&gt;
Next, the player who played the second highest Weather card must take the remaining Tide Level card and do the same.&lt;br /&gt;
&lt;br /&gt;
When you receive a new Tide Level card, it is placed on top of the old one, if there was one.&lt;br /&gt;
&lt;br /&gt;
The player who now has the highest Tide Level card showing among all players loses a life preserver. If two players tie for the highest Tide Level, then both must turn over a life preserver.&lt;br /&gt;
&lt;br /&gt;
All played Weather cards are then discarded and two new Tide Level cards are revealed next to the deck.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Round elimination =&lt;br /&gt;
If you loose your last life preserver, you get one last chance to stay in the round. You are only eliminated from the round when you loose once more (that is, when you must turn over another life preserver, but have none left to turn).&lt;br /&gt;
&lt;br /&gt;
If you are eliminated from the round, your Weather and Tide Level cards are discarded.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= End of a round and scoring =&lt;br /&gt;
A round ends after each player has played all 12 cards from his hand. Alternatively, the round ends instantly when there are only two players left in the game.&lt;br /&gt;
&lt;br /&gt;
At the end of the round, you are awarded one point for each remaining life preserver. If you have no life preservers, you get no points (0). If you were eliminated from the round because of a lack of life preservers, you receive one negative point (-1).&lt;br /&gt;
&lt;br /&gt;
In addition, the player who, at the end of the round, had the lowest Tide Level card showing, receives one additional bonus point. If two players are tied for the lowest Tide Level, then they each receive an additional point. A player with no Tide Level cards in his playing area has the lowest Tide Level.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Starting a new round =&lt;br /&gt;
Your initial 12 Weather cards are passed to the player on your left, as well as the corresponding life preservers.&lt;br /&gt;
The Tide Level cards are re-shuffle at the beginning of each round.&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Gamehelpturnthetide&amp;diff=4990</id>
		<title>Gamehelpturnthetide</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Gamehelpturnthetide&amp;diff=4990"/>
		<updated>2020-07-14T06:34:41Z</updated>

		<summary type="html">&lt;p&gt;Volker78: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Ziel =&lt;br /&gt;
Erziele die meisten Punkte, in dem Du Karten ausspielst, die Deine Flut niedrig halten und Deine Rettungsringe durch die Runden erhalten.&lt;br /&gt;
Es gibt so viele Runden wie es Spieler gibt.&lt;br /&gt;
Der Spieler mit den meisten Punkten am Ende der Runden gewinnt das Spiel.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Spielverlauf =&lt;br /&gt;
Zwölf Runden bilden einen kompletten Durchgang. Die Anzahl der Rettungsringe richtet sich danach, welche Karten Du auf der Hand hast. Die Verteilung der Rettungsringe mag ungerecht erscheinen. Die Spieler mit mehr Rettungsringen haben jedoch eine höhere Anzahl von Wetterkarten, die schwieriger zu spielen sind.&lt;br /&gt;
&lt;br /&gt;
Jeder Spieler wählt eine Wetterkarte aus seinem Blatt aus. Wenn alle Spieler ihre Karten ausgewählt haben, decken alle gleichzeitig ihre gewählte Karte auf und vergleichen die Zahlen.&lt;br /&gt;
&lt;br /&gt;
Der Spieler, der die Wetterkarte mit der höchsten Zahl gespielt hat, muss die Karte mit dem niedrigeren Flutniveau von den beiden aufgedeckten Karten neben dem Stapel nehmen. Diese Karte wird dann aufgedeckt vor ihm abgelegt, so dass alle anderen Spieler sie sehen können.&lt;br /&gt;
&lt;br /&gt;
Als nächstes muss der Spieler, der die zweithöchste Wetterkarte ausgespielt hat, die verbleibende Karte mit dem Flutniveau nehmen und dasselbe tun.&lt;br /&gt;
&lt;br /&gt;
Wenn Du eine neue Flutkarte erhältst, wird sie auf die alte Karte gelegt, falls es eine gab.&lt;br /&gt;
&lt;br /&gt;
Der Spieler, der nun die höchste der aufgedeckten Flutkarten hat, verliert einen Rettungsring. Wenn zwei Spieler bei Gleichstand die höchste Flutkarte haben, müssen beide Spieler einen Rettungsring umdrehen.&lt;br /&gt;
&lt;br /&gt;
Alle gespielten Wetterkarten werden dann abgelegt und zwei neue Flutkarten werden neben dem Stapel aufgedeckt.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Ausscheidung aus einer Runde =&lt;br /&gt;
Wenn Du Deinen letzten Rettungsring verlierst, bekommst Du eine letzte Chance, in der Runde zu bleiben. Du scheidest erst dann aus der Runde aus, wenn du noch einmal verlierst (d.h. wenn du einen anderen Rettungsring umdrehen musst, aber keinen mehr zum Drehen hast).&lt;br /&gt;
&lt;br /&gt;
Wenn Du aus der Runde ausscheidest, werden Deine Wetter- und Gezeitenkarten abgelegt.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Ende einer Runde und Wertung =&lt;br /&gt;
Eine Runde endet, nachdem jeder Spieler alle 12 Karten aus seiner Hand gespielt hat. Alternativ endet die Runde sofort, wenn nur noch zwei Spieler im Spiel sind.&lt;br /&gt;
&lt;br /&gt;
Am Ende der Runde erhält man für jeden verbleibenden Rettungsring einen Punkt. Wenn du keine Rettungsringe hast, bekommst du keine Punkte (0). Wenn du wegen fehlender Rettungsringe aus der Runde ausgeschieden bist, bekommst du einen Minuspunkt (-1).&lt;br /&gt;
&lt;br /&gt;
Darüber hinaus erhält der Spieler, der am Ende der Runde die Karte mit dem niedrigsten Flutniveau ausliegen hat, einen zusätzlichen Bonuspunkt. Wenn zwei Spieler für die niedrigste Flutkarte gleichauf liegen, erhält jeder von ihnen einen zusätzlichen Punkt. Ein Spieler ohne Flutkarte in seinem Spielbereich hat das niedrigste Flutniveau.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Beginn einer neuen Runde =&lt;br /&gt;
Deine ersten 12 Wetterkarten sowie die entsprechenden Rettungsringe werden an den Spieler zu deiner Linken weitergegeben.&lt;br /&gt;
Die Flutkarten werden zu Beginn jeder Runde neu gemischt.&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
	<entry>
		<id>https://en.doc.boardgamearena.com/index.php?title=Your_game_state_machine:_states.inc.php&amp;diff=4983</id>
		<title>Your game state machine: states.inc.php</title>
		<link rel="alternate" type="text/html" href="https://en.doc.boardgamearena.com/index.php?title=Your_game_state_machine:_states.inc.php&amp;diff=4983"/>
		<updated>2020-07-13T19:33:41Z</updated>

		<summary type="html">&lt;p&gt;Volker78: It was not clear, if using private-args in description messages are ok, but it seems so after testing.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Studio_Framework_Navigation}}&lt;br /&gt;
&lt;br /&gt;
This file describes the state machine of your game (all the game states properties, and the transitions to get from one state to another).&lt;br /&gt;
&lt;br /&gt;
Important: to understand the game state machine, it&#039;s recommended that you read this presentation first:&lt;br /&gt;
&lt;br /&gt;
[http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine Focus on BGA game state machine]&lt;br /&gt;
&lt;br /&gt;
== Overall structure ==&lt;br /&gt;
&lt;br /&gt;
The machine states are described by a PHP associative array.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
$machinestates = array(&lt;br /&gt;
&lt;br /&gt;
    // The initial state. Please do not modify.&lt;br /&gt;
    1 =&amp;gt; array(&lt;br /&gt;
        &amp;quot;name&amp;quot; =&amp;gt; &amp;quot;gameSetup&amp;quot;,&lt;br /&gt;
        &amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&amp;quot;Game setup&amp;quot;),&lt;br /&gt;
        &amp;quot;type&amp;quot; =&amp;gt; &amp;quot;manager&amp;quot;,&lt;br /&gt;
        &amp;quot;action&amp;quot; =&amp;gt; &amp;quot;stGameSetup&amp;quot;,&lt;br /&gt;
        &amp;quot;transitions&amp;quot; =&amp;gt; array( &amp;quot;&amp;quot; =&amp;gt; 2 )&lt;br /&gt;
    ),&lt;br /&gt;
    &lt;br /&gt;
    // Note: ID=2 =&amp;gt; your first state&lt;br /&gt;
&lt;br /&gt;
    2 =&amp;gt; array(&lt;br /&gt;
    		&amp;quot;name&amp;quot; =&amp;gt; &amp;quot;playerTurn&amp;quot;,&lt;br /&gt;
    		&amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} must play a card or pass&#039;),&lt;br /&gt;
    		&amp;quot;descriptionmyturn&amp;quot; =&amp;gt; clienttranslate(&#039;${you} must play a card or pass&#039;),&lt;br /&gt;
    		&amp;quot;type&amp;quot; =&amp;gt; &amp;quot;activeplayer&amp;quot;,&lt;br /&gt;
    		&amp;quot;possibleactions&amp;quot; =&amp;gt; array( &amp;quot;playCard&amp;quot;, &amp;quot;pass&amp;quot; ),&lt;br /&gt;
    		&amp;quot;transitions&amp;quot; =&amp;gt; array( &amp;quot;playCard&amp;quot; =&amp;gt; 2, &amp;quot;pass&amp;quot; =&amp;gt; 2 )&lt;br /&gt;
    ),&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Syntax ==&lt;br /&gt;
&lt;br /&gt;
=== id ===&lt;br /&gt;
&lt;br /&gt;
The keys determine game state IDs (in the example above: 1 and 2).&lt;br /&gt;
&lt;br /&gt;
IDs must be positive integers.&lt;br /&gt;
&lt;br /&gt;
ID=1 is reserved for the first game state and should not be used (and you must not modify it).&lt;br /&gt;
&lt;br /&gt;
ID=99 is reserved for the last game state (end of the game) (and you must not modify it).&lt;br /&gt;
&lt;br /&gt;
Note: you may use any ID, even an ID greater than 100. But you cannot use 1 or 99.&lt;br /&gt;
&lt;br /&gt;
Note²: You must not use the same ID twice.&lt;br /&gt;
&lt;br /&gt;
Note³: When a game is in prod and you change the ID of a state, all active games (including many turn based) will behave unpredictably.&lt;br /&gt;
&lt;br /&gt;
=== name ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
The name of a game state is used to identify it in your game logic.&lt;br /&gt;
&lt;br /&gt;
Several game states can share the same name; however, this is not recommended.&lt;br /&gt;
&lt;br /&gt;
Warning! Do not put spaces in the name. This could cause unexpected problems in some cases.&lt;br /&gt;
&lt;br /&gt;
PHP example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
// Get current game state&lt;br /&gt;
$state = $this-&amp;gt;gamestate-&amp;gt;state();&lt;br /&gt;
if( $state[&#039;name&#039;] == &#039;myGameState&#039; )&lt;br /&gt;
{&lt;br /&gt;
...&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
JS example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        onEnteringState: function( stateName, args )&lt;br /&gt;
        {&lt;br /&gt;
            console.log( &#039;Entering state: &#039;+stateName );&lt;br /&gt;
            &lt;br /&gt;
            switch( stateName )&lt;br /&gt;
            case &#039;myGameState&#039;:&lt;br /&gt;
            &lt;br /&gt;
                // Do some stuff at the beginning at this game state&lt;br /&gt;
                ....&lt;br /&gt;
                &lt;br /&gt;
                break;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== type ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
You can use 3 types of game states:&lt;br /&gt;
* activeplayer (1 player is active and must play.)&lt;br /&gt;
* multipleactiveplayer (1..N players can be active and must play.)&lt;br /&gt;
* game (No player is active. This is a transitional state to do something automatic specified by the game rules.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; Make sure you don&#039;t mistype the value of this attribute. If you do (e.g. &#039;multiactiveplayer&#039; instead of &#039;multipleactiveplayer&#039;), things won&#039;t work, and you might have a hard time figuring out why.&lt;br /&gt;
&lt;br /&gt;
=== description ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
The description is the string that is displayed in the main action bar (top of the screen) when the state is active.&lt;br /&gt;
&lt;br /&gt;
When a string is specified as a description, you must use &amp;quot;clienttranslate&amp;quot; in order for the string to be translated on the client side:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
 		&amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} must play a card or pass&#039;),&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the description string, you can use ${actplayer} to refer to the active player.&lt;br /&gt;
&lt;br /&gt;
You can also use custom arguments in your description. These custom arguments correspond to values returned by your &amp;quot;args&amp;quot; PHP method (see below &amp;quot;args&amp;quot; field).&lt;br /&gt;
&lt;br /&gt;
Example of custom field:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In states.inc.php:&lt;br /&gt;
        &amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} must choose ${nbr} identical energies&#039;),&lt;br /&gt;
        &amp;quot;args&amp;quot; =&amp;gt; &amp;quot;argMyArgumentMethod&amp;quot;&lt;br /&gt;
&lt;br /&gt;
In mygame.game.php:&lt;br /&gt;
    function argMyArgumentMethod()&lt;br /&gt;
    {&lt;br /&gt;
        return array(&lt;br /&gt;
            &#039;nbr&#039; =&amp;gt; 2  // In this case ${nbr} in the description will be replaced by &amp;quot;2&amp;quot;&lt;br /&gt;
        );    &lt;br /&gt;
    }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: You may specify an empty string (&amp;quot;&amp;quot;) here if it never happens that the game remains in this state (i.e., if this state immediately jumps to another state when activated).&lt;br /&gt;
&lt;br /&gt;
Note²: Usually, you specify a string for &amp;quot;activeplayer&amp;quot; and &amp;quot;multipleactiveplayer&amp;quot; game states, and you specify an empty string for &amp;quot;game&amp;quot; game states. BUT, if you are using synchronous notifications, the client can remain on a &amp;quot;game&amp;quot; type game state for a few seconds, and in this case it may be useful to display a description in the status bar while in this state.&lt;br /&gt;
&lt;br /&gt;
=== descriptionmyturn ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039; when the state type is &amp;quot;activeplayer&amp;quot; or &amp;quot;multipleactiveplayer&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
&amp;quot;descriptionmyturn&amp;quot; has exactly the same role and properties as &amp;quot;description&amp;quot;, except that this value is displayed to the current active player - or to all active players in case of a multipleactiveplayer game state.&lt;br /&gt;
&lt;br /&gt;
In general, we have this situation:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        &amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} can take some actions&#039;),&lt;br /&gt;
        &amp;quot;descriptionmyturn&amp;quot; =&amp;gt; clienttranslate(&#039;${you} can take some actions&#039;),&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: you can use ${you} in descriptionmyturn so the description will display &amp;quot;You&amp;quot; instead of the name of the player.&lt;br /&gt;
&lt;br /&gt;
=== action ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039; when the state type is &amp;quot;game.&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
&amp;quot;action&amp;quot; specifies a PHP method to call when entering this game state.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
In states.inc.php:&lt;br /&gt;
    28 =&amp;gt; array(&lt;br /&gt;
        &amp;quot;name&amp;quot; =&amp;gt; &amp;quot;startPlayerTurn&amp;quot;,&lt;br /&gt;
        &amp;quot;description&amp;quot; =&amp;gt; &#039;&#039;,&lt;br /&gt;
        &amp;quot;type&amp;quot; =&amp;gt; &amp;quot;game&amp;quot;,&lt;br /&gt;
        &amp;quot;action&amp;quot; =&amp;gt; &amp;quot;stStartPlayerTurn&amp;quot;,&lt;br /&gt;
&lt;br /&gt;
In mygame.game.php:&lt;br /&gt;
    function stStartPlayerTurn()&lt;br /&gt;
    {   &lt;br /&gt;
        // ... do something at the beginning of this game state&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Usually, for a &amp;quot;game&amp;quot; state type, the action method is used to perform automatic functions specified by the rules (for example: check victory conditions, deal cards for a new round, go to the next player, etc.) and then jump to another game state.&lt;br /&gt;
&lt;br /&gt;
Note: a BGA convention specifies that PHP methods called with &amp;quot;action&amp;quot; are prefixed by &amp;quot;st&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
Note: this field CAN be used for player states to set something up; e.g., for multiplayer states, it can make all players active.&lt;br /&gt;
&lt;br /&gt;
=== transitions ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
With &amp;quot;transitions&amp;quot; you specify which game state(s) you can jump to from a given game state.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    25 =&amp;gt; array(&lt;br /&gt;
        &amp;quot;name&amp;quot; =&amp;gt; &amp;quot;myGameState&amp;quot;,&lt;br /&gt;
        &amp;quot;transitions&amp;quot; =&amp;gt; array( &amp;quot;nextPlayer&amp;quot; =&amp;gt; 27, &amp;quot;endRound&amp;quot; =&amp;gt; 39 ),&lt;br /&gt;
        ....&lt;br /&gt;
    }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In the example above, if &amp;quot;myGameState&amp;quot; is the current active game state, I can jump to the game state with ID 27 or the game state with ID 39.&lt;br /&gt;
&lt;br /&gt;
Example to jump to ID 27:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
In mygame.game.php:&lt;br /&gt;
    $this-&amp;gt;gamestate-&amp;gt;nextState( &amp;quot;nextPlayer&amp;quot; );&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Important: &amp;quot;nextPlayer&amp;quot; is the name of the transition, and NOT the name of the target game state. Multiple transitions can lead to the same game state.&lt;br /&gt;
&lt;br /&gt;
Note: If there is only 1 transition, you may give it an empty name.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
In states.inc.php:&lt;br /&gt;
    &amp;quot;transitions&amp;quot; =&amp;gt; array( &amp;quot;&amp;quot; =&amp;gt; 27 ),&lt;br /&gt;
&lt;br /&gt;
In mygame.game.php:&lt;br /&gt;
    $this-&amp;gt;gamestate-&amp;gt;nextState(  );     // We don&#039;t need to specify a transition as there is only one here&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== possibleactions ===&lt;br /&gt;
&lt;br /&gt;
(&#039;&#039;&#039;Mandatory&#039;&#039;&#039; when the game state is &amp;quot;activeplayer&amp;quot; or &amp;quot;multipleactiveplayer&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
&amp;quot;possibleactions&amp;quot; defines the actions possible by the players in this game state, and ensures they cannot cannot perform actions that are not allowed in this state.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
In states.game.php:&lt;br /&gt;
       	&amp;quot;possibleactions&amp;quot; =&amp;gt; array( &amp;quot;playCard&amp;quot;, &amp;quot;pass&amp;quot; ),&lt;br /&gt;
&lt;br /&gt;
In mygame.game.php:&lt;br /&gt;
        function playCard( ...)&lt;br /&gt;
        {&lt;br /&gt;
             self::checkAction( &amp;quot;playCard&amp;quot; );    // Will fail if &amp;quot;playCard&amp;quot; is not specified in &amp;quot;possibleactions&amp;quot; in the current game state.&lt;br /&gt;
&lt;br /&gt;
            ....&lt;br /&gt;
&lt;br /&gt;
In mygame.js:&lt;br /&gt;
        playCard: function( ... )&lt;br /&gt;
        {&lt;br /&gt;
            if( this.checkAction( &amp;quot;playCard&amp;quot; ) ) // Will fail if &amp;quot;playCard&amp;quot; is not specified in &amp;quot;possibleactions&amp;quot; in the current game state.&lt;br /&gt;
            {  return ;   }&lt;br /&gt;
&lt;br /&gt;
            ....&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== args ===&lt;br /&gt;
&lt;br /&gt;
(optional)&lt;br /&gt;
&lt;br /&gt;
Sometimes it happens that you need some information on the client side (i.e., for your game interface) only for a specific game state.&lt;br /&gt;
&lt;br /&gt;
Example 1 : in &#039;&#039;Reversi&#039;&#039;, the list of possible moves during the playerTurn state.&lt;br /&gt;
Example 2 : in &#039;&#039;Caylus&#039;&#039;, the number of remaining king&#039;s favors to choose in the state where the player is choosing a favor.&lt;br /&gt;
Example 3 : in &#039;&#039;Can&#039;t Stop&#039;&#039;, the list of possible die combinations to be displayed to the active player so that he can choose from among them.&lt;br /&gt;
&lt;br /&gt;
In such a situation, you can specify a method name as the « args » argument for your game state. This method must retrieve some piece of information about the game (example: for &#039;&#039;Reversi&#039;&#039;, the list of possible moves) and return it.&lt;br /&gt;
&lt;br /&gt;
Thus, this data can be transmitted to the clients and used by the clients to display it. It should always be an associative array.&lt;br /&gt;
&lt;br /&gt;
Let&#039;s see a complete example using args with « Reversi » game :&lt;br /&gt;
&lt;br /&gt;
In states.inc.php, we specify an « args » argument for gamestate « playerTurn » :&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    10 =&amp;gt; array(&lt;br /&gt;
        &amp;quot;name&amp;quot; =&amp;gt; &amp;quot;playerTurn&amp;quot;,&lt;br /&gt;
		&amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} must play a disc&#039;),&lt;br /&gt;
		&amp;quot;descriptionmyturn&amp;quot; =&amp;gt; clienttranslate(&#039;${you} must play a disc&#039;),&lt;br /&gt;
        &amp;quot;type&amp;quot; =&amp;gt; &amp;quot;activeplayer&amp;quot;,&lt;br /&gt;
        &amp;quot;args&amp;quot; =&amp;gt; &amp;quot;argPlayerTurn&amp;quot;,    &amp;lt;================================== HERE&lt;br /&gt;
        &amp;quot;possibleactions&amp;quot; =&amp;gt; array( &#039;playDisc&#039; ),&lt;br /&gt;
        &amp;quot;transitions&amp;quot; =&amp;gt; array( &amp;quot;playDisc&amp;quot; =&amp;gt; 11, &amp;quot;zombiePass&amp;quot; =&amp;gt; 11 )&lt;br /&gt;
    ),&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It corresponds to a « argPlayerTurn » method in our PHP code (reversi.game.php):&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    function argPlayerTurn()   {&lt;br /&gt;
        return array(&lt;br /&gt;
            &#039;possibleMoves&#039; =&amp;gt; self::getPossibleMoves()&lt;br /&gt;
        );&lt;br /&gt;
    }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Then, when we enter into the « playerTurn » game state on the client side, we can highlight the possible moves on the board using information returned by argPlayerTurn :&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
        onEnteringState: function( stateName, args )  {&lt;br /&gt;
           console.log( &#039;Entering state: &#039;+stateName );&lt;br /&gt;
            &lt;br /&gt;
            switch( stateName )  {&lt;br /&gt;
            case &#039;playerTurn&#039;:&lt;br /&gt;
                this.updatePossibleMoves( args.args.possibleMoves );&lt;br /&gt;
                break;&lt;br /&gt;
            }&lt;br /&gt;
        },&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note: you can also use values returned by your &amp;quot;args&amp;quot; method to have some custom values in your &amp;quot;description&amp;quot;/&amp;quot;descriptionmyturn&amp;quot; (see above).&lt;br /&gt;
&lt;br /&gt;
Note: as a BGA convention, PHP methods called with &amp;quot;args&amp;quot; are prefixed by &amp;quot;arg&amp;quot; (example: argPlayerTurn).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Warning&#039;&#039;&#039;: the &amp;quot;args&amp;quot; method can be called before the &amp;quot;action&amp;quot; method so don&#039;t expect data modifications by the &amp;quot;action&amp;quot; method to be available in the &amp;quot;args&amp;quot; method!&lt;br /&gt;
&lt;br /&gt;
==== Private info in args ====&lt;br /&gt;
&lt;br /&gt;
By default, all data provided through this method are PUBLIC TO ALL PLAYERS. Please do not send any private data with this method, as a cheater could see it even it is not used explicitly by the game interface logic.&lt;br /&gt;
&lt;br /&gt;
However, it is possible to specify that some data should be sent to specific players only.&lt;br /&gt;
&lt;br /&gt;
Example 1: send information to active player(s) only:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    function argPlayerTurn()  {&lt;br /&gt;
        return array(&lt;br /&gt;
            &#039;_private&#039; =&amp;gt; array(          // Using &amp;quot;_private&amp;quot; keyword, all data inside this array will be made private&lt;br /&gt;
&lt;br /&gt;
                &#039;active&#039; =&amp;gt; array(       // Using &amp;quot;active&amp;quot; keyword inside &amp;quot;_private&amp;quot;, you select active player(s)&lt;br /&gt;
                    &#039;somePrivateData&#039; =&amp;gt; self::getSomePrivateData()   // will be send only to active player(s)&lt;br /&gt;
                )&lt;br /&gt;
            ),&lt;br /&gt;
&lt;br /&gt;
            &#039;possibleMoves&#039; =&amp;gt; self::getPossibleMoves()          // will be sent to all players&lt;br /&gt;
        );&lt;br /&gt;
    }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Inside the js file, these variables will be available through `args.args._private`. (e.g. `args.args._private.somePrivateData` -- it is not `args._private.active.somePrivateData` nor is it `args.somePrivateData`)&lt;br /&gt;
&lt;br /&gt;
Example 2: send information to a specific player (&amp;lt;specific_player_id&amp;gt;) only:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
    function argPlayerTurn()  {&lt;br /&gt;
        return array(&lt;br /&gt;
            &#039;_private&#039; =&amp;gt; array(          // Using &amp;quot;_private&amp;quot; keyword, all data inside this array will be made private&lt;br /&gt;
&lt;br /&gt;
                &amp;lt;specific_player_id&amp;gt; =&amp;gt; array(       // select one specific player by id&lt;br /&gt;
                    &#039;somePrivateData&#039; =&amp;gt; self::getSomePrivateData()   // will be sent only to &amp;lt;specific_player_id&amp;gt;&lt;br /&gt;
                )&lt;br /&gt;
            ),&lt;br /&gt;
&lt;br /&gt;
            &#039;possibleMoves&#039; =&amp;gt; self::getPossibleMoves()          // will be sent to all players&lt;br /&gt;
        );&lt;br /&gt;
    }&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
IMPORTANT: in certain situations (example: &amp;quot;multipleactiveplayer&amp;quot; game state) these &amp;quot;private data&amp;quot; features can have a significant impact on performance. Please do not use if not needed.&lt;br /&gt;
&lt;br /&gt;
It is also possible to use these private args in the &amp;quot;description&amp;quot; messages, like &amp;quot;${you} have to play ${_private.count} cards&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
=== updateGameProgression ===&lt;br /&gt;
&lt;br /&gt;
(optional)&lt;br /&gt;
&lt;br /&gt;
If you specify &amp;quot;updateGameProgression =&amp;gt; true&amp;quot; in a game state, your &amp;quot;getGameProgression&amp;quot; PHP method will be called at the beginning of this game state - and thus the game progression of the game will be updated.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;At least one&#039;&#039; of your game states (any one) must specify &amp;quot;updateGameProgression=&amp;gt;true&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Implementation Notes ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Using Named Constants for States ===&lt;br /&gt;
&lt;br /&gt;
Using numeric constants is prone to errors. If you want you can declare state constants as PHP named constants. This way you can&lt;br /&gt;
use them in the states file and in game.php as well&lt;br /&gt;
&lt;br /&gt;
EXAMPLE:&lt;br /&gt;
&lt;br /&gt;
states.inc.php:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
// define contants for state ids&lt;br /&gt;
if (!defined(&#039;STATE_END_GAME&#039;)) { // ensure this block is only invoked once, since it is included multiple times&lt;br /&gt;
   define(&amp;quot;STATE_PLAYER_TURN&amp;quot;, 2);&lt;br /&gt;
   define(&amp;quot;STATE_GAME_TURN&amp;quot;, 3);&lt;br /&gt;
   define(&amp;quot;STATE_PLAYER_TURN_CUBES&amp;quot;, 4);&lt;br /&gt;
   define(&amp;quot;STATE_END_GAME&amp;quot;, 99);&lt;br /&gt;
}&lt;br /&gt;
 &lt;br /&gt;
$machinestates = array(&lt;br /&gt;
&lt;br /&gt;
   ...&lt;br /&gt;
&lt;br /&gt;
    STATE_PLAYER_TURN =&amp;gt; array(&lt;br /&gt;
    		&amp;quot;name&amp;quot; =&amp;gt; &amp;quot;playerTurn&amp;quot;,&lt;br /&gt;
    		&amp;quot;description&amp;quot; =&amp;gt; clienttranslate(&#039;${actplayer} must select an Action Space or Pass&#039;),&lt;br /&gt;
    		&amp;quot;descriptionmyturn&amp;quot; =&amp;gt; clienttranslate(&#039;${you} must select an Action Space or Pass&#039;),&lt;br /&gt;
    		&amp;quot;type&amp;quot; =&amp;gt; &amp;quot;activeplayer&amp;quot;,&lt;br /&gt;
                &amp;quot;args&amp;quot; =&amp;gt; &#039;arg_playerTurn&#039;,&lt;br /&gt;
    		&amp;quot;possibleactions&amp;quot; =&amp;gt; array( &amp;quot;selectWorkerAction&amp;quot;, &amp;quot;pass&amp;quot; ),&lt;br /&gt;
    		&amp;quot;transitions&amp;quot; =&amp;gt; array( &lt;br /&gt;
    		        &amp;quot;loopback&amp;quot; =&amp;gt; STATE_PLAYER_TURN,&lt;br /&gt;
    		        &amp;quot;playCubes&amp;quot; =&amp;gt; STATE_PLAYER_TURN_CUBES,&lt;br /&gt;
    		        &amp;quot;pass&amp;quot; =&amp;gt; STATE_GAME_TURN )&lt;br /&gt;
    ),&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Example of multipleactiveplayer state ===&lt;br /&gt;
&lt;br /&gt;
This is an example of a multipleactiveplayer state:&lt;br /&gt;
&lt;br /&gt;
  2 =&amp;gt;  array (&lt;br /&gt;
    &#039;name&#039; =&amp;gt; &#039;playerTurnSetup&#039;,&lt;br /&gt;
    &#039;type&#039; =&amp;gt; &#039;multipleactiveplayer&#039;,&lt;br /&gt;
    &#039;description&#039; =&amp;gt; clienttranslate(&#039;Other players must choose one Objective&#039;),&lt;br /&gt;
    &#039;descriptionmyturn&#039; =&amp;gt; clienttranslate(&#039;${you} must choose one Objective card to keep&#039;),&lt;br /&gt;
    &#039;possibleactions&#039; =&amp;gt;     array (&#039;playKeep&#039; ),&lt;br /&gt;
    &#039;transitions&#039; =&amp;gt;    array (       &#039;next&#039; =&amp;gt; 5, &#039;loopback&#039; =&amp;gt; 2, ),&lt;br /&gt;
    &#039;action&#039; =&amp;gt; &#039;st_MultiPlayerInit&#039;,&lt;br /&gt;
    &#039;args&#039; =&amp;gt; &#039;arg_playerTurnSetup&#039;,&lt;br /&gt;
  ),&lt;br /&gt;
&lt;br /&gt;
In game.php:&lt;br /&gt;
    // this will make all players multiactive just before entering the state&lt;br /&gt;
    function st_MultiPlayerInit() {&lt;br /&gt;
        $this-&amp;gt;gamestate-&amp;gt;setAllPlayersMultiactive();&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
When ending the player action, instead of a state transition, deactivate player.&lt;br /&gt;
&lt;br /&gt;
    function action_playKeep($cardId) {&lt;br /&gt;
        $this-&amp;gt;checkAction(&#039;playKeep&#039;);&lt;br /&gt;
        $player_id = $this-&amp;gt;getCurrentPlayerId(); // CURRENT!!! not active&lt;br /&gt;
        ... // some logic here&lt;br /&gt;
        $this-&amp;gt;gamestate-&amp;gt;setPlayerNonMultiactive($player_id, &#039;next&#039;); // deactivate player; if none left, transition to &#039;next&#039; state&lt;br /&gt;
    }&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Diffrence between Single active and Multi active states ===&lt;br /&gt;
In a classic &amp;quot;activePlayer&amp;quot; state:&lt;br /&gt;
&lt;br /&gt;
* You cannot change the active player DURING the state. This is to ensure that during 1 activePlayer state, only ONE player is active&lt;br /&gt;
* As a consequence, you must set the active player BEFORE entering the activePlayer state&lt;br /&gt;
* Finally, during onEnteringState, on JS side, the active player is signaled as active and the information is reliable and usable.&lt;br /&gt;
&lt;br /&gt;
In a &amp;quot;multiplePlayer&amp;quot; state:&lt;br /&gt;
&lt;br /&gt;
* You can (and must) change the active players DURING the state&lt;br /&gt;
* During such a state, players can be activated/desactivated anytime during the state, giving you the maximum of possibilities.&lt;br /&gt;
* You shouldn&#039;t set actives player before entering the state. But you can set it in &amp;quot;state initialized&amp;quot; php function (see example above st_MultiPlayerInit)&lt;br /&gt;
* Finally, during onEnteringState, on JS side, the active players are NOT actives yet so you must use onUpdateActionButtons to perform the client side operation which depends on a player active/unactive status.&lt;/div&gt;</summary>
		<author><name>Volker78</name></author>
	</entry>
</feed>