BGA game Lifecycle: Difference between revisions

Revision as of 18:57, 17 January 2021

Game File Reference

Overview

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

BGA Code Sharing - Shared resources, projects on git hub, common code, other links
BGA Studio Cookbook - Tips and instructions on using API's, libraries and frameworks
Common board game elements image resources

Game Development Process

Guides for Common Topics

Miscellaneous Resources

Studio FAQ
Tools and tips of BGA Studio - Tips and instructions on setting up development environment
Studio logs - Instructions for log access
Practical debugging - Tips focused on debugging
Troubleshooting - Most common "I am really stuck" situations
Studio Bugs - Reports against Studio itself (not BGA!)

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 happened during the 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 check if it respects BGA guidelines. If not, we will ask you (and help you) to fix them. "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 is approved by the publisher, receives at least 10 approvals from reviewers, and you request beta	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.

@@ Line 11: / Line 11: @@
 | Assigned || You choose a game  || You can start the development of the game
 |-
-| Pre-alpha || You've started to write some piece of code  || You develop the game. During this phase, we can assist you with the framework and give you some pieces of advice.
+| 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 check if it respects [http://fr.slideshare.net/boardgamearena/bga-studio-guidelines BGA guidelines]. If not, we will ask you (and help you) to fix them. "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.