Post-release phase - Гісторыя версій

Brainchild: Fixed the link to the bugs forum

2020-07-08T21:18:42Z

Fixed the link to the bugs forum

← Папярэдн. версія		Версія ад 23:18, 8 ліпеня 2020
Радок 9:		Радок 9:
	== Bugs reporting ==		== Bugs reporting ==

	Bugs are reported in the [~~http~~://~~forum.~~boardgamearena.com/~~viewforum.php?f=4~~ BGA bugs ~~forum~~].		Bugs are reported on the [https://boardgamearena.com/bugs BGA bugs page].

	During days after your game has been published and from time to time, please have a look at it to check if everything is fine.		During days after your game has been published and from time to time, please have a look at it to check if everything is fine.

Brainchild: /* Updating game options */

2020-07-06T16:37:57Z

Updating game options

← Папярэдн. версія		Версія ад 18:37, 6 ліпеня 2020
Радок 45:		Радок 45:
	* If you add options, you should let us know which value should be used for the arena mode, so that we can update the arena configuration.		* If you add options, you should let us know which value should be used for the arena mode, so that we can update the arena configuration.
	* If you remove an option or change a version ID, it will break the arena configuration and prevent creating new arena games, so you should let us know so that we can synchronize to update the configuration at the same time as you deploy the new version.		* If you remove an option or change a version ID, it will break the arena configuration and prevent creating new arena games, so you should let us know so that we can synchronize to update the configuration at the same time as you deploy the new version.
			* Do not change option IDs once the game is in production, it will break ongoing games and audience option statistics.

	=== Updating Statistics ===		=== Updating Statistics ===

Een: /* Updating the database schema */ update procedure to test upgradeTableDb

2020-07-01T16:42:44Z

Updating the database schema: update procedure to test upgradeTableDb

← Папярэдн. версія		Версія ад 18:42, 1 ліпеня 2020
Радок 81:		Радок 81:

	Note3: testing on the studio is possible by following the following procedure:		Note3: testing on the studio is possible by following the following procedure:
	* ~~launch a game with~~ the ~~dbmodel.sql~~ matching the current production ~~version (you can go~~ back ~~in time~~ with the version control ~~buttons if needed to retrieve it~~)		* make sure the current state of your project is correctly committed
	* access ~~this~~ game database		* revert to the revision currently in production using the version control tools ("Display commit log" -> find the revision matching the current version in production, then "Overwrite working copy with this revision" to get back the matching code)
	* in the "global" table, find the row with id 300. Its value is ~~9999999999~~ by default on the studio. Change it to the current production version number		* launch a game with this code
			* revert to your code latest version using the version control tools (use "Overwrite working copy with this revision" with "head" for the revision)
			* access the game database
			* in the "global" table, find the row with id 300. Its value is 999999999 by default on the studio. Change it to the current production version number
	* hit refresh to reload your game page. Your upgradeTableDb() function will be run and the global value will be updated again to the studio value		* hit refresh to reload your game page. Your upgradeTableDb() function will be run and the global value will be updated again to the studio value
	* check the database to see if your changes have been correctly applied.		* check the database to see if your changes have been correctly applied.

Een: /* Updating the database schema */

2020-06-26T12:37:18Z

Updating the database schema

← Папярэдн. версія		Версія ад 14:37, 26 чэрвеня 2020
Радок 77:		Радок 77:

	Note2: this is always risky to modify the DB scheme, so:		Note2: this is always risky to modify the DB scheme, so:
	_ if your game is already open to everyone on BGA (from BETA onwards), it may be worth contacting us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).		* if your game is already open to everyone on BGA (from BETA onwards), it may be worth contacting us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).
	_ if you can avoid it... try to avoid it :)		* if you can avoid it... try to avoid it :)

	Note3: testing on the studio is possible by following the following procedure:		Note3: testing on the studio is possible by following the following procedure:
	_ launch a game with the dbmodel.sql matching the current production version (you can go back in time with the version control buttons if needed to retrieve it)		* launch a game with the dbmodel.sql matching the current production version (you can go back in time with the version control buttons if needed to retrieve it)
	_ access this game database		* access this game database
	_ in the "global" table, find the row with id 300. Its value is 9999999999 by default on the studio. Change it to the current production version number		* in the "global" table, find the row with id 300. Its value is 9999999999 by default on the studio. Change it to the current production version number
	_ hit refresh to reload your game page. Your upgradeTableDb() function will be run and the global value will be updated again to the studio value		* hit refresh to reload your game page. Your upgradeTableDb() function will be run and the global value will be updated again to the studio value
	_ check the database to see if your changes have been correctly applied.		* check the database to see if your changes have been correctly applied.

	=== Updating string to be translated ===		=== Updating string to be translated ===

Een: /* Updating the database schema */ testing updateTableDb on the studio

2020-06-26T12:35:44Z

Updating the database schema: testing updateTableDb on the studio

← Папярэдн. версія		Версія ад 14:35, 26 чэрвеня 2020
Радок 79:		Радок 79:
	_ if your game is already open to everyone on BGA (from BETA onwards), it may be worth contacting us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).		_ if your game is already open to everyone on BGA (from BETA onwards), it may be worth contacting us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).
	_ if you can avoid it... try to avoid it :)		_ if you can avoid it... try to avoid it :)

			Note3: testing on the studio is possible by following the following procedure:
			_ launch a game with the dbmodel.sql matching the current production version (you can go back in time with the version control buttons if needed to retrieve it)
			_ access this game database
			_ in the "global" table, find the row with id 300. Its value is 9999999999 by default on the studio. Change it to the current production version number
			_ hit refresh to reload your game page. Your upgradeTableDb() function will be run and the global value will be updated again to the studio value
			_ check the database to see if your changes have been correctly applied.

	=== Updating string to be translated ===		=== Updating string to be translated ===

Een: /* What can be modified after release? */ options change and arena

2020-06-16T09:40:59Z

What can be modified after release?: options change and arena

← Папярэдн. версія		Версія ад 11:40, 16 чэрвеня 2020
Радок 33:		Радок 33:
	* Changes in the database schema of the game (dbmodel.sql).		* Changes in the database schema of the game (dbmodel.sql).
	* New global variable or game option accessed during the game (if it's only used during setup, it should be safe).		* New global variable or game option accessed during the game (if it's only used during setup, it should be safe).
	* Delete or change ID of existing game option (especially for Arena tables and turn by turn tables)
	* Change ID of existing game states (adding new game states is fine).		* Change ID of existing game states (adding new game states is fine).

Радок 41:		Радок 40:

	Note: in the near future, we will introduce the possibility for you to block/unblock a game directly from your Control Panel in order to perform all the process by yourself.		Note: in the near future, we will introduce the possibility for you to block/unblock a game directly from your Control Panel in order to perform all the process by yourself.

			=== Updating game options ===

			* If you add options, you should let us know which value should be used for the arena mode, so that we can update the arena configuration.
			* If you remove an option or change a version ID, it will break the arena configuration and prevent creating new arena games, so you should let us know so that we can synchronize to update the configuration at the same time as you deploy the new version.

	=== Updating Statistics ===		=== Updating Statistics ===

Cpasbanal: /* Changes that breaks the games in progress */

2020-06-16T08:51:59Z

Changes that breaks the games in progress

← Папярэдн. версія		Версія ад 10:51, 16 чэрвеня 2020
Радок 33:		Радок 33:
	* Changes in the database schema of the game (dbmodel.sql).		* Changes in the database schema of the game (dbmodel.sql).
	* New global variable or game option accessed during the game (if it's only used during setup, it should be safe).		* New global variable or game option accessed during the game (if it's only used during setup, it should be safe).
			* Delete or change ID of existing game option (especially for Arena tables and turn by turn tables)
	* Change ID of existing game states (adding new game states is fine).		* Change ID of existing game states (adding new game states is fine).

Een: /* Updating the database schema */ contact us info (from BETA onwards)

2020-05-20T19:15:31Z

Updating the database schema: contact us info (from BETA onwards)

← Папярэдн. версія		Версія ад 21:15, 20 мая 2020
Радок 51:		Радок 51:
	=== Updating the database schema ===		=== Updating the database schema ===

	If you want to update the database schema of the game (dbmodel.sql), you should inform us before releasing the new version (see "[[#Changes that breaks the games in progress\|changes that breaks the games in progress]]").		If you want to update the database schema of the game (dbmodel.sql) and your game is already open to everyone on BGA (from BETA onwards), you should inform us before releasing the new version (see "[[#Changes that breaks the games in progress\|changes that breaks the games in progress]]").

	Any modification in dbmodel.sql should also appear in your nameofyourgame.game.php, in a function		Any modification in dbmodel.sql should also appear in your nameofyourgame.game.php, in a function
Радок 69:		Радок 69:
	}}		}}

	~~Note~~: of course you need to change your dbmodel.sql accordingly, so that new games get your updated scheme.		Note1: of course you need to change your dbmodel.sql accordingly, so that new games get your updated scheme.

	Note2: this is always risky to modify the DB scheme, so:		Note2: this is always risky to modify the DB scheme, so:
	_ it may be ~~worthy to contact~~ us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).		_ if your game is already open to everyone on BGA (from BETA onwards), it may be worth contacting us before, so we can stop the realtime games during the update (this way, only turn based games are concerned by the DB live upgrade).
	_ if you can avoid it... try to avoid it :)		_ if you can avoid it... try to avoid it :)

Tutchek: Added navigation

2020-04-15T21:21:13Z

Added navigation

← Папярэдн. версія		Версія ад 23:21, 15 красавіка 2020
Радок 1:		Радок 1:
			{{Studio_Framework_Navigation}}

	Your game is now on BGA: congrats!		Your game is now on BGA: congrats!

Sourisdudesert: /* Major changes */

2019-12-19T07:58:23Z

Major changes

@@ Радок 82: / Радок 82: @@
 * Has the meaning of the string changed? If yes, you HAVE to change the original string in order to invalidate all translations that has been done already.
 * Is there a similar string already used elsewhere in my game? In this case, you'd better use it again to enjoy immediately all translations already available.
 ===Major changes===