Castle Wiki - User contributions [en]

Response

2023-05-07T06:07:44Z

Maricel Ty: /* General */

A '''Response''' is the part of a [[Rule]] that describes what to do when the rule is [[Trigger|triggered]]. One rule typically has many responses, which are run in order from top to bottom.

Typically, responses describe actions that change the state of the [[Deck]]. Some common uses for responses include changing the motion of the player, creating or destroying actors, adding to the player's score, or sending the player to another [[Card]] in the deck.

== List of responses ==
Castle will only show responses that are available for the [[Behavior|Behaviors]] being used on the given [[Blueprint]]. For example, if the blueprint does not have [[Music]], then the "Play this actor's song" response will not appear.

Some responses are contextual to the rule. For example, the "Stop repeating" response is only available if already inside a [[Repeat]] response.

=== General ===

* Create a new [[Actor]] from [[Blueprint]], tell the created actor perform [[response]]
*Create a new [[Actor]] from [[Blueprint]], tell the created actor (none)
* Create a [[Text Box|Text box]]
* Destroy this actor
* Hide all text boxes
* Send player to a different [[Card]]
* Restart this card
* Add [[Tag|Tags]] to this actor
* Remove tags from this actor

=== Order ===

* Move this actor to the front
* Move this actor to the back

=== [[Behavior]] ===

* Enable a behavior
* Disable a behavior
* Modify a property

=== Tell other actors ===

* Tell actors with a [[Tag]] to perform a response
* Tell closest actor with a tag to perform a response
*Tell the [[Collision|Colliding]] actor to perform a response

=== Logic ===

* If a [[Condition]] is met, run a response
* [[Repeat]] N times
* Repeat every N seconds
*Stop repeating
* Wait before a response

=== State ===

* Modify the value of a [[Variable]]
* Reset a variable to its initial value
* Reset all variables to their initial values
* Save a variable to the [[Leaderboard]]
* Show the leaderboard for a variable

=== Inventory ===

* Offer a [[snapshot]] to the player

=== [[Motion]] ===

* Face direction of motion
* Move toward my own angle
* Move toward another actor

=== Sound ===

* Play a sound
* Stop all sound
* Play this actor's [[Music|song]]
* Stop this actor's song
* Stop a track from this actor's song
* Play a pattern from this actor's song
* Play one step from a pattern in this actor's song
* Mute a track from this actor's song
* Unmute a track from this actor's song

=== [[Clock]] ===

* Set the clock tempo

=== [[Camera]] ===

* Follow this with the camera

=== Meta ===

* Add a note to this rule

Shoot 'Em Up Kit

2022-07-31T10:05:14Z

Maricel Ty: Created page with "Sorry. This Is Under Progress"

Sorry. This Is Under Progress

Rhythm Kit

2022-07-31T10:04:31Z

Maricel Ty: Created page with "Sorry. This Is Under Progress"

Sorry. This Is Under Progress

Pinball Kit

2022-07-31T10:03:33Z

Maricel Ty: Created page with "Sorry. This Is Under Progress"

Sorry. This Is Under Progress

Tower Defense Kit

2022-07-31T10:01:44Z

Maricel Ty:

Back:
[[Rhythm Kit]] [[Action Platformer Kit]]
[[Platformer Kit]] [[Golf Course Kit]]
[[Topdown Golf Course Kit]] [[Adventure Kit]]
[[Lab Escape Kit]] [[Shoot 'Em Up Kit]]
[[Pinball Kit]] [[Meadowland Kit]]
[[Race Track Kit]] [[Flappy Kit]]

Tower Defense Kit

2022-07-31T09:55:41Z

Maricel Ty: Blanked the page

Tower Defense Kit

2022-07-31T09:54:56Z

Maricel Ty: Created page with "Entrance Will Do These Rules: Tell Actors With Tag #path to peform Add tag #unconnected Your Turn To Edit!"

Entrance Will Do These Rules: Tell Actors With Tag #path to peform

Add tag #unconnected

Your Turn To Edit!

Rule

2022-07-31T09:52:08Z

Maricel Ty: Edited Rules

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.

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 ==
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 ==
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
Eventually, after the ball reaches the ground and comes to a stop, we want to allow the player to sling again:
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:
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:
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]]. More Decks: [[Topdown Golf Course Kit]] (under progress),
[[Lab Escape Kit]],
[[Tower Defense Kit]]

Topdown Golf Course Kit

2022-07-31T03:31:51Z

Maricel Ty: Created page with "Under Progress."

Under Progress.

Rule

2022-07-31T03:30:53Z

Maricel Ty:

Rule

2022-07-31T03:29:55Z

Maricel Ty: Added A New Link To Decks

Rule

2022-07-31T03:27:39Z

Maricel Ty:

Rule

2022-07-31T03:18:26Z

Maricel Ty:

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.

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 ==
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 ==
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
Eventually, after the ball reaches the ground and comes to a stop, we want to allow the player to sling again:
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:
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:
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]].

Rule

2022-07-30T14:07:27Z

Maricel Ty:

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.

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 ==
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 ==
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
Eventually, after the ball reaches the ground and comes to a stop, we want to allow the player to sling again:
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:
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:
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]].