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

BGA game Lifecycle

From Board Game Arena
Revision as of 12:21, 14 March 2022 by Ufm (talk | contribs)
Jump to navigation Jump to search


Game File Reference


Useful Components

Official

  • Deck: a PHP component to manage cards (deck, hands, picking cards, moving cards, shuffle deck, ...).
  • Draggable: a JS component to manage drag'n'drop actions.
  • Counter: a JS component to manage a counter that can increase/decrease (ex: player's score).
  • ExpandableSection: a JS component to manage a rectangular block of HTML than can be displayed/hidden.
  • Scrollmap: a JS component to manage a scrollable game area (useful when the game area can be infinite. Examples: Saboteur or Takenoko games).
  • Stock: a JS component to manage and display a set of game elements displayed at a position.
  • Zone: a JS component to manage a zone of the board where several game elements can come and leave, but should be well displayed together (See for example: token's places at Can't Stop).

Undocumented component (if somebody knows please help with docs)

  • Wrapper: a JS component to wrap a <div> element around its child, even if these elements are absolute positioned.

Unofficial


Game Development Process


Guides for Common Topics


Miscellaneous Resources

Here's a summary of the different steps you would follow when developing a game with BGA Studio.

Step How to reach this step What happens during this step?
Initial How to join BGA developer team? You can choose to join an existing team / create a new project
Assigned You choose a game You can start the development of the game
Pre-alpha You've started to write some code You develop the game. During this phase, we can assist you with the framework and give you some advice.
Alpha Follow Pre-release_checklist, then tell us that your development is finished "BGA review": we are reviewing your game and checking that it respects BGA guidelines. If not, we will ask you (and help you) to fix it.

Publisher review: the publisher, the designer, we and you can test the game together and separately. We help you to take into account remarks from the publisher and the designer.

Public beta The adaptation should be approved by the publisher while receiving enough approvals from reviewers before requesting beta. Having 10 or more approvals is recommended, but if the game is generally well-received (preferably game rating above 4.5) and there are no pending bugs and issues left the game may progress ignoring 10 approvals hurdle as administrative discretion. All players can play! During the first days, it is common that some bugs are reported by players, and you can fix them following the instructions in Post-release phase.
Gold The game is stable on BGA We find together a good launch date for the game, we announce the game on BGA news. Congrats! You can still modify and optimize things following the instructions in Post-release phase.

See also

Retrieved from "http:///index.php?title=BGA_game_Lifecycle&oldid=12269"