When just starting out in game development, it is very common to want to jump right in to making your dream game. If you love your ideas, I would suggest waiting, at least for a bit. To do your game justice, first develop some skills. You can build these skills through repeated simple successes that lead to incrementally more challenging and rewarding goals. With this approach in mind, this project is an ideal starting point for beginners. We will cover a large variety of game topics like physics, handling user input, and even some scripting.
Unity
Handling User Input
Most projects you will create in Unity are probably intended to be interactive. They should be able to respond to mouse clicks and drags, keyboard, touch, or other forms of user input. This tutorial will cover a variety of options by which you can manage these types of events.
Scratch To Unity: Operators
This post provides a handy reference guide to go from Scratch’s “Operators” category of code blocks to C# with Unity.
Scratch To Unity: Sensing
This post provides a handy reference guide to go from Scratch’s “Sensing” category of code blocks to C# with Unity.
Scratch To Unity: Control
This post provides a handy reference guide to go from Scratch’s “Control” category of code blocks to C# with Unity.
Scratch To Unity: Events
This post provides a handy reference guide to go from Scratch’s “Events” category of code blocks to C# with Unity.
Scratch To Unity: Sound
This post provides a handy reference guide to go from Scratch’s “Sound” category of code blocks to C# with Unity.
Scratch To Unity: Looks
This post provides a handy reference guide to go from Scratch’s “Looks” category of code blocks to C# with Unity.
Scratch To Unity: Motion
This post provides a handy reference guide to go from Scratch’s “Motion” category of code blocks to C# with Unity.
Scratch To Unity: Scripting Over Time
Scratch has several code blocks that can take time to complete. For example, you might chain together several “say” blocks to present a conversation. Each block will then pause the execution of that stack until it completes. Up to this point, all of the code we have learned has been synchronous. This means that even if you may know enough to change the text on your UI, that each statement would run one after another so fast that you wouldn’t be able to read each message. Not to worry, we can also obtain a similar result, and we will learn all about it in this lesson.