Main game logic: yourgamename.game.php - 편집 역사

Archduke: /* Notify players */

2014-06-15T21:03:48Z

Notify players

← 이전 판		2014년 6월 15일 (일) 23:03 판
328번째 줄:		328번째 줄:
	If you define a real string here, you should use "clienttranslate" method to make sure it can be translate.		If you define a real string here, you should use "clienttranslate" method to make sure it can be translate.

	You can use arguments in your notification_log strings, that refers to values defines in the "notification_args" argument (see below).		You can use arguments in your notification_log strings, that refers to values defines in the "notification_args" argument (see below). NB: Make sure you only use single quotes ('), otherwise PHP will try to interpolate the variable and will ignore the values in the args array.

	Note: you CAN use some HTML inside your notification log, and it is working. However:		Note: you CAN use some HTML inside your notification log, and it is working. However:

Archduke: /* Accessing database */

2014-06-08T08:51:18Z

Accessing database

← 이전 판		2014년 6월 8일 (일) 10:51 판
66번째 줄:		66번째 줄:
	: This is the generic method to access the database.		: This is the generic method to access the database.
	: It can execute any type of SELECT/UPDATE/DELETE/REPLACE query on the database.		: It can execute any type of SELECT/UPDATE/DELETE/REPLACE query on the database.
	: You should use it for UPDATE/DELETE/REPLACE query. For SELECT queries, the specialized methods ~~above~~ are much better.		: You should use it for UPDATE/DELETE/REPLACE query. For SELECT queries, the specialized methods below are much better.

	; getUniqueValueFromDB( $sql )		; getUniqueValueFromDB( $sql )

Sourisdudesert: /* File Structure */

2014-01-06T09:00:34Z

File Structure

← 이전 판		2014년 1월 6일 (월) 11:00 판
13번째 줄:		13번째 줄:
	* Utility functions: your utility functions.		* Utility functions: your utility functions.
	* Player actions: the entry points for players actions.		* Player actions: the entry points for players actions.
	* Game state arguments: methods to return additional data on specific game states.		* Game state arguments: methods to return additional data on specific game states ([http://en.doc.boardgamearena.com/Your_game_state_machine:_states.inc.php#args more info here]).
	* Game state actions: the logic to run when entering a new game state.		* Game state actions: the logic to run when entering a new game state ([http://en.doc.boardgamearena.com/Your_game_state_machine:_states.inc.php#action more info here]).
	* zombieTurn: what to do it's the turn of a zombie player.		* zombieTurn: what to do it's the turn of a zombie player.

Sourisdudesert: /* Player elimination */

2014-01-06T08:53:15Z

Player elimination

← 이전 판		2014년 1월 6일 (월) 10:53 판
506번째 줄:		506번째 줄:
	In some games, this is useful to eliminate a player from the game in order he/she can start another game without waiting for the current game end.		In some games, this is useful to eliminate a player from the game in order he/she can start another game without waiting for the current game end.

	This case should be rare. Please don't use player elimination feature if some player just has to wait the last 10% of the game for game end. This feature is		This case should be rare. Please don't use player elimination feature if some player just has to wait the last 10% of the game for game end. This feature should be used only in games where players are eliminated all along the game (typical examples: "Perudo" or "The Werewolves of Miller's Hollow").

			Usage:

			* Player to eliminate should NOT be active anymore (preferably use the feature in a "game" type game state).
			* In your PHP code:
			self::eliminatePlayer( <player_to_eliminate_id> );
			* the player is informed in a dialog box that he no longer have to played and can start another game if he/she wants too (whith buttons "stay at this table" "quit table and back to main site"). In any case, the player is free to tart&join another table from now.
			* When your game is over, all players who have been eliminated before receive a "notification" (the small "!" icon on the top right of the BGA interface) that indicate them that "the game has ended" and invite them to review the game results.

2014년 1월 6일 (월) 08:45에 Sourisdudesert님의 편집

2014-01-06T08:45:43Z

← 이전 판		2014년 1월 6일 (월) 10:45 판
501번째 줄:		501번째 줄:

	Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.		Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.

			== Player elimination ==

			In some games, this is useful to eliminate a player from the game in order he/she can start another game without waiting for the current game end.

			This case should be rare. Please don't use player elimination feature if some player just has to wait the last 10% of the game for game end. This feature is

Sourisdudesert: /* Manage player scores and Tie breaker */

2013-09-30T16:32:23Z

Manage player scores and Tie breaker

← 이전 판		2013년 9월 30일 (월) 18:32 판
423번째 줄:		423번째 줄:
	Tie breaker score is displayed only for players who are tied at the end of the game. Most of the time, it is not supposed to be displayed explicitly during the game.		Tie breaker score is displayed only for players who are tied at the end of the game. Most of the time, it is not supposed to be displayed explicitly during the game.

	When you are using "player_score_aux" functionality, you must describe the formula to use in your ~~Constructor method~~ like this:		When you are using "player_score_aux" functionality, you must describe the formula to use in your gameinfos.inc.php file like this:

	<pre>		<pre>
	~~$this->~~tie_breaker_description = ~~self::_~~("Describe here your tie breaker formula");		'tie_breaker_description' => totranslate("Describe here your tie breaker formula"),
	</pre>		</pre>

2013년 5월 22일 (수) 09:01에 Sourisdudesert님의 편집

2013-05-22T09:01:51Z

← 이전 판		2013년 5월 22일 (수) 11:01 판
454번째 줄:		454번째 줄:


	; throw new ~~BgaSystemVisibleException~~ ( $error_message)		; throw new BgaVisibleSystemException ( $error_message)
	: You must throw this exception when you detect something that is not supposed to happened into your code.		: You must throw this exception when you detect something that is not supposed to happened into your code.
	: The error message is shown to the user as an "Unexpected error", in order he can report it in the forum.		: The error message is shown to the user as an "Unexpected error", in order he can report it in the forum.
496번째 줄:		496번째 줄:
	}		}
	else		else
	throw new ~~BgaSystemVisibleException~~( "Zombie mode not supported at this game state: ".$statename );		throw new BgaVisibleSystemException( "Zombie mode not supported at this game state: ".$statename );
	}		}
	</pre>		</pre>

	Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.		Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.

Tilalilalou: /* Zombie mode */

2013-05-21T16:24:52Z

Zombie mode

← 이전 판		2013년 5월 21일 (화) 18:24 판
496번째 줄:		496번째 줄:
	}		}
	else		else
	throw new ~~feException~~( "Zombie mode not supported at this game state: ".$statename );		throw new BgaSystemVisibleException( "Zombie mode not supported at this game state: ".$statename );
	}		}
	</pre>		</pre>

	Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.		Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.

Pikiou: /* Game states and active players */ Precision on setPlayersMultiactive

2013-04-18T14:32:20Z

Game states and active players: Precision on setPlayersMultiactive

← 이전 판		2013년 4월 18일 (목) 16:32 판
259번째 줄:		259번째 줄:
	; $this->gamestate->setPlayersMultiactive( $players, $next_state )		; $this->gamestate->setPlayersMultiactive( $players, $next_state )
	: Make a specific list of players active during a multiactive gamestate.		: Make a specific list of players active during a multiactive gamestate.
			: Bare in mind it doesn't deactivate other previously active players.
	: "players" is the array of player id that should be made active.		: "players" is the array of player id that should be made active.
	: In case "players" is empty, the method trigger the "next_state" transition to go to the next game state.		: In case "players" is empty, the method trigger the "next_state" transition to go to the next game state.

Sourisdudesert: /* Zombie mode */

2013-03-06T15:35:34Z

Zombie mode

← 이전 판		2013년 3월 6일 (수) 17:35 판
498번째 줄:		498번째 줄:
	}		}
	</pre>		</pre>

			Note that in the example above, all corresponding game state should implement "zombiePass" as a transition.