Deck - Историја измена

Amadannabriona: /* The 5 properties of each card */

2018-09-20T01:00:27Z

The 5 properties of each card

← Старија измена		Верзија на датум 20. септембар 2018. у 03:00
Ред 28:		Ред 28:
	'''type''' and '''type_arg''' defines the type of your card.		'''type''' and '''type_arg''' defines the type of your card.

	'''type''' is a short string, and '''type_arg''' is ~~a string~~.		'''type''' is a short string, and '''type_arg''' is an integer.

	You can use these two values as you like to make sure you will be able to identify the different cards in the game. See usage of "type" and "type_arg" below.		You can use these two values as you like to make sure you will be able to identify the different cards in the game. See usage of "type" and "type_arg" below.

Amadannabriona: /* The 5 properties of each card */

2018-09-20T00:59:22Z

The 5 properties of each card

← Старија измена		Верзија на датум 20. септембар 2018. у 02:59
Ред 28:		Ред 28:
	'''type''' and '''type_arg''' defines the type of your card.		'''type''' and '''type_arg''' defines the type of your card.

	'''type''' is a short string, and '''type_arg''' is ~~an integer~~.		'''type''' is a short string, and '''type_arg''' is a string.

	You can use these two values as you like to make sure you will be able to identify the different cards in the game. See usage of "type" and "type_arg" below.		You can use these two values as you like to make sure you will be able to identify the different cards in the game. See usage of "type" and "type_arg" below.

Amadannabriona: /* Create a new Deck component */

2018-09-16T04:24:19Z

Create a new Deck component

← Старија измена		Верзија на датум 16. септембар 2018. у 06:24
Ред 51:		Ред 51:
	=== Create a new Deck component ===		=== Create a new Deck component ===

	For each Deck component in your game, you need to create a dedicated table in database. This table has a standard format. In ~~practical~~, if you want to have a Deck component named "card", you ~~just have to~~ copy/paste the following in your "dbmodel.sql":		For each Deck component in your game, you need to create a dedicated table in the SQL database. This table has a standard format. In practice, if you just want to have a Deck component named "card", you can copy/paste the following into your "dbmodel.sql" file:

	<pre>		<pre>
Ред 64:		Ред 64:
	</pre>		</pre>

	Note: database schema of this table does not have to be exactly ~~that, you~~ can increase size of fields or add more fields. For additional fields		Note: the database schema of this table does not have to be exactly what is listed above. You can increase the size of the fields or add more fields. For additional fields
	you just have to do manual queries.		you just have to do manual queries.

	Once you ~~did~~ this (and ~~restart~~ your game), you can declare ~~your~~ Deck component in your PHP code in your class constructor. For Hearts for example, I added to "Hearts()" method:		Once you have done this (and restarted your game), you can declare the Deck component in your PHP code in your class constructor. For ''Hearts'' for example, I added to the "Hearts()" method:

	<pre>		<pre>
Ред 74:		Ред 74:
	</pre>		</pre>

	Note that we specify "card" here, the name of our previously created table. It means you can create several "Deck" with ~~several~~ tables. Most of the time this is ~~unuseful:~~ a Deck component should manage all objects of the same kind (~~ex:~~ all cards of the game).		Note that we specify "card" here: the name of our previously created table. This means you can create several "Deck" components with multiple tables. Most of the time this is not useful; a Deck component should manage all objects of the same kind (i.e., all cards in the game).

	Afterwards, we can initialize your "Deck" by creating all the cards of the game. Generally, this is done only once during the game, ~~during~~ the "setupNewGame" method.		Afterwards, we can initialize your "Deck" by creating all the cards of the game. Generally, this is done only once during the game, in the "setupNewGame" method.

	"Deck" component provides ~~you~~ a fast way to initialize all your cards at once: createCards. Here is how it is used for "Hearts":		The "Deck" component provides a fast way to initialize all your cards at once: createCards. Here is how it is used for "Hearts":
	<pre>		<pre>
	// Create cards		// Create cards

Amadannabriona у 04:20, 16. септембар 2018.

2018-09-16T04:20:37Z

← Старија измена		Верзија на датум 16. септембар 2018. у 06:20
Ред 1:		Ред 1:
	"Deck" is one of the most useful component on PHP side. With "Deck", you can manage cards of your game on server side.		"Deck" is one of the most useful component on the PHP side. With "Deck", you can manage the cards in your game on the server side.

	Using "deck", you will be able to use the following features without writing a single SQL database request:		Using "deck", you will be able to use the following features without writing a single SQL database request:
	* Place cards in pile, shuffle cards, draw cards one by one or many ~~by many~~.		* Place cards in a pile, shuffle cards, draw cards one by one or many at a time.
	* "Auto-reshuffle" discard pile into deck when deck is empty.		* "Auto-reshuffle" the discard pile into the deck when the deck is empty.
	* Move cards between different locations: hands of players, the table, ...		* Move cards between different locations: hands of players, the table, etc.

Amadannabriona: /* Using Deck: Hearts example */

2018-09-16T04:19:22Z

Using Deck: Hearts example

← Старија измена		Верзија на датум 16. септембар 2018. у 06:19
Ред 9:		Ред 9:
	== Using Deck: Hearts example ==		== Using Deck: Hearts example ==

	Deck component is ~~massively~~ used in "Hearts~~" example game - a~~ card game. You ~~can~~ find in "hearts.game.php" that the object "$this->cards" is used many times.		The Deck component is extensively used in the sample ''Hearts'' card game. You will find in "hearts.game.php" that the object "$this->cards" is used many times.

	== Deck overview ==		== Deck overview ==

Amadannabriona: /* The 5 properties of each card */

2018-09-16T04:18:22Z

The 5 properties of each card

Victoria la: /* Create a new Deck component */

2017-04-03T00:50:31Z

Create a new Deck component

← Старија измена		Верзија на датум 3. април 2017. у 02:50
Ред 58:		Ред 58:
	) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;		) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;
	</pre>		</pre>

			Note: database schema of this table does not have to be exactly that, you can increase size of fields or add more fields. For additional fields
			you just have to do manual queries.

	Once you did this (and restart your game), you can declare your Deck component in your PHP code in your class constructor. For Hearts for example, I added to "Hearts()" method:		Once you did this (and restart your game), you can declare your Deck component in your PHP code in your class constructor. For Hearts for example, I added to "Hearts()" method:

Episodic: /* Initializing Deck component */ typos

2017-03-12T21:20:10Z

Initializing Deck component: typos

← Старија измена		Верзија на датум 12. март 2017. у 23:20
Ред 175:		Ред 175:

	$cards = array(		$cards = array(
	array( 'type' => 1, 'type_arg' => 99, nbr' => 1 ),		array( 'type' => 1, 'type_arg' => 99, 'nbr' => 1 ),
	array( 'type' => 2, 'type_arg' => 12, nbr' => 4 ),		array( 'type' => 2, 'type_arg' => 12, 'nbr' => 4 ),
	array( 'type' => 3, 'type_arg' => 33, nbr' => 2 )		array( 'type' => 3, 'type_arg' => 33, 'nbr' => 2 )
	...		...
	);		);
	</pre>		</pre>

	Note: During the "createCards" process, Deck ~~generate~~ unique IDs for all card items.		Note: During the "createCards" process, Deck generates unique IDs for all card items.

	Note: createCards is optimized to create a lot of cards at once. Do not use it to create cards one by one.		Note: createCards is optimized to create a lot of cards at once. Do not use it to create cards one by one.

Yami-sakana: /* Shuffling */

2016-09-14T05:01:42Z

Shuffling

← Старија измена		Верзија на датум 14. септембар 2016. у 07:01
Ред 410:		Ред 410:
	Shuffle only works on locations where cards are on a "pile" (ex: "deck").		Shuffle only works on locations where cards are on a "pile" (ex: "deck").

	Please note that all "location_arg" will be ~~reseted~~ to reflect the new order of the cards in the pile.		Please note that all "location_arg" will be reset to reflect the new order of the cards in the pile.

Sourisdudesert: /* Get cards informations */

2013-02-13T17:04:14Z

Get cards informations

← Старија измена		Верзија на датум 13. фебруар 2013. у 19:04
Ред 315:		Ред 315:
	Get all cards in specific location, as an array. Return an empty array if the location is empty.		Get all cards in specific location, as an array. Return an empty array if the location is empty.

	_ location (string): the location where to get the cards.		* location (string): the location where to get the cards.
	_ location_arg (optional): if specified, return only cards with the specified "location_arg".		* location_arg (optional): if specified, return only cards with the specified "location_arg".
	_ order_by (optional): if specified, returned cards are ordered by the given database field. Example: "card_id" or "card_type".		* order_by (optional): if specified, returned cards are ordered by the given database field. Example: "card_id" or "card_type".

	'''countCardInLocation( $location, $location_arg=null )'''		'''countCardInLocation( $location, $location_arg=null )'''
Ред 323:		Ред 323:
	Return the number of cards in specified location.		Return the number of cards in specified location.

	_ location (string): the location where to count the cards.		* location (string): the location where to count the cards.
	_ location_arg (optional): if specified, count only cards with the specified "location_arg".		* location_arg (optional): if specified, count only cards with the specified "location_arg".

	'''countCardsInLocations()'''		'''countCardsInLocations()'''
Ред 399:		Ред 399:
	Return an array of cards, or an empty array if there is no cards of the specified type.		Return an array of cards, or an empty array if there is no cards of the specified type.

	_ type: the type of cards		* type: the type of cards
	_ type_arg: if specified, return only cards with the specified "type_arg".		* type_arg: if specified, return only cards with the specified "type_arg".

	=== Shuffling ===		=== Shuffling ===

← Старија измена		Верзија на датум 16. септембар 2018. у 06:18
Ред 17:		Ред 17:
	=== The 5 properties of each card ===		=== The 5 properties of each card ===

	Using Deck component, each card will have 5 properties:		Using the Deck component, each card will have 5 properties:
	* '''id''': This is the unique ID of each card.		* '''id''': This is the unique ID of each card.
	* '''type''' and '''type_arg''': These two values ~~defines~~ the type of your card (=what sort of card this is?).		* '''type''' and '''type_arg''': These two values define the type of your card (i.e., what sort of card is this?).
	* '''location''' and '''location_arg''': These two values ~~defines~~ where is the card at now.		* '''location''' and '''location_arg''': These two values define where the card is at now.

	id, type and type_arg properties are constants ~~during~~ the game. location and location_arg ~~are changing~~ when your cards ~~are moving~~ from ~~places~~ to ~~places on~~ the game area.		The id, type, and type_arg properties are constants throughout the game. location and location_arg change when your cards move from one place to another in the game area.

	'''id''' is the unique ID of each card. Two cards ~~can't get~~ the same ID. IDs are generated automatically by the Deck component when you create cards during the Setup phase of your game.		'''id''' is the unique ID of each card. Two cards cannot have the same ID. IDs are generated automatically by the Deck component when you create cards during the Setup phase of your game.

	'''type''' and '''type_arg''' defines the type of your card. '''type''' is a short string, and '''type_arg''' is an integer. You can use these two values as you ~~want~~ to make sure you will be able to identify the different cards of the game. See usage of "type" and "type_arg" below.		'''type''' and '''type_arg''' defines the type of your card.

			'''type''' is a short string, and '''type_arg''' is an integer.

			You can use these two values as you like to make sure you will be able to identify the different cards in the game. See usage of "type" and "type_arg" below.

	Examples of usage of "type" and "type_arg":		Examples of usage of "type" and "type_arg":
	* In "Hearts", "type" is the color of the card (1 to 4) and "type_arg" is the value of the card (1, 2, ... 10, J, Q, K).		* In ''Hearts'', "type" represents the color (suite) of the card (1 to 4) and "type_arg" is the value of the card (1, 2, ... 10, J, Q, K).
	* In "Seasons", "type" is the type of the card (~~ex:~~ 1 is Amulet of Air, 2 is Amulet of Fire, etc...). type_arg is not used.		* In ''Seasons'', "type" represents the type of the card (e.g., 1 is Amulet of Air, 2 is Amulet of Fire, etc...). type_arg is not used.
	* In "Takenoko", a Deck component is used for objective cards. "type" is the kind of objective (irrigation/panda/plot) and "type_arg" is the ID of the specific objective to realize (~~ex:~~ "a green bamboo x4"). Note that a second Deck component is used in Takenoko to manage the "garden plot" pile.		* In ''Takenoko'', a Deck component is used for objective cards. "type" is the kind of objective (irrigation/panda/plot) and "type_arg" is the ID of the specific objective to realize (e.g., "green bamboo x4"). Note that a second Deck component is used in ''Takenoko'' to manage the "garden plot" pile.

			'''location''' and '''location_arg''' define where a card is at now. '''location''' is a short string, and '''location_arg''' is an integer.

	'''location''' and '''location_arg'~~'' defines where is~~ the ~~card at now. '''location''' is a short string, and '''location_arg''' is an integer~~.		You can use 'location' and 'location_arg' as you like, to move your card within the game area.

	~~You can use 'location' and 'location_arg' as you want, to move your card on the game area. Although, there~~ are 3 special 'location' that Deck ~~manage specifically~~. You can choose to use - or not ~~to use - these locations~~ depending of your needs:		There are 3 special 'location' values that Deck manages automatically. You can choose to use these locations or not, depending on your needs:
	* 'deck': in 'deck' location~~, cards~~ are placed face down in a ~~pile~~ and are drawn during the game. 'location_arg' is used to specify where the card is in the ~~deck pile~~ (the card with the ~~biggest~~ location_arg is the next to be drawn).		* 'deck': the 'deck' location is a standard draw deck. Cards are placed face down in a stack and are drawn in sequential order during the game. 'location_arg' is used to specify where the card is located within the stack (the card with the highest location_arg value is the next to be drawn).
	* 'hand': in 'hand' location, cards ~~are~~ in ~~the hand of~~ a player. 'location_arg' is set to the ID of ~~this~~ player.		* 'hand': the 'hand' location represents cards in a player's hand. 'location_arg' is set to the ID of each player.
	* 'discard': in 'discard' ~~location, cards are discarded, and are ready to~~ be ~~shuffled~~ into the deck if needed (see "autoreshuffle").		* 'discard': the 'discard' location is used for discard piles. Card in 'discard' may be reshuffled into the deck if needed (see "autoreshuffle").


	Tips: using Deck component, you ~~are going to~~ use generic properties ("location", "type_arg",...) for specific purposes of your game. Thus, during the design step before realizing your game, take 2 minutes to write down ~~what is~~ the meaning of each of ~~this~~ generic properties in the context of your game.		Tips: using the Deck component, you will use generic properties ("location", "type_arg",...) for specific purposes in your game. Thus, during the design step before realizing your game, take a few minutes to write down the exact meaning of each of these generic properties in the context of your game.

	=== Create a new Deck component ===		=== Create a new Deck component ===