This is a documentation for Board Game Arena: play board games online !

Pre-release checklist: Difference between revisions

From Board Game Arena
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 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]]

Revision as of 23:19, 25 February 2017

If you think your game is ready to be reviewed by by BGA admins and/or Publisher please consult this checklist first

  • Metadata and graphics
    • 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.
    • 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)
  • Server side
    • 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.
    • 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)
    • You implement tiebreaking (using aux score field) and updated tiebreaker description in meta-data
  • Special testing
    • Game is tested with spectator (non player observer)
    • 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 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
  • Cleanup
    • Remove all extra console.log from your js code
    • 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 [1]
    • 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