Deck - Lịch sử thay đổi

Tilalilalou: /* auto-reshuffle */

2019-02-20T09:42:36Z

auto-reshuffle

← Phiên bản cũ		Phiên bản lúc 11:42, ngày 20 tháng 2 năm 2019
Dòng 436:		Dòng 436:

	If you need to notify players when the deck is shuffled, you can setup a callback method using this feature: $this->cards->autoreshuffle_trigger = array('obj' => $this, 'method' => 'deckAutoReshuffle');		If you need to notify players when the deck is shuffled, you can setup a callback method using this feature: $this->cards->autoreshuffle_trigger = array('obj' => $this, 'method' => 'deckAutoReshuffle');

			If you need to use other locations than "deck" and "discard" for auto-reshuffle feature, you can configure it this way: $this->cards->autoreshuffle_custom = array('deck' => 'discard'); (replace 'deck' and 'discard' with your custom locations).

Tilalilalou: /* auto-reshuffle */

2019-02-20T09:38:21Z

auto-reshuffle

← Phiên bản cũ		Phiên bản lúc 11:38, ngày 20 tháng 2 năm 2019
Dòng 434:		Dòng 434:

	Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.		Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.

			If you need to notify players when the deck is shuffled, you can setup a callback method using this feature: $this->cards->autoreshuffle_trigger = array('obj' => $this, 'method' => 'deckAutoReshuffle');

Tilalilalou: /* auto-reshuffle */

2019-02-20T09:34:47Z

auto-reshuffle

← Phiên bản cũ		Phiên bản lúc 11:34, ngày 20 tháng 2 năm 2019
Dòng 432:		Dòng 432:

	To enable auto-reshuffle you must do "$mydeck->autoreshuffle = true" during the setup of the component.		To enable auto-reshuffle you must do "$mydeck->autoreshuffle = true" during the setup of the component.

	Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.		Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.

Tilalilalou vào lúc 09:34, ngày 20 tháng 2 năm 2019

2019-02-20T09:34:39Z

← Phiên bản cũ		Phiên bản lúc 11:34, ngày 20 tháng 2 năm 2019
Dòng 431:		Dòng 431:
	=== auto-reshuffle ===		=== auto-reshuffle ===

			To enable auto-reshuffle you must do "$mydeck->autoreshuffle = true" during the setup of the component.
	Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.		Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.

Tilalilalou vào lúc 15:23, ngày 12 tháng 2 năm 2019

2019-02-12T15:23:31Z

← Phiên bản cũ		Phiên bản lúc 17:23, ngày 12 tháng 2 năm 2019
Dòng 428:		Dòng 428:

	Please note that all "location_arg" will be reset 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.

			=== auto-reshuffle ===

			Every time a card must be retrieved from the "deck" location, if it is empty the "discard" location will be automatically reshuffled into the "deck" location.

Tilalilalou: /* Create a new Deck component */

2019-01-31T17:18:20Z

Create a new Deck component

← Phiên bản cũ		Phiên bản lúc 19:18, ngày 31 tháng 1 năm 2019
Dòng 74:		Dòng 74:
	</pre>		</pre>

	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).		Note that we specify "card" here: the name of our previously created table. This means you can create several "Deck" components with multiple tables:

			<pre>
			$this->firstKindCards = self::getNew( "module.common.deck" );
			$this->firstKindCards ->init( "first_kind_card" );
			$this->secondKindCards = self::getNew( "module.common.deck" );
			$this->secondKindCards ->init( "second_kind_card" );
			</pre>

			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, in 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.

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

2018-09-20T01:00:27Z

The 5 properties of each card

← Phiên bản cũ		Phiên bản lúc 03:00, ngày 20 tháng 9 năm 2018
Dòng 28:		Dòng 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

← Phiên bản cũ		Phiên bản lúc 02:59, ngày 20 tháng 9 năm 2018
Dòng 28:		Dòng 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

← Phiên bản cũ		Phiên bản lúc 06:24, ngày 16 tháng 9 năm 2018
Dòng 51:		Dòng 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>
Dòng 64:		Dòng 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>
Dòng 74:		Dòng 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 vào lúc 04:20, ngày 16 tháng 9 năm 2018

2018-09-16T04:20:37Z

← Phiên bản cũ		Phiên bản lúc 06:20, ngày 16 tháng 9 năm 2018
Dòng 1:		Dòng 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.