Guides:Castle Crash Course - Revision history

Lukalot: editor notes, rule uses section

2022-06-08T09:42:49Z

editor notes, rule uses section

← Older revision		Revision as of 09:42, 8 June 2022
Line 1:		Line 1:
	''<u>This article is an outline for a future collection of guides, and is incomplete</u>''		''<u>This article is an outline for a future collection of guides, and is incomplete</u>''<blockquote>The following is a rough draft

	~~The following is~~ a ~~possible rough draft outline~~		Points to consider revising/improving:

			- Walk through a creation process step by step or explain feature by feature?

			- General structure and ordering</blockquote>

	= Introduction =		= Introduction =
Line 47:		Line 51:
	If we want to make a nice title piece for your intro card, we definitely need to know how to add art to our blueprints. The good news is that there's an art and drawing tool built right into Castle. Just tap the empty "Artwork" frame with the pencil icon on it. This will open the [[Art\|art tool]].		If we want to make a nice title piece for your intro card, we definitely need to know how to add art to our blueprints. The good news is that there's an art and drawing tool built right into Castle. Just tap the empty "Artwork" frame with the pencil icon on it. This will open the [[Art\|art tool]].

	Take a look around around. There are lots of tools and options here. On the left side, we see a bar of selectable tools:		Take a look around around. There are lots of tools and options here. On the left side, we see a bar of selectable tools:<blockquote>Should we be listing each tool or addressing the tools as they're needed? If we only address the tools as needed, how long will it take for the user to learn the tools, and what kind of project/learning path will we need to take to teach them about each tool?</blockquote>

	* '''Pencil tool''': This tool lets you draw shapes and lines		* '''Pencil tool''': This tool lets you draw shapes and lines
	* '''Bucket tool''': Fills existing spaces with new colors		* '''Bucket tool''': Fills existing spaces with new colors
Line 64:		Line 67:

	== Fleshing out your introduction deck ==		== Fleshing out your introduction deck ==
	Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:[[File:Nikki_Profile_Image_with_spikes.png\|frameless]]As you can see, it lists a few facts about @nikki's profile, like how there are experiments and games on it!		<blockquote>This section jumps quickly to a finished and aesthetically pleasing deck outcome, without explanation of the individual art steps to get there. It may be better to walk the creator through each step of drawing the button and rainbow, and suggest they make further changes on their own.</blockquote>Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:[[File:Nikki_Profile_Image_with_spikes.png\|frameless]]As you can see, it lists a few facts about @nikki's profile, like how there are experiments and games on it!

	Here are some ideas for your own introduction deck:		Here are some ideas for your own introduction deck:
Line 74:		Line 77:

	== Publishing your intro deck ==		== Publishing your intro deck ==
	[[File:How to share.png\|thumb\|531x531px]]		<blockquote>Publishing seems like a good motivator, but is best worded as a prompt to consider rather than of a requirement. Revise this section</blockquote>[[File:How to share.png\|thumb\|531x531px]]
	You've done it! You have a cool intro deck ready to share with the rest of the Castle world. The last step in making a deck is to publish it! You can publish your new introduction deck to your profile and the public feed by setting it to "published" from the share screen. Here's how you can navigate there:		You've done it! You have a cool intro deck ready to share with the rest of the Castle world. The last step in making a deck is to publish it! You can publish your new introduction deck to your profile and the public feed by setting it to "published" from the share screen. Here's how you can navigate there:

Line 87:		Line 90:
	'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''		'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''

	Your deck is bustling with shapes and colors, but it's lacking something: There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive machines or games that can do things that even the creators would never have expected. One ~~such~~ thing to ~~add~~ to your decks is movement~~, which can make your actors come to life on the screen~~.		Your deck is bustling with shapes and colors, but it's lacking something: There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive machines or games that can do things that even the creators would never have expected. One thing you can use to bring life to your decks is movement.

	~~Create~~ a new deck where we can experiment with movement.		Let's create a new deck where we can experiment with movement. In this deck, let's try adding the "Ball" default blueprint, which is listed near the bottom of the "Add a blueprint" list. If you don't remember how to add a new blueprint to the deck, or any other detail of how to make and edit actors, you can always check back to the previous chapter.

	In this deck, let's try adding the "Ball" default blueprint, which is listed near the bottom of the "Add a blueprint" list. If you don't remember how to add a new blueprint to the deck, or any other detail of how to make and edit actors, you can always check back to the previous chapter.

	Once the ball is in the scene, try pressing play! You should see that the ball falls out of the scene. This is because there are no solid walls around the screen edges, or really anywhere, to stop the ball from keeping falling. We can fix this by adding some solid actors. Let's try adding an actor with the Border blueprint, which is also a default option in the "Add a blueprint" list. Once you've selected it, drag it from the belt and center it on the scene.		Once the ball is in the scene, try pressing play! You should see that the ball falls out of the scene. This is because there are no solid walls around the screen edges, or really anywhere, to stop the ball from keeping falling. We can fix this by adding some solid actors. Let's try adding an actor with the Border blueprint, which is also a default option in the "Add a blueprint" list. Once you've selected it, drag it from the belt and center it on the scene.
Line 107:		Line 108:
	* Bounce allows a solid actor to regain some of it's reflected velocity when colliding with other solids.		* Bounce allows a solid actor to regain some of it's reflected velocity when colliding with other solids.
	* Slowdown causes an actor to lose velocity gradually over time.		* Slowdown causes an actor to lose velocity gradually over time.
	* Axis lock prevents an actor from moving on a certain axis, ~~wether~~ it be their, up (y), down (x), or rotational axis.		* Axis lock prevents an actor from moving on a certain axis, whether it be their up (y), down (x), or rotational axis.

	In this case, let's add a new behavior, [[Drag]]!		In this case, let's add a new behavior, [[Drag]]!
Line 132:		Line 133:

	<image of a rule in the inspector for an enemy blueprint>		<image of a rule in the inspector for an enemy blueprint>

			== Basic rule use ==
			Now that you understand the components of a rule, let's take a look at how we could use rules to do some useful things in our deck.<blockquote>This section seems overwhelming / it might be better to take only one subject at a time. In fact, dedicating chapters or large parts of chapters to single useful responses seems useful</blockquote>

			=== Actors that can't leave the screen ===
			In chapter two, we created a ball actor and it fell out of the screen when we pressed play. Imagine if instead of falling out of the screen, it moved through the screen edge and out of the ceiling. We can do that with rules!

			* Make a ball actor with the ball default blueprint and place it in an empty scene
			* Add a new rule on the ball actor which checks if the ball has left the screen, and sends it to the opposite side of the screen depending on which side of the screen that it left

			When this leaves the camera viewport

			if x is greater than 5, modify property x to -5

			if x is less than -5, modify property x to 5

			if y is greater than 7, modify property y to -7

			if y is less than -7, modify property y to 7

			=== Actors that grow when they're tapped ===

			* Draw some art for a new empty actor, or use the "Wall" default blueprint.
			* Add a new rule to the actor that uses the "When this is tapped" trigger, and sets the actor's width and height to be larger whenever it is tapped.

			When this is tapped

			modify property Width Scale to 1 (relative)

			modify property Height Scale to 1 (relative)

			=== Actors that play a sound when colliding ===

			* Draw some art of rocks or characters that can bounce around, or use the "ball" default blueprint. Make sure your blueprint has the 'gravity', 'bounce', and 'drag' behaviors.
			* Add a rule to the actors

	== Making a game with rules ==		== Making a game with rules ==
	You've learned a lot so far in this tutorial, and now that you understand rules a bit better, we can build a small game as this chapter's project.		You've learned a lot so far in this tutorial, and now that you understand rules a bit better, we can build a small game as this chapter's project. With the Castle knowledge you've taken on so far, you could already try hundreds of different game concepts! One of those possibilities, which we'll build in this chapter, is an ''infinite runner'' game!

	= Chapter 4 - Labeling actors with Tags =		= Chapter 4 - Labeling actors with Tags =

Lukalot: remove old nikki intro image

2022-06-06T20:52:41Z

remove old nikki intro image

← Older revision		Revision as of 20:52, 6 June 2022
Line 64:		Line 64:

	== Fleshing out your introduction deck ==		== Fleshing out your introduction deck ==
	Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:		Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:[[File:Nikki_Profile_Image_with_spikes.png\|frameless]]As you can see, it lists a few facts about @nikki's profile, like how there are experiments and games on it!
	[[File:~~Nikki Profile Image with spikes.png\|thumb]]~~
	~~[[File:Nikki_Intro_Deck~~.png\|frameless]]

	As you can see, it lists a few facts about @nikki's profile, like how there are experiments and games on it!

	Here are some ideas for your own introduction deck:		Here are some ideas for your own introduction deck:

Lukalot: New intro deck image

2022-06-06T20:51:46Z

New intro deck image

← Older revision		Revision as of 20:51, 6 June 2022
Line 65:		Line 65:
	== Fleshing out your introduction deck ==		== Fleshing out your introduction deck ==
	Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:		Great work so far! You've learned how to create blueprints, draw artwork, and place new actors. Now you're free to flesh out your intro deck with more art and designs! Here's what an example of an introduction deck for the profile <code>@Nikki</code> might look like:
			[[File:Nikki Profile Image with spikes.png\|thumb]]
	[[File:Nikki_Intro_Deck.png\|frameless]]		[[File:Nikki_Intro_Deck.png\|frameless]]

Lukalot: Chapter 3 project

2022-06-06T10:55:54Z

Chapter 3 project

← Older revision		Revision as of 10:55, 6 June 2022
Line 118:		Line 118:

	= Chapter 3 - Using Rules =		= Chapter 3 - Using Rules =
	'''''What you'll build in this chapter:''' Infinite ~~runner~~ game''		'''''What you'll build in this chapter:''' Infinite flyer game''

	In this section, you'll learn about rules, and how they can let you control and design your actors to do interesting things.		In this section, you'll learn about rules, and how they can let you control and design your actors to do interesting things.
Line 136:		Line 136:

	<image of a rule in the inspector for an enemy blueprint>		<image of a rule in the inspector for an enemy blueprint>

			== Making a game with rules ==
			You've learned a lot so far in this tutorial, and now that you understand rules a bit better, we can build a small game as this chapter's project.

	= Chapter 4 - Labeling actors with Tags =		= Chapter 4 - Labeling actors with Tags =

Lukalot: what are rules?

2022-06-06T09:17:10Z

what are rules?

← Older revision		Revision as of 09:17, 6 June 2022
Line 118:		Line 118:

	= Chapter 3 - Using Rules =		= Chapter 3 - Using Rules =
	'''''What you'll build in this chapter:''' ~~Incremental game / Story game /~~ Infinite runner game''		'''''What you'll build in this chapter:''' Infinite runner game''

	Rules are the ~~secret~~ sauce that ~~makes~~ some blueprints and their actors ~~truly~~ unique and special. In this chapter we'll take a look at how rules can let you build actors with all sorts of interesting purposes.		In this section, you'll learn about rules, and how they can let you control and design your actors to do interesting things.

			== What are rules? ==
			[[Rule\|Rules]] are the special sauce that make some blueprints and their actors behave in unique and special ways. In this chapter we'll take a look at how rules can let you build actors with all sorts of interesting purposes.

			Rules can be added to a blueprint via the [[Logic]] tab of the inspector. Rules are made up of two main parts, the Trigger and the Responses.

			<image of a simple rule on the right>

			=== Triggers ===
			Triggers are the part of a rule which determines when it will run. An example of a trigger is "When this is created", which will cause the rule to run as soon as the actor containing the rule is created.

			=== Responses ===
			Responses determine what the rule does when the trigger is activated. For example, if the rule has a response that says "Play a sound", the actor will play the sound whenever the rule is triggered. Here's a rule that play's a voice clip whenever a new enemy appears:

			<image of a rule in the inspector for an enemy blueprint>

	= Chapter 4 - Labeling actors with Tags =		= Chapter 4 - Labeling actors with Tags =

Lukalot: remove bonus section

2022-06-03T11:02:44Z

remove bonus section

← Older revision		Revision as of 11:02, 3 June 2022
Line 87:		Line 87:

	Woohoo, your deck is now public, so other castle users can see it and play it themselves. Welcome to Castle, and good job finishing chapter one of the Crash Course!		Woohoo, your deck is now public, so other castle users can see it and play it themselves. Welcome to Castle, and good job finishing chapter one of the Crash Course!

	~~= Bonus Section: Getting to know the inspector General tab =~~
	~~This bonus section takes a look at the general tab of the inspector and explains each of it's features!~~

	~~=== Artwork ===~~
	Artwork is the first section of the inspector. It features one or multiple ''art frames'' and a "plus" button to add more.Art frames are animated between when the actor's animation is played. You can also change how the animation is treated when the actor is created with the "play when created' options.

	* Still will not play, but can be modified with [[Logic]]
	* Once will play the animation once, and stop when it reaches the end
	* Loop will keep playing the animation repeatedly, returning to the beginning and continuing when it reaches the end.

	Frames per second is how many animation frames will appear during a second while the actor is animating. It's set to 4 by default, which means that for every second that passes while the actor is animating, four of the actors frames will be flipped through.

	~~The Visible option determines whether the actor displays it's art on screen or not.~~

	~~=== Tags ===~~
	~~Tags are something we'll discuss in a future chapter, but they're a way of labelling and managing your actors!~~

	~~=== Music ===~~
	~~You can use the music section to write custom songs into actors to be played. There'll also be a chapter about this!~~

	~~=== Layout ===~~
	Layout determines the scale and orientation of the actor. For example, editing width to 2 instead of the default 1 will cause it to be stretched. "Apply layout to blueprint" will modify all actors that use this blueprint in the scene to share the settings that you make on the blueprint. Otherwise, they'll retain their own scale and orientation. Actors that have been newly dragged from the belt will always share the blueprints properties.

	~~The "Relative to camera" option will make your actors always move with the screen. Very handy for onscreen UI and some special effects!~~

	= Chapter 2 - Movement, physics, and touchable decks =		= Chapter 2 - Movement, physics, and touchable decks =

Lukalot: Behaviors

2022-06-02T10:49:55Z

Behaviors

← Older revision		Revision as of 10:49, 2 June 2022
Line 129:		Line 129:
	You've seen what a physics actor can do on the outside, but what do they look like on the inside? We'll find out while trying to turn our "Ball" blueprint into a "Marble" blueprint by editing it.		You've seen what a physics actor can do on the outside, but what do they look like on the inside? We'll find out while trying to turn our "Ball" blueprint into a "Marble" blueprint by editing it.

	To begin editing, let's open the inspector on the Ball actor by selecting it and pressing Edit Blueprint. From the inspector, open the Movement tab and take a look around. The movement tab contains the blueprint's [[Behavior\|behaviors]], which are ~~different~~ features and qualities that you can enable for the blueprint's ~~actors~~.		To begin editing, let's open the inspector on the Ball actor by selecting it and then pressing Edit Blueprint. From the inspector, open the Movement tab and take a look around. The movement tab contains the blueprint's [[Behavior\|behaviors]], which are features and qualities that you can enable for the blueprint which change what it can do as an actor. You can experiment at any time with adding and removing behaviors.

			Here are some behaviors to experiment with:

			* Solid determines whether your actor can move through other actors which are solid.
			* Bounce allows a solid actor to regain some of it's reflected velocity when colliding with other solids.
			* Slowdown causes an actor to lose velocity gradually over time.
			* Axis lock prevents an actor from moving on a certain axis, wether it be their, up (y), down (x), or rotational axis.

			In this case, let's add a new behavior, [[Drag]]!

			The drag behavior enables dragging for the actor, so that it can be pressed and dragged around in the scene by the player. By enabling drag on the Marble actor, the player can now have some fun tossing it around. Try it yourself!

	= Chapter 3 - Using Rules =		= Chapter 3 - Using Rules =

Lukalot: behaviors

2022-06-01T10:55:45Z

behaviors

← Older revision		Revision as of 10:55, 1 June 2022
Line 124:		Line 124:
	Once the ball is in the scene, try pressing play! You should see that the ball falls out of the scene. This is because there are no solid walls around the screen edges, or really anywhere, to stop the ball from keeping falling. We can fix this by adding some solid actors. Let's try adding an actor with the Border blueprint, which is also a default option in the "Add a blueprint" list. Once you've selected it, drag it from the belt and center it on the scene.		Once the ball is in the scene, try pressing play! You should see that the ball falls out of the scene. This is because there are no solid walls around the screen edges, or really anywhere, to stop the ball from keeping falling. We can fix this by adding some solid actors. Let's try adding an actor with the Border blueprint, which is also a default option in the "Add a blueprint" list. Once you've selected it, drag it from the belt and center it on the scene.

	Now if you press play, you'll notice that your ball stays inside the boundaries! As usual on Castle, we can modify ~~anything and~~ everything to ~~build~~ anything we want. You're probably seeing where this is going with the Marble Machine idea!		Now if you press play, you'll notice that your ball stays inside the boundaries! As usual on Castle, we can modify everything to turn it into anything we want. You're probably seeing where this is going with the Marble Machine idea!

	== Editing physics ourselves ==		== Editing physics ourselves with behaviors ==
	You've seen what a physics actor can do on the outside, but what do they look like on the inside? We'll find out while trying to turn our "Ball" blueprint into a "Marble" blueprint by editing it.		You've seen what a physics actor can do on the outside, but what do they look like on the inside? We'll find out while trying to turn our "Ball" blueprint into a "Marble" blueprint by editing it.

	To begin editing, let's open the inspector on the Ball actor by selecting it and pressing Edit Blueprint. From the inspector, open the Movement tab and take a look around.		To begin editing, let's open the inspector on the Ball actor by selecting it and pressing Edit Blueprint. From the inspector, open the Movement tab and take a look around. The movement tab contains the blueprint's [[Behavior\|behaviors]], which are different features and qualities that you can enable for the blueprint's actors.

	= Chapter 3 - Using Rules =		= Chapter 3 - Using Rules =
	'''''What you'll build in this chapter:'''''		'''''What you'll build in this chapter:''' Incremental game / Story game / Infinite runner game''

	Rules are the secret sauce that makes some blueprints and their actors truly unique and special. In this chapter we'll take a look at how rules can let you build actors with all sorts of interesting purposes.		Rules are the secret sauce that makes some blueprints and their actors truly unique and special. In this chapter we'll take a look at how rules can let you build actors with all sorts of interesting purposes.

Lukalot: systems -> machines or games

2022-05-31T11:20:31Z

systems -> machines or games

← Older revision		Revision as of 11:20, 31 May 2022
Line 116:		Line 116:
	'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''		'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''

	Your deck is bustling with shapes and colors, but it's lacking something: There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive ~~systems~~ that can do things that even the creators would never have expected. One such thing to add to your decks is movement, which can make your actors come to life on the screen.		Your deck is bustling with shapes and colors, but it's lacking something: There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive machines or games that can do things that even the creators would never have expected. One such thing to add to your decks is movement, which can make your actors come to life on the screen.

	Create a new deck where we can experiment with movement.		Create a new deck where we can experiment with movement.

Lukalot: chapter 3 detail

2022-05-31T11:11:23Z

chapter 3 detail

← Older revision		Revision as of 11:11, 31 May 2022
Line 116:		Line 116:
	'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''		'''''What you'll learn to build in this chapter:''' A fancy Rube Goldberg Marble Machine!''

	Your deck is bustling with shapes and colors, but it's lacking something. There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive systems that can do things that even the creators would never have expected. One such thing to add to your decks is movement, which can make your actors come to life on the screen.		Your deck is bustling with shapes and colors, but it's lacking something: There's no movement. Castle decks aren't just about still art, sometimes they're about making interactive systems that can do things that even the creators would never have expected. One such thing to add to your decks is movement, which can make your actors come to life on the screen.

	Create a new deck where we can experiment with movement.		Create a new deck where we can experiment with movement.
Line 134:		Line 134:
	'''''What you'll build in this chapter:'''''		'''''What you'll build in this chapter:'''''

	~~Using~~ rules ~~to craft custom events and behaviors~~		Rules are the secret sauce that makes some blueprints and their actors truly unique and special. In this chapter we'll take a look at how rules can let you build actors with all sorts of interesting purposes.

	= Chapter 4 - Labeling actors with Tags =		= Chapter 4 - Labeling actors with Tags =