Pre-release checklist - ประวัติรุ่นแก้ไข

Vincentt เมื่อ 11:39, 20 เมษายน 2561

2018-04-20T11:39:10Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 13:39, 20 เมษายน 2561
บรรทัดที่ 10:		บรรทัดที่ 10:
	* Server side		* Server side
	** Game progression is implemented (getGameProgression() in php)		** Game progression is implemented (getGameProgression() in php)
	** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested ~~with two different studio accounts (dev0 and devzombi0 for example,~~ not ~~dev0 and dev1)~~		** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested if you explicitly click on the quit button to create a zombie. If you are expelled it does not generated a Zombie.
	** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)		** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
	** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)		** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)

Victoria la เมื่อ 01:25, 14 กุมภาพันธ์ 2561

2018-02-14T01:25:28Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 03:25, 14 กุมภาพันธ์ 2561
บรรทัดที่ 10:		บรรทัดที่ 10:
	* Server side		* Server side
	** Game progression is implemented (getGameProgression() in php)		** Game progression is implemented (getGameProgression() in php)
	** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested with two different studio accounts (dev0 and devzombi0 for example)		** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested with two different studio accounts (dev0 and devzombi0 for example, not dev0 and dev1)
	** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)		** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
	** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)		** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)

Vincentt เมื่อ 18:55, 12 กุมภาพันธ์ 2561

2018-02-12T18:55:56Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 20:55, 12 กุมภาพันธ์ 2561
บรรทัดที่ 10:		บรรทัดที่ 10:
	* Server side		* Server side
	** Game progression is implemented (getGameProgression() in php)		** Game progression is implemented (getGameProgression() in php)
	** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested ~~in pre-production or production so far.~~		** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested with two different studio accounts (dev0 and devzombi0 for example)
	** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)		** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
	** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)		** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)

Victoria la เมื่อ 02:41, 6 มกราคม 2561

2018-01-06T02:41:37Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:41, 6 มกราคม 2561
บรรทัดที่ 26:		บรรทัดที่ 26:
	** Copyright headers in all source files have your name		** Copyright headers in all source files have your name
	* User Interface		* User Interface
	** Review BGA UI design Guidelines [~~http://www.slideshare.net/boardgamearena/bga-studio-guidelines~~]		** Review BGA UI design Guidelines [[BGA_Studio_Guidelines]]
	** Non-self explanatory graphic elements should have tooltips		** Non-self explanatory graphic elements should have tooltips
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)

Victoria la เมื่อ 15:46, 21 ตุลาคม 2560

2017-10-21T15:46:46Z

Victoria la เมื่อ 21:53, 28 กรกฎาคม 2560

2017-07-28T21:53:48Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 23:53, 28 กรกฎาคม 2560
บรรทัดที่ 18:		บรรทัดที่ 18:
	** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)		** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)
	** Test your game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn		** Test your game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn
			** Test your game in 3D mode
	* Cleanup		* Cleanup
	** Remove all extra console.log from your js code		** Remove all extra console.log from your js code

Victoria la เมื่อ 21:52, 28 กรกฎาคม 2560

2017-07-28T21:52:03Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 23:52, 28 กรกฎาคม 2560
บรรทัดที่ 27:		บรรทัดที่ 27:
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)
	** Strings in your source code are ready for translation. See [[Translations]]		** Strings in your source code are ready for translation. See [[Translations]]
			* Finally
			** Send e-mail to bga admins asking for review of the game, you cannot post to pre-production using control panel until review is done and they unlock it
			** If you looking for advise on design and some 3rd party testing you can post a message of developers forum, and ask our developers, there are a lot of people who will gladly do it.

Victoria la เมื่อ 01:57, 1 มิถุนายน 2560

2017-06-01T01:57:41Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 03:57, 1 มิถุนายน 2560
บรรทัดที่ 26:		บรรทัดที่ 26:
	** Non-self explanatory graphic elements should have tooltips		** Non-self explanatory graphic elements should have tooltips
	** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)		** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)
	** Strings in your source code ~~and there~~ are ready for translation. See [[Translations]]		** Strings in your source code are ready for translation. See [[Translations]]

Victoria la เมื่อ 22:19, 25 กุมภาพันธ์ 2560

2017-02-25T22:19:23Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 00:19, 26 กุมภาพันธ์ 2560
บรรทัดที่ 1:		บรรทัดที่ 1:
	If you think your game is ready to be reviewed by by BGA admins and/or Publisher please consult this checklist first		If you think your game is ready to be reviewed by by BGA admins and/or Publisher please consult this checklist first

	* [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game		* Metadata and graphics
	* Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]]). Space around the box has to be transparent, not white.		** [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game
	* ~~Game progression is implemented (getGameProgression() in php)~~		** Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]]). Space around the box has to be transparent, not white.
	* Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested in pre-production or production so far.		** There is no images in img directory which are not needed anymore, check other images for sizes make sure its not like 10 megabytes each
	* There is no images in img directory which are not needed anymore, check other images for sizes make sure its not like 10 megabytes each		** Multiple images (i.e. cards) are compressed in "Sprite" (see [[Game art: img directory]])
	* Multiple images (i.e. cards) are compressed in "Sprite" (see [[Game art: img directory]])		* Server side
	* You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)		** Game progression is implemented (getGameProgression() in php)
	* ~~Copyright headers~~ in ~~all source files have your name~~		** Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested in pre-production or production so far.
	* ~~Strings in your source code and there are ready for translation. See [[Translations]]~~		** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
	* Game is tested with spectator (non player observer)		** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)
	* Game is tested with in-game replay feature (by clicking on notification log items)		** You implement tiebreaking (using aux score field) and updated tiebreaker description in meta-data
	* ~~Game has meaningful notification messages~~		* Special testing
	* Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE.		** Game is tested with spectator (non player observer)
	* Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)		** Game is tested with in-game replay feature (by clicking on notification log items)
	* ~~Non-self explanatory graphic elements should have tooltips~~		** Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE.
	* ~~If graphic elements appear~~ in ~~notification log they should have titles (i~~.~~e. title attribute~~ of ~~div) so can be read in non rendered form~~ (~~i.e. as text only~~)		** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)
	* Remove all extra console.log from your js code		** Test your game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn
	* Remove all unnecessary debug logging from your php code		* Cleanup
	* ~~Test~~ your ~~game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn~~		** Remove all extra console.log from your js code
	* Review BGA UI design Guidelines [http://www.slideshare.net/boardgamearena/bga-studio-guidelines]		** Remove all unnecessary debug logging from your php code
			** Copyright headers in all source files have your name
			* User Interface
			** Review BGA UI design Guidelines [http://www.slideshare.net/boardgamearena/bga-studio-guidelines]
			** Non-self explanatory graphic elements should have tooltips
			** If graphic elements appear in notification log they should have titles (i.e. title attribute of div) so can be read in non rendered form (i.e. as text only)
			** Strings in your source code and there are ready for translation. See [[Translations]]

Victoria la เมื่อ 00:23, 15 กุมภาพันธ์ 2560

2017-02-15T00:23:12Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 02:23, 15 กุมภาพันธ์ 2560
บรรทัดที่ 2:		บรรทัดที่ 2:

	* [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game		* [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game
	* Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]])		* Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]]). Space around the box has to be transparent, not white.
	* Game progression is implemented (getGameProgression() in php)		* Game progression is implemented (getGameProgression() in php)
	* Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested in pre-production or production so far.		* Zombie turn is implemented (zombieTurn() in php). Note: it can only be tested in pre-production or production so far.

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 17:46, 21 ตุลาคม 2560
บรรทัดที่ 4:		บรรทัดที่ 4:
	** [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game		** [[Game_meta-information: gameinfos.inc.php]] has correct and up to date information about the game
	** Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]]). Space around the box has to be transparent, not white.		** Game box graphics is 3D version of the game box (if available) and publisher icon is correct (see [[Game art: img directory]]). Space around the box has to be transparent, not white.
	** There is no images in img directory which are not needed anymore~~, check other images for sizes make sure its not like 10 megabytes each~~		** There is no images in img directory which are not needed anymore
	** Multiple images (i.e. cards) are compressed in "Sprite" (see [[Game art: img directory]])		** Multiple images (i.e. cards) are compressed in "Sprite" (see [[Game art: img directory]])
			** Each image should not exceed 4M
			** Total size should not exceed 10M, image compression should be used otherwise
	* Server side		* Server side
	** Game progression is implemented (getGameProgression() in php)		** Game progression is implemented (getGameProgression() in php)
บรรทัดที่ 11:		บรรทัดที่ 13:
	** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)		** You have defined and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
	** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)		** Game has meaningful notification messages (but don't overkill it, more user logs will slow down the loading)
	** You ~~implement~~ tiebreaking (using aux score field) and updated tiebreaker description in meta-data		** You implemented tiebreaking (using aux score field) and updated tiebreaker description in meta-data
	* Special testing		* Special testing
	** Game is tested with spectator (non player observer)		** Game is tested with spectator (non player observer)
	** Game is tested with in-game replay feature (by clicking on notification log items)		** Game is tested with in-game replay feature (by clicking on notification log items)
	** Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE.		** Game works in Chrome and Firefox browsers at least. Also very recommended to test in IE 11 and Edge.
	** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)		** Game works on mobile device (if you don't have mobile device to test at least test in Chrome with smaller screen, they have a mode for that)
	** Test your game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn		** Test your game in realtime mode. Usually people will run out of time if you use default times unless you add call giveExtraTime($active_player_id) before each turn
บรรทัดที่ 29:		บรรทัดที่ 31:
	** Strings in your source code are ready for translation. See [[Translations]]		** Strings in your source code are ready for translation. See [[Translations]]
	* Finally		* Finally
	** Send e-mail to bga admins asking for review of the game, you cannot post to pre-production using control panel until review is done and they unlock it		** Send e-mail to bga admins asking for review of the game, you cannot post to pre-production yourself using control panel until review is done and they unlock it. If they don't reply post on dev forum.
	** If you looking for advise on design and some 3rd party testing you can post a message of developers forum, and ask our developers, there are a lot of people who will gladly do it.		** If you looking for advise on design and some 3rd party testing you can post a message of developers forum, and ask our developers, there are a lot of people who will gladly do it.