Rule - Revision history

Lukalot: Reverted edits by Maricel Ty (talk) to last revision by Ben

2022-08-01T19:53:50Z

Reverted edits by Maricel Ty (talk) to last revision by Ben

← Older revision		Revision as of 19:53, 1 August 2022
Line 17:		Line 17:
	When this stops moving: Enable behavior slingshot		When this stops moving: Enable behavior slingshot
	If the player accidentally slings the ball out of the screen, we count that as losing the game, so we want to start the level over. The golf ball might have a third rule like this one:		If the player accidentally slings the ball out of the screen, we count that as losing the game, so we want to start the level over. The golf ball might have a third rule like this one:
	When this exits the camera viewport~~: Crate text box "The ball fell out of the card" when tapped peform response~~: Restart this card		When this exits the camera viewport: Restart this card
	But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:		But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:
	When this collides with tag #hole: ~~If variable: hits is greater than 1~~ Create text box "You got the ball into the hole! ~~Hits: $hits else Create text box~~ "~~HOLE IN ONE!~~		When this collides with tag #hole: Create text box "You got the ball into the hole!"
			You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].


	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. ~~More Decks: [[Topdown Golf Course Kit]] (under progress),~~
	~~[[Lab Escape Kit]],~~
	~~[[Tower Defense Kit]]~~

Maricel Ty: Edited Rules

2022-07-31T09:52:08Z

Edited Rules

← Older revision		Revision as of 09:52, 31 July 2022
Line 23:		Line 23:


	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. More Decks: [[Topdown Golf Course Kit]] (under progress).		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. More Decks: [[Topdown Golf Course Kit]] (under progress),
			[[Lab Escape Kit]],
			[[Tower Defense Kit]]

Maricel Ty at 03:30, 31 July 2022

2022-07-31T03:30:53Z

← Older revision		Revision as of 03:30, 31 July 2022
Line 23:		Line 23:


	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. More Decks: [[Topdown Golf Course Kit]].		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. More Decks: [[Topdown Golf Course Kit]] (under progress).

Maricel Ty: Added A New Link To Decks

2022-07-31T03:29:55Z

Added A New Link To Decks

← Older revision		Revision as of 03:29, 31 July 2022
Line 23:		Line 23:


	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]]. More Decks: [[Topdown Golf Course Kit]].

Maricel Ty at 03:27, 31 July 2022

2022-07-31T03:27:39Z

← Older revision		Revision as of 03:27, 31 July 2022
Line 19:		Line 19:
	When this exits the camera viewport: Crate text box "The ball fell out of the card" when tapped peform response: Restart this card		When this exits the camera viewport: Crate text box "The ball fell out of the card" when tapped peform response: Restart this card
	But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:		But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:
	When this collides with tag #hole: If variable: hits is greater than 1 Create text box "You got the ball into the hole! Hits: $hits else		When this collides with tag #hole: If variable: hits is greater than 1 Create text box "You got the ball into the hole! Hits: $hits else Create text box "HOLE IN ONE!



	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].

Maricel Ty at 03:18, 31 July 2022

2022-07-31T03:18:26Z

← Older revision		Revision as of 03:18, 31 July 2022
Line 17:		Line 17:
	When this stops moving: Enable behavior slingshot		When this stops moving: Enable behavior slingshot
	If the player accidentally slings the ball out of the screen, we count that as losing the game, so we want to start the level over. The golf ball might have a third rule like this one:		If the player accidentally slings the ball out of the screen, we count that as losing the game, so we want to start the level over. The golf ball might have a third rule like this one:
	When this exits the camera viewport: Restart this card		When this exits the camera viewport: Crate text box "The ball fell out of the card" when tapped peform response: Restart this card
	But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:		But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:
	When this collides with tag #hole: Create text box "You got the ball into the hole! Hits: $hits		When this collides with tag #hole: If variable: hits is greater than 1 Create text box "You got the ball into the hole! Hits: $hits else
	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].

Maricel Ty at 14:07, 30 July 2022

2022-07-30T14:07:27Z

← Older revision		Revision as of 14:07, 30 July 2022
Line 19:		Line 19:
	When this exits the camera viewport: Restart this card		When this exits the camera viewport: Restart this card
	But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:		But if the player succeeds in putting the golf ball in the hole, we want to show a message saying they won:
	When this collides with tag #hole: Create text box "You got the ball into the hole!"		When this collides with tag #hole: Create text box "You got the ball into the hole! Hits: $hits
	You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].		You can find a (slightly more complex) version of these exact rules if you check out the [[Golf Course Kit]].

Ben: Add a screenshot showing an example of a blueprint with rules

2022-05-17T17:14:10Z

Add a screenshot showing an example of a blueprint with rules

← Older revision		Revision as of 17:14, 17 May 2022
Line 1:		Line 1:
	A Rule is a unit of logic in Castle decks. Rules can be added to [[blueprint\|blueprints]] in order to change the behavior of the blueprint in response to specific events or under certain conditions.		A Rule is a unit of logic in Castle decks. Rules can be added to [[blueprint\|blueprints]] in order to change the behavior of the blueprint in response to specific events or under certain conditions.
			[[File:Golf-ball-rules.jpg\|alt=A screenshot of a blueprint in the Castle editor showing several Rules\|thumb\|An example of a blueprint containing several rules.]]
	Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.		Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.

Ben at 23:51, 12 May 2022

2022-05-12T23:51:42Z

← Older revision		Revision as of 23:51, 12 May 2022
Line 3:		Line 3:
	Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.		Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.

	There are many different possible triggers and even more responses. Simple rules can be used by anybody to add basic logic to a game or a piece of art, like playing a sound effect when the player taps an item, or restarting the card when the player ~~falls off a ledge~~. When rules start to get more complex, they can do almost anything. Advanced users have used them to make procedural art, simulations, and even basic 3d games. Rules are one of the most powerful core elements of Castle.		There are many different possible triggers and even more responses. Simple rules can be used by anybody to add basic logic to a game or a piece of art, like playing a sound effect when the player taps an item, or restarting the card when the player [[Collision\|collides]] with an enemy. When rules start to get more complex, they can do almost anything. Advanced users have used them to make procedural art, simulations, and even basic 3d games. Rules are one of the most powerful core elements of Castle.

	== Adding and editing rules ==		== Adding and editing rules ==

Ben at 21:47, 12 May 2022

2022-05-12T21:47:34Z

← Older revision		Revision as of 21:47, 12 May 2022
Line 7:		Line 7:
	== Adding and editing rules ==		== Adding and editing rules ==
	To add rules to blueprints, first open the [[Inspector]] for the blueprint you'd like to edit, then go to the [[Logic]] tab.		To add rules to blueprints, first open the [[Inspector]] for the blueprint you'd like to edit, then go to the [[Logic]] tab.

			== Learning how to write rules ==
			The best way to learn Rules is to follow a guide, such as [[Guides:How to make your first Castle deck\|How to make your first Castle deck]], which walks you through making your first Rules. Secondly, consider starting with one of the premade Castle [[Kits]], and then inspect the blueprints that come with it. Lastly, you can also [[View Source\|View the Source]] of any deck to see how it was made.

	== Examples of rules ==		== Examples of rules ==
	The best way to learn Rules is to start with one of the premade Castle [[Kits]] and inspect the blueprints that come with it. You can also [[View Source\|View the Source]] of any deck to see how it was made.

	As an illustrative example, imagine a golf game. You want to be able to sling the golf ball when it's sitting on the ground, but after it's flying through the air, the player shouldn't be able to sling it anymore. The golf ball might have a rule like this:		As an illustrative example, imagine a golf game. You want to be able to sling the golf ball when it's sitting on the ground, but after it's flying through the air, the player shouldn't be able to sling it anymore. The golf ball might have a rule like this:
	When this is slung: Disable behavior slingshot		When this is slung: Disable behavior slingshot

← Older revision		Revision as of 17:14, 17 May 2022
Line 1:		Line 1:
	A Rule is a unit of logic in Castle decks. Rules can be added to [[blueprint\|blueprints]] in order to change the behavior of the blueprint in response to specific events or under certain conditions.		A Rule is a unit of logic in Castle decks. Rules can be added to [[blueprint\|blueprints]] in order to change the behavior of the blueprint in response to specific events or under certain conditions.
			[[File:Golf-ball-rules.jpg\|alt=A screenshot of a blueprint in the Castle editor showing several Rules\|thumb\|An example of a blueprint containing several rules.]]
	Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.		Each rule consists of a [[Trigger]] and one or more [[response\|Responses]]. A trigger is the part of a Rule that describes when to run that rule, such as '''When this is tapped'''. Responses are the part of the rule that describe what to do after the rule is triggered, such as '''Destroy this actor'''. A blueprint can have many rules, but it doesn't have to have any.