Create a game in BGA Studio: Complete Walkthrough - Историја измена

Victoria la у 02:05, 18. април 2018.

2018-04-18T02:05:07Z

@@ Ред 30: / Ред 30: @@
 If you want to take over existing project first ask on forum to see if project is abandoned, then get read only access (via project list) and see if this worth using it, if it has no code or graphics just start from the scratch, don't worry about project name it can be renamed later
 == Obtain game graphics ==
@@ Ред 60: / Ред 95: @@
 exclude them from version control. There is also a misc/ folder now but it will hold up to 1 Mb of data files which would be checked in, so rules pdf's may not fit there.
 == Update game infos and box graphics ==

Victoria la: /* Wrap Up */

2018-04-18T01:45:20Z

Wrap Up

← Старија измена		Верзија на датум 18. април 2018. у 03:45
Ред 270:		Ред 270:

	== Wrap Up ==		== Wrap Up ==


			* Implement game progression (getGameProgression() in php)
			* Implement Zombie turn (zombieTurn() in php)
			* Define and implemented some meaningful statistics for your game (i.e. total points, point from source A, B, C...)
			* The games logs should explain what happened if player was not looking
			* You need to implemented tiebreaking (using aux score field) and updated tiebreaker description in meta-data
			* Make sure all UI strings are marked for translation
			* UI elements which are images (i.e. tokens, cards) should have tooltips


	When you think you game is completely working there is still bunch of stuff you have to do/check before telling admin that game is ready, please go though this [[Pre-release checklist]].		When you think you game is completely working there is still bunch of stuff you have to do/check before telling admin that game is ready, please go though this [[Pre-release checklist]].

	~~'''TO BE CONTINUED...'''~~

Victoria la: /* Create Database Schema */

2018-04-18T01:36:24Z

Create Database Schema

Victoria la: /* Select a First Game */

2018-04-18T01:26:54Z

Select a First Game

← Старија измена		Верзија на датум 18. април 2018. у 03:26
Ред 26:		Ред 26:

	Even if you see few projects with name of the game they may not be active. There are a lot abandoned game projects. If its not clear by the status, post to Developers forum as ask if anybody actively working on the project, and at the same time ask admins on the same forum post to send you graphics for that game if they have it (yeah on the forum, there is better chance of them seeing your post on the forum then in email).		Even if you see few projects with name of the game they may not be active. There are a lot abandoned game projects. If its not clear by the status, post to Developers forum as ask if anybody actively working on the project, and at the same time ask admins on the same forum post to send you graphics for that game if they have it (yeah on the forum, there is better chance of them seeing your post on the forum then in email).

			If you goal was to fix bugs in existing project, you have to ask on forum to get access to it, projects developed by bga admins are not in the studio.

			If you want to take over existing project first ask on forum to see if project is abandoned, then get read only access (via project list) and see if this worth using it, if it has no code or graphics just start from the scratch, don't worry about project name it can be renamed later

	== Obtain game graphics ==		== Obtain game graphics ==

Victoria la: /* Select a First Game */

2018-04-18T01:12:24Z

Select a First Game

← Старија измена		Верзија на датум 18. април 2018. у 03:12
Ред 15:		Ред 15:
	== Select a First Game ==		== Select a First Game ==

	For you first game you must either		For you first '''real''' game you must either
	* Select a game from [http://en.studio.boardgamearena.com/#!page/availablelicences Available Licenses]		* Select a game from [http://en.studio.boardgamearena.com/#!page/availablelicences Available Licenses]
	* Or from Public Domain		* Or from Public Domain

Victoria la: /* Create State Machine */

2018-01-06T02:37:44Z

Create State Machine

← Старија измена		Верзија на датум 6. јануар 2018. у 04:37
Ред 246:		Ред 246:
	Please fist watch this again [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine BGA game state machine]		Please fist watch this again [http://www.slideshare.net/boardgamearena/bga-studio-focus-on-bga-game-state-machine BGA game state machine]
	and then please read [[Your game state machine: states.inc.php]]		and then please read [[Your game state machine: states.inc.php]]

			Now the state machine should be relatively simple, if you find yourself with machine with more than 10 states its probably not the way to go.
			Not all the player interactions need separate states, a lot of things can be implemented directly on client, i.e. if your player need to select
			a reward token, which offers choice of resource, instead of two states on server just have one state on server and possible few states on client (client side states)
			to collect this info.

	== Implement Notification handling ==		== Implement Notification handling ==

Victoria la: /* Create Database Schema */

2018-01-06T02:30:20Z

Create Database Schema

@@ Ред 185: / Ред 185: @@
 * For dynamic stuff we should try to reduce amount of fields we need, i.e. we need a field for card, so its one, we need to know what zone cards belong to, its 2, and we have possible few other fields, if you look closely at you game you may find out that most of the zone only need one attribute at a time, i..e draw pile always have cards face  down, hand always face up, also for hand and discard order does not matter at all (but for draw it does matter). So in majority of cases we can get away with one single extra integer field representing state or order
 * In real database both card and zone will be integers as primary keys referring to additional tables, but in our case its total overkill, so they can be strings as easily
 Another Example: '''The euro game'''
@@ Ред 204: / Ред 216: @@
 </pre>
-You can also use cards database schema and [[Deck]] implementation for most purposes (even you not dealing with cards).
 See [[Game database model: dbmodel.sql]] for details about editing the file.

Victoria la: /* Hook Input and Animation */

2018-01-06T02:26:19Z

Hook Input and Animation

← Старија измена		Верзија на датум 6. јануар 2018. у 04:26
Ред 143:		Ред 143:
	Usually all pieces will be hooked to onclick during JS "setup" method, in addition if you create elements during server notification they have to be hooked up at that time.		Usually all pieces will be hooked to onclick during JS "setup" method, in addition if you create elements during server notification they have to be hooked up at that time.

	You can play with animation effects you want put in place, in general all the pieces that move in real game should be moving, such as meeples, resources tokens/cubes, cards, vp tokens. Regular piece animation provided by BGA framework, but if you use html layout positioning not inline positioning you have to remove absolute position after move. The set of functions for relative position token animation can found in https://github.com/elaskavaia/bga-sharedcode/blob/master/sharedcode.js		You can play with animation effects you want put in place, in general all the pieces that move in real game should be moving, such as meeples, resources tokens/cubes, cards, vp tokens.
			Regular piece animation is provided by BGA framework, but if you use html layout positioning not inline positioning you have to remove absolute positions (inline position styling) after each move. The set of functions for relative position token animation can found in https://github.com/elaskavaia/bga-sharedcode/blob/master/sharedcode.js

	Also its a good idea to give player a visual cues on what game elements are clickable now, usually it will be a style, such as "~~active_element~~", with visual effect of white dashed outline (outline is better then border, because border changes will make piece move since it changes the size)		Also its a good idea to give player a visual cues on what game elements are clickable now, usually it will be a style, such as "active_slot", with visual effect of white dashed outline (outline is better then border, because border changes will make piece slightly move since it changes the size) or box-shadow (i.e. neon glow)

	If you read [http://www.slideshare.net/boardgamearena/bga-studio-guidelines BGA developers guidelines] you know that you should not get carried away with animation, you creating a board game not a video game... That also applies to sound effects (you should not use any sounds effects beside already provided by framework).		If you read [http://www.slideshare.net/boardgamearena/bga-studio-guidelines BGA developers guidelines] you know that you should not get carried away with animation, you creating a board game not a video game... That also applies to sound effects (you should not use any sounds effects beside already provided by framework).

Victoria la: /* Create a project */

2017-11-03T11:52:01Z

Create a project

← Старија измена		Верзија на датум 3. новембар 2017. у 13:52
Ред 66:		Ред 66:
	Note: if you have not setup [http://en.doc.boardgamearena.com/Tools_and_tips_of_BGA_Studio#File_Sync FTP auto-sync] yet, do it now, manually copying files is a no-starter.		Note: if you have not setup [http://en.doc.boardgamearena.com/Tools_and_tips_of_BGA_Studio#File_Sync FTP auto-sync] yet, do it now, manually copying files is a no-starter.

	Update your project status in ~~Management~~ page, you can say "development started" or "waiting for license" or "waiting for graphics" or combination of those.		Update your project status in [http://en.studio.boardgamearena.com/#!studio Control Panel > Manage games] page, you can say "development started" or "waiting for license" or "waiting for graphics" or combination of those.

	== Hook version control system ==		== Hook version control system ==

Victoria la: /* Obtain game graphics */

2017-11-03T11:49:21Z

Obtain game graphics

← Старија измена		Верзија на датум 3. новембар 2017. у 13:49
Ред 37:		Ред 37:
	* Go to boardgamegeek.com find your game and obtain 3D game box image, 2D box image, and if you lucky they also sometime have boards and token scans in "Game Pieces" section of Images		* Go to boardgamegeek.com find your game and obtain 3D game box image, 2D box image, and if you lucky they also sometime have boards and token scans in "Game Pieces" section of Images
	* If that fail google "boardgame <name>" and check Images section		* If that fail google "boardgame <name>" and check Images section
			* Get the rules PDF as well, there tools that allows you to extract graphics from PDF, which usually good for meeples, cubes and such

	Once you get the graphics one way or another you have to massage it to fit in the BGA criteria, which usually involves		Once you get the graphics one way or another you have to massage it to fit in the BGA criteria, which usually involves

← Старија измена		Верзија на датум 18. април 2018. у 03:36
Ред 173:		Ред 173:

	Usually design process will contain the following steps:		Usually design process will contain the following steps:
	* Design game model - model that represent your game in progress, such as at any ~~give~~ step you can restore the game from that model		* Design game model - model that represent your game in progress, such as at any given step you can restore the game from that model
	* Mapping - now map real game to that model		* Mapping - now map real game to that model
	* Encoding - now represent this model in database and material file with reasonable amount of fields		* Encoding - now represent this model in database and material file with reasonable amount of fields
Ред 182:		Ред 182:
	* Framework handles state machine transition, so you don't have to worry about database design for that (i.e. who's turn it is, what phase of the game we are at, you still have to design it but as part of state machine step)		* Framework handles state machine transition, so you don't have to worry about database design for that (i.e. who's turn it is, what phase of the game we are at, you still have to design it but as part of state machine step)
	* Also framework supports basic player information, color, order around the table, basic scoring, etc, so you don't have to worry about it either		* Also framework supports basic player information, color, order around the table, basic scoring, etc, so you don't have to worry about it either
	* The only thing you need in ~~our~~ database is state of the "board", which is "where each pieces is, and in what state", or (position,rotation) pair.		* The only thing you need in your database is state of the "board", which is "where each pieces is, and in what state", or (position,rotation) pair.
	* The card state is very simple, its usually "face up/face down", "tapped/untapped", "right side up/up side down"		* The card state is very simple, its usually "face up/face down", "tapped/untapped", "right side up/up side down"
	* As position go we never need real x,y,z. We need to know what "zone" card was, and depending on the zone it may sometimes need an extra "z" or "x" as card order. The zone position itself usually static or irrelevant.		* As position go we never need real x,y,z. We need to know what "zone" card was, and depending on the zone it may sometimes need an extra "z" or "x" as card order. The zone position itself usually static or irrelevant.
	* So our model is: we have cards, which have some attributes, at any given point in time they belong to a "zone", and can also have order and state		* So our model is: we have cards, which have some attributes, at any given point in time they belong to a "zone", and can also have order and state
	* Now for mapping we should consider what info changes and what info is static, static info is always candidate for material file or html		* Now for mapping we should consider what info changes and what info is static, static info is always candidate for material file or html
	* For dynamic stuff we should try to reduce amount of fields we need, i.e. we need a field for card, so its one, we need to know what zone cards belong to, its 2, and we have possible few other fields, if you look closely at you game you may find out that most of the zone only need one attribute at a time, i..e draw pile always have cards face down, hand always face up, also for hand and discard order does not matter at all (but for draw it does matter). So in majority of cases we can get away with one single extra integer field representing state or order		* For dynamic stuff we should try to reduce amount of fields we need, i.e. we need a field for card, so its one, we need to know what zone cards belong to, its 2, and we have possible few other fields, but if you look closely at you game you may find out that most of the zone only need one attribute at a time, i.e. draw pile always have cards face down, hand always face up, also for hand and discard order does not matter at all (but for draw it does matter). So in majority of cases we can get away with one single extra integer field representing state or order
	* In real database both card and zone will be integers as primary keys referring to additional tables, but in our case its total overkill, so they can be strings as easily		* In real database both card and zone will be integers as primary keys referring to additional tables, but in our case its total overkill, so they can be strings as easily