Studio FAQ - Laptörténet

Een: /* Some frequent errors */

2012-12-23T17:18:00Z

Some frequent errors

← Régebbi változat		A lap 2012. december 23., 17:18-kori változata
78. sor:		78. sor:
	=== Some frequent errors ===		=== Some frequent errors ===

	; The following error occurs when launching the game "Fatal error during creation of database ebd_quoridor_389: Not logged."		; The following error occurs when launching the game "Fatal error during creation of database ebd_quoridor_389 Not logged."
	: Check that you didn't use $g_user or getCurrentPlayerId() in setupNewGame() function or in an "args" function of your state. As these functions are not consequences of a user action, there is no current player defined. As a general rule, you should use getActivePlayerId() and not getCurrentPlayerId(). See the [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine presentation on the game state machine] for more information.		: Check that you didn't use $g_user or getCurrentPlayerId() in setupNewGame() function or in an "args" function of your state. As these functions are not consequences of a user action, there is no current player defined. As a general rule, you should use getActivePlayerId() and not getCurrentPlayerId(). See the [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine presentation on the game state machine] for more information.

Een: /* What is the best way to debug? */

2012-12-23T17:17:40Z

What is the best way to debug?

← Régebbi változat		A lap 2012. december 23., 17:17-kori változata
75. sor:		75. sor:

	In general for debugging, think of using the 'Save & restore state' 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. You can save up to 3 different states.		In general for debugging, think of using the 'Save & restore state' 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. You can save up to 3 different states.

			=== Some frequent errors ===

			; The following error occurs when launching the game "Fatal error during creation of database ebd_quoridor_389: Not logged."
			: Check that you didn't use $g_user or getCurrentPlayerId() in setupNewGame() function or in an "args" function of your state. As these functions are not consequences of a user action, there is no current player defined. As a general rule, you should use getActivePlayerId() and not getCurrentPlayerId(). See the [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine presentation on the game state machine] for more information.

Een: /* What is the best way to debug? */

2012-12-09T20:46:36Z

What is the best way to debug?

← Régebbi változat		A lap 2012. december 9., 20:46-kori változata
70. sor:		70. sor:
	* throw new BgaUserException(var_dump( $variable_to_inspect );		* throw new BgaUserException(var_dump( $variable_to_inspect );

	On the client side (Javascript), we recommand installing Firebug for Firefox (or using the Developer tools with Chrome ~~which has~~ about the same functionalities), then:		On the client side (Javascript), we recommand installing Firebug for Firefox (or using the 'Developer tools' with Chrome that have about the same functionalities), then:
	* console.log( variable_to_inspect ); will give you the object structure of the variable in the Firebug console, without blocking the execution. It's often a good idea to precede this call with a console.log( '### HERE ###' ); to find more easily the appropriate line in the console log.		* console.log( variable_to_inspect ); will give you the object structure of the variable in the Firebug console, without blocking the execution. It's often a good idea to precede this call with a console.log( '### HERE ###' ); to find more easily the appropriate line in the console log.
	* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.		* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.

	In general for debugging, think of using the 'Save & restore state' 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. You can save up to 3 different states.		In general for debugging, think of using the 'Save & restore state' 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. You can save up to 3 different states.

Een: /* What is the best way to debug? */

2012-12-09T20:42:02Z

What is the best way to debug?

← Régebbi változat		A lap 2012. december 9., 20:42-kori változata
74. sor:		74. sor:
	* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.		* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.

	In general for debugging, think of using the 'Save & restore state' functionality ~~(NB: currently non functional, will be ok with the next studio update)~~. 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. You can save up to 3 different states.		In general for debugging, think of using the 'Save & restore state' 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. You can save up to 3 different states.

Een: /* What is the best way to debug? */

2012-12-09T20:21:23Z

What is the best way to debug?

← Régebbi változat		A lap 2012. december 9., 20:21-kori változata
74. sor:		74. sor:
	* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.		* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.

	In general for debugging, think of using the ~~save/~~restore functionality (NB: currently non functional, will be ok with the next studio update). It ~~enable~~ 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.		In general for debugging, think of using the 'Save & restore state' functionality (NB: currently non functional, will be ok with the next studio update). 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. You can save up to 3 different states.

Een, 2012. december 9., 20:19-n

2012-12-09T20:19:37Z

← Régebbi változat		A lap 2012. december 9., 20:19-kori változata
63. sor:		63. sor:

	Yes! While playing a game on studio, you have a "Go to game database" link at the bottom of your game. This link will bring you directly to the database for the current table.		Yes! While playing a game on studio, you have a "Go to game database" link at the bottom of your game. This link will bring you directly to the database for the current table.

			== What is the best way to debug? ==

			On the server side (PHP), you can use one of these:
			* die(var_dump( $variable_to_inspect );
			* throw new BgaUserException(var_dump( $variable_to_inspect );

			On the client side (Javascript), we recommand installing Firebug for Firefox (or using the Developer tools with Chrome which has about the same functionalities), then:
			* console.log( variable_to_inspect ); will give you the object structure of the variable in the Firebug console, without blocking the execution. It's often a good idea to precede this call with a console.log( '### HERE ###' ); to find more easily the appropriate line in the console log.
			* alert( variable_to_inspect ); will popup what you wish and pause the execution until you click ok. This won't be useful for complex structures, only native types will get plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.

			In general for debugging, think of using the save/restore functionality (NB: currently non functional, will be ok with the next studio update). It enable 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.

Een, 2012. december 6., 21:43-n

2012-12-06T21:43:08Z

← Régebbi változat		A lap 2012. december 6., 21:43-kori változata
12. sor:		12. sor:

	You should first connect to the Studio website (with any of your <developer name><number> accounts). As the authentication is shared with the back-office, then you will be able to access it.		You should first connect to the Studio website (with any of your <developer name><number> accounts). As the authentication is shared with the back-office, then you will be able to access it.

			== I don't know the name to use to commit my game, what name should I use? ==

			The game name for committing is the name of the game in lower case and without spaces or special characters (ex: puertorico).
			It is the same name as the name used for the game folder in your SFTP access.

	== It's pretty annoying to log in with multiple users to start a game. Is there some easier way? ==		== It's pretty annoying to log in with multiple users to start a game. Is there some easier way? ==

Een, 2012. december 5., 21:45-n

2012-12-05T21:45:22Z

← Régebbi változat		A lap 2012. december 5., 21:45-kori változata
8. sor:		8. sor:

	On Windows, there is for example the WinSCP client.		On Windows, there is for example the WinSCP client.

			== I can't access the Studio back-office, I get a 'Not authorized' error message? ==

			You should first connect to the Studio website (with any of your <developer name><number> accounts). As the authentication is shared with the back-office, then you will be able to access it.

	== It's pretty annoying to log in with multiple users to start a game. Is there some easier way? ==		== It's pretty annoying to log in with multiple users to start a game. Is there some easier way? ==

Een: /* I updated the images in the 'img' folder of my game, but they don't show? */

2012-12-05T20:01:10Z

I updated the images in the 'img' folder of my game, but they don't show?

← Régebbi változat		A lap 2012. december 5., 20:01-kori változata
43. sor:		43. sor:
	== I updated the images in the 'img' folder of my game, but they don't show? ==		== I updated the images in the 'img' folder of my game, but they don't show? ==

	On BGA Studio, there is the gameserver you are developing on, and the main site server that ~~serves~~ to launch the games. The game icon, box and the publisher logo are hosted on the ~~mainsite~~ server, so they are not immediately available when you modify them on the gameserver. To deploy them on the main site, you have to use the [[Studio back-office]] to do a commit.		On BGA Studio, there is the gameserver you are developing on, and the main site server that is used to launch the games. The game icon, box and the publisher logo are hosted on the main site server, so they are not immediately available when you modify them on the gameserver. To deploy them on the main site, you have to use the [[Studio back-office]] to do a commit.

	If the images still don't show after that, please try emptying your browser cache and reloading the page.		If the images still don't show after that, please try emptying your browser cache and reloading the page.

Een, 2012. december 5., 19:59-n

2012-12-05T19:59:56Z

← Régebbi változat		A lap 2012. december 5., 19:59-kori változata
43. sor:		43. sor:
	== I updated the images in the 'img' folder of my game, but they don't show? ==		== I updated the images in the 'img' folder of my game, but they don't show? ==

	On BGA Studio, there is the gameserver you are developing on, and the main site server that serves to launch the games. The game icon, box and the publisher logo are hosted on the mainsite server, so they are not immediately available when you modify them on the gameserver. To deploy them on the main site, you have to use the Studio back office to do a commit.		On BGA Studio, there is the gameserver you are developing on, and the main site server that serves to launch the games. The game icon, box and the publisher logo are hosted on the mainsite server, so they are not immediately available when you modify them on the gameserver. To deploy them on the main site, you have to use the [[Studio back-office]] to do a commit.

	If the images still don't show after that, please try emptying your browser cache and reloading the page.		If the images still don't show after that, please try emptying your browser cache and reloading the page.