Game meta-information: gameinfos.jsonc - Revision history

N e s s u n o: /* Minimum screen size */

2026-08-07T07:42:30Z

Minimum screen size

← Older revision		Revision as of 09:42, 7 August 2026
Line 50:		Line 50:

	== Minimum screen size ==		== Minimum screen size ==
	The settings to specify mobile (or small desktop) screen size ~~if detailled~~ here:		The settings to specify mobile (or small desktop) screen size is detailed here:
	https://en.doc.boardgamearena.com/Your_game_mobile_version		https://en.doc.boardgamearena.com/Your_game_mobile_version

Thoun at 10:17, 20 April 2026

2026-04-20T10:17:12Z

← Older revision		Revision as of 12:17, 20 April 2026
Line 19:		Line 19:
	These fields should match the publisher of the game. In the case of a public domain name, they should be left empty (empty string)		These fields should match the publisher of the game. In the case of a public domain name, they should be left empty (empty string)

	~~==Beta==~~

	~~You are not allowed to set the "'''is_beta'''" to 0 before the game has been released on BGA and stabilized.~~
	==Time Profiles==		==Time Profiles==
	'''fast/medium/slow_additional_time''': please set high values here: after the game has been released, there is a process that adjusts these values to match the real game duration. Adjustment starts when the game enters beta, after that these have no effect, and require admin intervention to change.		'''fast/medium/slow_additional_time''': please set high values here: after the game has been released, there is a process that adjusts these values to match the real game duration. Adjustment starts when the game enters beta, after that these have no effect, and require admin intervention to change.
Line 28:		Line 25:

	'''players'''		'''players'''
	'players~~' => array(~~ 3, 4, 6 ),		"players": [3, 4, 6],

	*during the first step of development of a game, it is recommended to have a "1 player" configuration: it is much easier to start/stop a game this way, as you don't need to switch players.		*during the first step of development of a game, it is recommended to have a "1 player" configuration: it is much easier to start/stop a game this way, as you don't need to switch players.
Line 35:		Line 32:

	'''suggest_player_number''' / '''not_recommend_player_number'''		'''suggest_player_number''' / '''not_recommend_player_number'''
	'suggest_player_number~~' =>~~ 3,		"suggest_player_number": 3,
	'not_recommend_player_number~~' => array(~~ 6 ),		"not_recommend_player_number": [6],

	Don't specify anything here (null) if there is no configuration that is REALLY better/worse than another one. You can check player's poll on BoardGameGeek game page if you have any doubt. Note that there can be at most one suggested player count (provide either null or a single number), but there can be several not recommended player counts (provide either null or an array of values).		Don't specify anything here (null) if there is no configuration that is REALLY better/worse than another one. You can check player's poll on BoardGameGeek game page if you have any doubt. Note that there can be at most one suggested player count (provide either null or a single number), but there can be several not recommended player counts (provide either null or an array of values).
Line 47:		Line 44:

	'''player_colors'''		'''player_colors'''
	'player_colors~~' => array(~~ "ff0000", "008000", "0000ff", "ffa500", "ffffff" ),		"player_colors": ["ff0000", "008000", "0000ff", "ffa500", "ffffff"],

	This array defines the default player colors, theoretically this can be bigger then maximum number of players but you have to support all of the players in your game.		This array defines the default player colors, theoretically this can be bigger then maximum number of players but you have to support all of the players in your game.
Line 68:		Line 65:
	// If in the game, all losers are equal (no score to rank them or explicit in the rules that losers are not ranked between them), set this to true		// If in the game, all losers are equal (no score to rank them or explicit in the rules that losers are not ranked between them), set this to true
	// The game end result will display "Winner" for the 1st player and "Loser" for all other players		// The game end result will display "Winner" for the 1st player and "Loser" for all other players
	'losers_not_ranked~~' =>~~ false,		"losers_not_ranked": false,


Line 83:		Line 80:
	// When doing a rematch, the player order is swapped using a "rotation" so the starting player is not the same		// When doing a rematch, the player order is swapped using a "rotation" so the starting player is not the same
	// If you want to disable this, set this to true (even if the comment in your game file say the opposite).		// If you want to disable this, set this to true (even if the comment in your game file say the opposite).
	'disable_player_order_swap_on_rematch~~' =>~~ false,		"disable_player_order_swap_on_rematch": false,

	==Deprecated fields==		==Deprecated fields==
Line 103:		Line 100:

	Example:		Example:
	'tie_breaker_description~~' => totranslate(~~"Number of remaining cards in hand"),		"tie_breaker_description": "Number of remaining cards in hand",

	== Multiple tie breaker management ==		== Multiple tie breaker management ==
Line 117:		Line 114:
	In this case, you should add the following in gameinfos.inc.php:		In this case, you should add the following in gameinfos.inc.php:

	'tie_breaker_split~~' => array(~~ 10000, 100 , 1 ),		"tie_breaker_split": [10000, 100 , 1],

	It means that the first tie breaker has been multiplied by 10000, the second by 100, and the third by 1.		It means that the first tie breaker has been multiplied by 10000, the second by 100, and the third by 1.

Thoun: Thoun moved page Game meta-information: gameinfos.inc.php to Game meta-information: gameinfos.jsonc

2026-04-20T10:03:15Z

Thoun moved page Game meta-information: gameinfos.inc.php to Game meta-information: gameinfos.jsonc

← Older revision	Revision as of 12:03, 20 April 2026
(No difference)

James Games: /* Multiple tie breaker management */

2026-02-05T19:12:11Z

Multiple tie breaker management

← Older revision		Revision as of 21:12, 5 February 2026
Line 109:		Line 109:
	If your game has multiple tie breakers, here is what you should do.		If your game has multiple tie breakers, here is what you should do.

	Let's take this example: "In case of a tie, the winner is the ~~game~~ with the most remaining money, then number of buildings built, then number of cards in your hand".		Let's take this example: "In case of a tie, the winner is the player with the most remaining money, then number of buildings built, then number of cards in your hand".

	In this example, your playerScoreAux field might be calculated like this:		In this example, your playerScoreAux field might be calculated like this:

Thoun at 13:12, 1 October 2025

2025-10-01T13:12:19Z

← Older revision		Revision as of 15:12, 1 October 2025
Line 98:		Line 98:

	==Tie breaker description==		==Tie breaker description==
	Describe tie breaker score calculation (~~player_score_aux in player table~~).		Describe tie breaker score calculation (using $this->playerScoreAux).

	Important: This is used in the javascript too, which is automatically generated. Using newlines in here will cause errors in the javascript, which will cause the game to not load.		Important: This is used in the javascript too, which is automatically generated. Using newlines in here will cause errors in the javascript, which will cause the game to not load.
Line 111:		Line 111:
	Let's take this example: "In case of a tie, the winner is the game with the most remaining money, then number of buildings built, then number of cards in your hand".		Let's take this example: "In case of a tie, the winner is the game with the most remaining money, then number of buildings built, then number of cards in your hand".

	In this example, your ~~"player_score_aux"~~ field might be calculated like this:		In this example, your playerScoreAux field might be calculated like this:

	10000 * (remaining_money ) + 100 * (buildings_built) + (number_of_cards)		10000 * (remaining_money ) + 100 * (buildings_built) + (number_of_cards)

Ufm: /* Losers not ranked between themselves */

2025-06-15T22:16:48Z

Losers not ranked between themselves

← Older revision		Revision as of 00:16, 16 June 2025
Line 73:		Line 73:
	'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')		'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')

	To activate this ~~modifierfor~~ your game, please contact a BGA admin (<code>hardcoded_team_games</code> must be enabled manually).		To activate this modifier for your game, please contact a BGA admin (<code>hardcoded_team_games</code> must be enabled manually).

	<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).		<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).

BugLaden: /* Colors */

2024-10-16T20:44:45Z

Colors

← Older revision		Revision as of 22:44, 16 October 2024
Line 49:		Line 49:
	'player_colors' => array( "ff0000", "008000", "0000ff", "ffa500", "ffffff" ),		'player_colors' => array( "ff0000", "008000", "0000ff", "ffa500", "ffffff" ),

	This array defines the default player colors, theoretically this can be bigger then maximum number of players but you have to support all of the in your game.		This array defines the default player colors, theoretically this can be bigger then maximum number of players but you have to support all of the players in your game.
	Your setupNewGame in php is responsible for attributing these values to players. See section "Player color preferences" in [[Main_game_logic:_yourgamename.game.php]] for details.		Your setupNewGame in php is responsible for attributing these values to players. See section "Player color preferences" in [[Main_game_logic:_yourgamename.game.php]] for details.

Ufm: /* Losers not ranked between themselves */

2024-09-10T05:35:10Z

Losers not ranked between themselves

← Older revision		Revision as of 07:35, 10 September 2024
Line 69:		Line 69:
	// The game end result will display "Winner" for the 1st player and "Loser" for all other players		// The game end result will display "Winner" for the 1st player and "Loser" for all other players
	'losers_not_ranked' => false,		'losers_not_ranked' => false,


	'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')		'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')

	To activate this ~~for~~ your game, please contact a BGA admin (<code>hardcoded_team_games</code> must be enabled manually)~~. The game must support only 2p and/or team modes~~.		To activate this modifierfor your game, please contact a BGA admin (<code>hardcoded_team_games</code> must be enabled manually).

	<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).		<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).

Ufm: /* Losers not ranked between themselves */

2024-09-10T05:34:05Z

Losers not ranked between themselves

← Older revision		Revision as of 07:34, 10 September 2024
Line 71:		Line 71:
	'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')		'''Note''': In some team games like Tichu, Spades, and Belote, players do not gain or lose ELO by teammates. (Hover over the ELO changes to find 'Teammate: -100%')

	To activate this ~~modifier~~ for your game, please contact ~~the~~ BGA admin.		To activate this for your game, please contact a BGA admin (<code>hardcoded_team_games</code> must be enabled manually). The game must support only 2p and/or team modes.

	<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).		<b style="color:darkred">Warning:</b> This modifier should not be applied to co-op games or games where 3 or more parties can compete each other (e.g. individual mode with 3 or more players, 2v2v2 6 player mode, and etc.).

Sguzzer Gunayer: /* Beta */

2024-09-07T08:46:17Z

Beta

← Older revision		Revision as of 10:46, 7 September 2024
Line 22:		Line 22:

	You are not allowed to set the "'''is_beta'''" to 0 before the game has been released on BGA and stabilized.		You are not allowed to set the "'''is_beta'''" to 0 before the game has been released on BGA and stabilized.


	==Time Profiles==		==Time Profiles==
	'''fast/medium/slow_additional_time''': please set high values here: after the game has been released, there is a process that adjusts these values to match the real game duration. Adjustment starts when the game enters beta, after that these have no effect, and require admin intervention to change.		'''fast/medium/slow_additional_time''': please set high values here: after the game has been released, there is a process that adjusts these values to match the real game duration. Adjustment starts when the game enters beta, after that these have no effect, and require admin intervention to change.