\nAcknowledgements

Thanks to MakeCode Arcade forum user rymc88 for the inspiration behind some of the content in the Part zero appendix on vector math.

",{"_839":840,"_43":44,"_47":48,"_45":46,"_65":66,"_841":842,"_1057":837},"previewContent","

\n \n
- \n Notes about this preview edition\n
\n
\n Part zero: A history of video games\n
- \n About the cover\n
- \n Brief contents\n
  - \n A history of video games\n
  \n
- \n Introduction to Part zero\n
  - \n About the series\n
  - \n Intended audience\n
  - \n Titles in the series\n
  - \n About the book\n
  - \n Prior knowledge\n
  - \n Book web site and link codes\n
  \n
- \n Hello, world! Introducing MakeCode Arcade\n
  - \n Learning objectives\n
  - \n About Microsoft MakeCode\n
  - \n View a MakeCode Arcade project\n
  - \n Start MakeCode Arcade\n
  - \n Your first MakeCode Arcade project\n
  - \n Working with projects\n
  - \n Working with hardware\n
  - \n Sharing your projects\n
  - \n History of MakeCode Arcade\n
  \n
- \n Hello, it’s me! (Or is it I?)—Sprites and your hero character\n
  - \n Learning objectives\n
  - \n Additional controls in the MakeCode editor\n
  - \n Working with tutorials\n
  - \n Moving around\n
  - \n Using the image editor\n
  - \n Screen coordinates\n
  - \n Placing your character\n
  - \n Animating your character\n
  - \n Installing extensions\n
  - \n Creating a walking animation\n
  - \n Creating a spinning wheel\n
  - \n More complex animations\n
  - \n Making a background\n
  - \n Animated backgrounds\n
  - \n Artwork and prototypes\n
  - \n Additional practice with the image editor\n
  - \n Answers to review questions\n
  \n
- \n Which way did it go? Decisions, conditionals, and basic game physics\n
  - \n Learning objectives\n
  - \n Software development life cycle\n
  - \n Planning a project\n
  - \n Princess Pizza\n
  - \n Documentation in Blocks programs\n
  - \n Bouncing Burger\n
  - \n Event-driven programming\n
  - \n Sprite types\n
  - \n Pong\n
  - \n Pong simplified\n
  - \n Velocity\n
  - \n Adding sound effects\n
  - \n Determining the game’s end\n
  - \n The on game update block\n
  - \n Boolean expressions\n
  - \n Correcting an error\n
  - \n Acceleration\n
  - \n Decision structures\n
  - \n Additional tutorials\n
  - \n Answers to exercises\n
  \n
- \n What’s the score? Variables and data types\n
  - \n Learning objectives\n
  - \n Which button?\n
  - \n Pong part 2: Complete one-player game\n
  - \n Pong part 3: Complete two-player game\n
  - \n Introduction to variables\n
  - \n Creating variables\n
  - \n Naming conventions\n
  - \n Variable scope\n
  - \n Data types in Blocks\n
  - \n Guess My Number\n
  - \n Acey Deucey\n
  - \n Answers to exercises\n
  \n
- \n Zap! Debugging part 1\n
  - \n Playing the role of the computer\n
  - \n Using messages for debugging\n
  \n
- \n I’ve made some enemies—Introduction to object-oriented programming\n
  - \n Visual effects\n
  \n
- \n Debugging part 2\n
- \n Over … and over … and over again—Loops\n
- \n Who’s above me? Who’s next to me? Arrays and lists\n
- \n Better than right-click-duplicate—Functions\n
  - \n Naming convention\n
  - \n Local variables revisited\n
  \n
- \n Fun name :-) - Strings\n
  - \n Writing text on the screen\n
  \n
- \n Fun name :-) - Tile maps and platformers\n
  - \n Tile maps\n
  - \n Platformers\n
  - \n Mazes?\n
  \n
- \n What’s your name again? Persisting data\n
  - \n Session object\n
  \n
- \n Stranger, danger! Security and privacy\n
- \n It’s alive! Artificial intelligence\n
- \n Fun name :-) - Searching and sorting\n
- \n Where to now?\n
  - \n Additional books in the series\n
  - \n Learn other languages and programming environments\n
  - \n Other games to try to build in MakeCode Arcade\n
  - \n Other programming books\n
  - \n More on the history of video games\n
  \n
- \n Appendix - A Blocks style guide\n
  - \n Project description\n
  - \n Variable and function naming\n
  - \n Function description\n
  \n
- \n Appendix - Common game structures\n
  - \n Shoe of cards\n
  - \n Dice\n
  \n
- \n Appendix - Stopwatch in Blocks\n
  - \n Part I: Basic stopwatch\n
  - \n Finished code\n
  - \n Developing the project plan\n
  - \n Building the project\n
  - \n Next steps\n
  - \n Part II: Advanced stopwatch\n
  - \n Finished code\n
  - \n Adding to the project plan\n
  - \n Incorporate changes into code\n
  - \n Next steps\n
  \n
- \n Appendix - Common game mechanics\n
  - \n Shuffling\n
  \n
- \n Appendix - Advanced graphics\n
  - \n Parallax (sprites with depth)\n
  \n
- \n Appendix - Multiplayer games\n
- \n Appendix - Vector math\n
  - \n Revisiting velocity\n
  - \n Velocity vectors\n
  - \n Angles\n
  - \n Review of right triangles\n
  - \n Trigonomotric functions and right triangles\n
  - \n Practice with velocity vectors\n
  - \n Representing π\n
  - \n Sprite travelling in a random direction\n
  - \n Another challenge\n
  - \n Final challenge\n
  \n
- \n Appendix - A template for Blocks games\n
  - \n Splash screen\n
  - \n Attract mode\n
  - \n Button handlers\n
  \n
- \n Appendix - Additional Blocks games (showcase)\n
  - \n Additional clones\n
  \n
- \n Credits and licenses\n
\n
\n Part zero mark II: Time to type!\n
- \n About the cover\n
- \n Brief contents\n
- \n Introduction to Part zero mark II\n
  - \n About the series\n
  - \n Intended audience\n
  - \n Titles in the series\n
  - \n About the book\n
  - \n Prior knowledge\n
  - \n Book web site and link codes\n
  \n
- \n Hello, World! I’m typing! Introducing JavaScript\n
  - \n Transitioning from Blocks to JavaScript\n
  - \n Style guide\n
  \n
- \n To grandmother’s house—Revisiting topics from a JavaScript perspective\n
  - \n SDLC and documentation\n
  - \n Sprites\n
  - \n Variables and scope\n
  - \n Functions\n
  \n
- \n Return of the Jedi—Object-oriented programming basics\n
- \n ‘Round and ‘round we go—Loops and arrays\n
- \n Hold this, will ya? Working with GitHub\n
  - \n Introduction to agile methods\n
  - \n Publishing with GitHub\n
  \n
- \n Our first game—Card game?\n
- \n Our second game—Tabletop board game\n
- \n Our third game—Return to arcade games\n
- \n Our fourth game—Another arcade game\n
- \n Fun title :-) - Advanced graphics and physics\n
  - \n Parallax (Revisit of Part zero appendix)\n
  - \n Drawing directly to the screen\n
  - \n Simulating three dimensions\n
  \n
- \n Fun title :-) - Searching and sorting\n
- \n Fun title :-) - Introduction to data structures and algorithms\n
- \n Where to now?\n
  - \n Additional books in the series\n
  - \n Learn other languages and programming environments\n
  - \n Other games to try to build in MakeCode Arcade\n
  - \n Other programming books\n
  - \n More on the history of video games\n
  \n
- \n Appendix - A TypeScript style guide\n
- \n Appendix - Common game structures\n
  - \n Shoe of cards\n
  - \n Dice\n
  \n
- \n Appendix - Stopwatch in TypeScript\n
  - \n Introduction\n
  - \n Finished code\n
  - \n Working with the Text Sprite in TypeScript\n
  - \n Object-oriented design\n
  - \n Creating the Stopwatch class\n
  - \n Adding functionality to the Stopwatch class\n
  - \n Extras\n
  \n
- \n Appendix - Common game mechanics\n
  - \n Shuffling\n
  \n
- \n Appendix - Lambda and anonymous functions\n
- \n Appendix - Filtering and iterating with method calls\n
- \n Appendix - A template for JavaScript Games\n
- \n Appendix - Additional JavaScript games (showcase)\n
- \n Credits and licenses\n
- \n Bonus chapter: Can I be a computer scientist?\n
  - \n Can I be a computer scientist?\n
  - \n Do I need to be good at math?\n
  - \n I really like computers, but I don’t really like programming. Are there other things that I can do?\n
  \n
- \n Glossary\n
- \n Timeline of video games\n
- \n Acknowledgements\n
- \n About the author\n
- \n Colophon\n
- \n Link codes\n
- \n Bibliography\n
\n
\n Notes\n

\nNotes about this preview edition

\n\n

\nUpdate: August 2022

\n\n

Hi, all! I bet you thought I forgot about this project. Far from it! I really miss working on this book. I have, though, been writing … about MakeCode Arcade, to boot!

\n\n

You can learn about a course that I wrote with another author at the MakeCode Arcade home page. Scroll down to the Courses section, and you’ll find a new course named Introduction to Computer Science with MakeCode Arcade. The curriculum is available for free on GitHub to verified educators.

\n\n

The pandemic interrupted my writing schedule, but I’m returning to my personal projects now that we have wrapped up the Microsoft project. This update includes the next chapter on variables and data types. I’ve also added the raw text for a couple of new appendices taken from posts that I’ve made in the MakeCode forums. The outline also reflects two new chapters on debugging.

\n\n

I recently started using the LaTeX typesetting system, and I have fallen in love with it. I will be taking another pause from adding new content to this book while I convert the existing text to LaTeX. As I do so, I’ll be writing about my journey and the tools that I use in another book. If you’re interested, you can follow my progress here:

\n\n

https://leanpub.com/latex-tech-pub

\n\n

That book will be available free of charge on Leanpub. The next preview of this book will be typeset with LaTeX, and the online course should be ready for you to preview, too.

\n\n

Stay tuned!

\n\n

This preview edition of Robo Teaches Programming will differ from the final version. Some things to note:

\n\n

I am using Leanpub to render the preview editions. Final versions will be translated into Bookdown and will use a Tufte-style layout. I also am considering transitioning to MarkDeep to save the translation steps later.
Leanpub does not like nested ordered (i.e., numbered) lists. Hopefully, Bookdown handles those better. :-) MarkDeep certainly does, and I may switch to that, even for rendering the preview editions.
Some images are merely placeholders and will be replaced with appropriately-licensed images. Those images are noted in the text.
Figures, tables, and exercises are mentioned with the generic “Figure/Table/Exercise A-B,” and the actual labels are not printed in the captions. Leanpub does not automate the numbering of figures, tables, and exercises. That will be handled during prepress or in my transition to MarkDeep.
In-text citations and their related references are formatted neither correctly nor consistently. That also will be handled during prepress.
Bibliography is in BibTeX syntax. Appropriate formatting will be handled during prepress.
Link code site has not yet been built. A list of link codes and their URLs is provided at the end of the book for the time being.

\n\n

As noted at the bottom of most pages, this preview copy is provided for your own, personal use. Do not distribute in whole or in part without express, written consent. © 2019-2023 Robo Technical Group, LLC. All rights reserved.

\n\n\n\n\n

\nPart zero: A history of video games

\n\n

\n\n\n

\nAbout the cover

\n\n

As with many families in the United States during the 1970s, my family’s first computer was the Atari Video Computer System (also known as the Atari VCS or, most commonly, the Atari 2600). My siblings and I spent many hours playing video games on that Atari 2600, usually connected to a black-and-white, nine-inch television in one of the bedrooms. Every once in a while, our parents would let us connect it to the large, color television in the living room.

\n\n

The cover image is a photograph of a portion of the circuit board of the Atari 2600 that I currently own. In the photograph, you can see the MOS Technology 6507 CPU.

\n\n

\"\" — Screen shot of *Moon Patrol* on the Atari 2600 (Temporary image from Atari Age)

\n\n\n\n\n\n\n

\nBrief contents

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nA history of video games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction to Part zero\n

\n\n

\nAbout the series

\n\n

Robo teaches programming is a six-part double-trilogy! We start slowly, introducing you to basic programming concepts with a focus on graphical applications. In the later parts of the series, we introduce you to some more advanced concepts that are fundamental to computer science.

\n\n

\nIntended audience

\n\n

The series is meant to be used in undergraduate college courses, although the books can be used in a high school setting or by anyone else with an interest in programming. Part zero is meant to be used in a CS0-style course; parts one and two for CS1; parts three and four for CS2.

\n\n

\nTitles in the series

\n\n

\nPart zero: A history of video games (“The red book.” That’s this book!)
\nPart zero mark II: Time to type! (“The orange book.”)
\nPart one: The basics (“The yellow book.”)
\nPart two: Beyond the basics and introduction to OOP (“The green book.”)
\nPart three: Advanced OOP (“The blue book.”)
\nPart four: Introduction to data structures and algorithms (“The purple book.”)

\n\n

\nAbout the book

\n\n

The full name of this book is Robo teaches programming part zero: A history of video games. That is a lot to say and a lot to type! So, for simplicity, I affectionately call this book “the red book.”

\n\n

In the red book, we start gently and get our feet wet early in a great environment: Microsoft MakeCode Arcade. We begin by exploring an existing game within the environment. By the end of the first chapter, you will have created your first masterpiece! We use the Blocks interface throughout this prelude, yet we learn to create some pretty sophisticated programs. Throughout the book, we also stroll through the history of video games to give our projects some additional context.

\n\n

\nHistory of video games

\n\n

We study and create a lot of video games in this book. We use the history of video games in this book to give some context to the skills that we build. In each chapter, we look at the story behind a video game or platform that is relevant to the skills presented. Those stories will be presented in “aside” boxes like this one.

\n\n

\nWhy video games?

\n\n

When I was learning to write computer programs, some of the first programs that I wrote were games. Even now, when I am learning a new programming language, I often use simple games to help me learn the language. I also use video games and board games as diversions. I play video games on a console, on a PC, and on mobile devices. I play board games, party games, and video games with friends and family. I also create games as a diversion. Writing these games helps to keep my programming skills sharp, and often I use them as a way to learn new skills. With creating games, I’ve learned the more obvious skills, like adding graphics to my programs and moving them around on the screen. I’ve also learned how to use databases and other data files when writing games, along with other skills that you may not associate with games.

\n\n

Since I started writing this book, I’ve written a lot more games! You’ll get to see some of them as we travel on this journey together.

\n\n

As a computer programmer, I am not alone in my love of games. But, why are many computer programmers fascinated with games? I’ve heard several explanations for this, but this quote from Hennessey and McGowan’s The comic book story of video games resonates the best with me, where they discuss that computer games have been around since the very beginning.

\n\n

The first slate of video games all came about as explorations into the capabilities of this unproved frontier…. One such game was draughts (“checkers” in North America), realized in 1951 in Manchester, England. The computer that ran draughts–the von Neumann architecture-based Ferranti Mark I had its programs coded on and loaded in via hole-punched paper tape…. The very existence of these games sort of goes against the grain of what computing was first supposed to be about…. Yet many programmers kept returning to making–and playing–games. Often anyone daring this felt themselves placed on the wrong side of a “cultural divide” in computing. But games proved to be elegant and useful metaphors for the very aspects of life that computing advocates wanted to influence.¹

\n\n\n

\n\n

\nPrior knowledge

\n\n

You do not need any prior knowledge of computer programming to learn from this book. In fact, if you have no prior knowledge of programming, then that is great! This book is designed for you!

\n\n

You do need to have some basic knowledge of how to use your computer. Specifically, you should know how to do the following things:

\n\n

You should understand how to right-click (also known as opposite-click) on an object with your mouse.
You should know how to drag and drop items.
You should understand the basic locations in your file system and the basic operations on files.\n
- You should know how to find the documents that you create, whether they are stored on your desktop, in a Documents folder, or elsewhere in your file system.
- You should know where downloaded files are stored on your computer.
- You should know how to copy files and how to move files on your computer.
\n
You should know the basics of browsing the Internet with your web browser.
You should know the purpose of basic components of a computer system, including hardware, software, RAM, and CPU.

\n\n

As long as you have those basic skills, you will get along just fine with this book!

\n\n

\nBook web site and link codes

\n\n

Throughout this book, I refer to link codes when referring to Internet resources. I have done this for simplicity. The codes are easier to type compared to lengthy URLs, and they can be updated in the event that a URL changes.

\n\n

You can use the codes in a few ways. The easiest way is to use the book’s website. Open the following URL in your favorite web browser:

\n\n

https://books.robotech.app

\n\n

Click on the book cover to get to the support page for this book. You can enter link codes on this page. Feel free to add this page to your web browser’s bookmarks or favorites.

\n\n

Another way to use the link codes is to add the link code to this book’s support URL. For example, to use the link code B-7, you could enter this URL in your favorite browser:

\n\n

https://books.robotech.app/part-zero/B-7

\n\n

The last way to use the link codes is to look them up in the master list of codes for this book. You can see all of the book’s codes and their URLs here:

\n\n

https://books.robotech.app/part-zero/list-all

\n\n

\n\n\n

\nHello, world! Introducing MakeCode Arcade

\n\n

We are about to embark on a journey through the history of video games. On this journey, you also will learn how to write computer programs! My name is Robo, and I will be your guide.

\n\n

In this first chapter, we will learn about the programming environment that we will use throughout this book. By the end of the chapter, you will create your very first masterpiece!

\n\n

If you have not already done so, be sure to flip back a few pages and read the introduction. There is some important information there about link codes and prior knowledge that you will need to know before beginning.

\n\n

\nLearning objectives

\n\n

By reading this chapter and completing its activities, you will master the content when you can do the following:

\n\n

List the system requirements for MakeCode Arcade.
View a project and its code in MakeCode Arcade.
Connect to the MakeCode Arcade environment.
Create a new project in MakeCode Arcade.
Save and load a MakeCode Arcade project.
Describe hardware that can be used with MakeCode Arcade.
Describe the history of MakeCode Arcade.

\n\n

\nAbout Microsoft MakeCode

\n\n

Microsoft describes its MakeCode product as “a free, open source platform for creating engaging computer science learning experiences that support a progression path into real-world programming.”¹ Microsoft has created several MakeCode products, including editors for the BBC micro:bit, Lego Mindstorms, and Mojang’s Minecraft. You can learn more about Microsoft MakeCode by using the link code A-MAKECODE.²

\n\n

\nAbout MakeCode Arcade

\n\n

In this book, we will use one of the MakeCode products: MakeCode Arcade. Microsoft describes MakeCode Arcade as “a code editor to build Retro Arcade games for the browser and handheld consoles.”³ MakeCode Arcade supports three programming languages: Blocks, JavaScript, and Python. In this book, we will use the Blocks language to learn about program logic. Program logic, or simply logic, is the thought process behind how a program works. We also will learn about program design, which is how a program is structured.

\n\n

The Blocks language is an appropriate metaphor for both logic and design. We often think of building programs as taking pieces of knowledge that we already know—the blocks—and putting them together in different ways to create different programs.

\n\n

\nSystem Requirements

\n\n

To create programs in MakeCode Arcade, you will need the following:

\n\n

A computer with a web browser\n
- MakeCode Arcade is a web-based application, so it can be used on tablets, laptops, and desktops. While MakeCode Arcade can run on smartphones, their limited screen size will make code editing difficult. Playing MakeCode Arcade games on smartphones, however, works really well!
- MakeCode Arcade can be used with any modern browser.
- MakeCode Arcade is frequently tested with Apple Safari, Google Chrome, Microsoft Edge, and Mozilla Firefox.
- MakeCode Arcade is tested with current versions of browsers, so be sure to keep your browser updated.
\n
A keyboard and a mouse\n
- While you can create programs in MakeCode Arcade with a touchscreen and the on-screen keyboard for your device, you will find a better experience when using a keyboard and a mouse.
\n
An Internet connection\n
- Because MakeCode Arcade is a web-based application, you will need an Internet connection to load the interface into your web browser.
- Once MakeCode Arcade is loaded into your web browser, though, an Internet connection is not required for its core functionality. Note that some functionality within MakeCode Arcade, like loading games from the gallery and interacting with GitHub, requires an Internet connection even after the environment has been loaded.
- Offline editors (i.e. editors that do not require an Internet connection) for MakeCode are available. Use link code M-OFFLINE to access the latest information on using MakeCode Arcade offline.
\n

\n\n

You can use the following hardware to enhance your experience when playing MakeCode Arcade games:

Game controllers\n
- MakeCode Arcade games can be written for up to four players. You can use the keyboard for up to two players, but for a better gameplay experience or to accommodate more than two players, you can use game controllers. Any game controller that is compatible with your computer should work in MakeCode Arcade: gamepads, joysticks, flight controllers, arcade controls, etc.
\n
Dedicated gameplay hardware\n
- Besides playing games in your web browser, you can load your games onto separate hardware. Some of these devices are portable, so you can take your games anywhere! More information on these devices appears later in this chapter, in the “Working with hardware” section.
\n

\n\n

\nView a MakeCode Arcade project

\n\n

We will begin our journey through the MakeCode Arcade interface by exploring a game. Use the following link code to launch a clone of Spacewar!

\n\n

M-SW

\n\n

A link like the one above is created in MakeCode Arcade to allow creators to share their games. When you open a link to a shared game, the game is loaded into your browser to allow you to play it. The interface looks like the screenshot in Figure A-B.

\n\n

\"\" — Playing *Spacewar!* via a shared link.

\n\n\n

The main elements in the interface are described below. We will explore each of these a little later in this chapter.

\n\n

\nSimulator. As mentioned earlier in this chapter, MakeCode Arcade games can be played on dedicated hardware. MakeCode Arcade includes a simulator that acts like that dedicated hardware. In the simulator, you can see the game as it would be displayed on hardware, and you can interact with the game using the same buttons that are available on hardware.
\nCode viewer. You can see the game’s code by clicking on Show Code. Here, you can inspect the code and see how the game’s author was able to build the various elements of the game. You can learn a lot just by reading code!
\nCode editor. You can load the game’s code into your own editor, too! When you click on Edit Code, you can alter the game any way you like, from changing the graphics to fixing bugs to adding new gameplay.

\n\n

\nStart your engines: Playing games in MakeCode Arcade

\n\n

The game loads in the simulator so that you can play it. Maximize your browser or, better yet, switch to fullscreen mode in your browser by pressing F11 on your keyboard. To exit fullscreen mode, press F11 again.

\n\n

This game has a splash screen that lists the game controls and the basic object of the game. In video games, a splash screen or attract screen runs while players are not interacting with the game. A splash screen can tell a story or provide information to the players before the game starts. For games that are displayed in an arcade, attract screens are used to draw players to the machine and play the game.

\n\n

\n
Lab A-B: Play SpaceWar!
\n\n
Play Spacewar! for a little bit. Feel free to ask a friend to play against you! After you have played Spacewar! for a little while to learn the in-game controls, we will learn more about the MakeCode Arcade interface.
\n\n

\nGame controls in MakeCode Arcade

\n\n

There are several ways to interact with your computer to play games that are made in MakeCode Arcade. You can use game controllers connected to your system if you have them. You do not need game controllers, though, for one- or two-player games in MakeCode Arcade.

\n\n

Player one can use the on-screen controls in the simulator to play a game. Player one also can use the keyboard. To use the on-screen controls, simply click (or tap if your system has a touchscreen) on the d-pad arrows or on the buttons to activate them. To use the keyboard, refer to Table A-B for the keys that you can use when playing a game.

\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Keyboard controls for player one.
Player 1	Option 1	Option 2
Up	W	Up arrow
Down	S	Down arrow
Left	A	Left arrow
Right	D	Right arrow
A	Q	Space
B	E	Enter

\n\n

Player two can use the keys listed in Table A-B.

\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n

Keyboard controls for player two.
Player 2	Key
Up	I
Down	K
Left	J
Right	L
A	U
B	O

\n\n

\nHistory of Spacewar!

\n\n

\n $\"\"$ \n

Spacewar! running on the Computer History Museum’s PDP-1.

\n \n

\n\n

“Spacewar!-PDP-1-20070512” by Joi Ito from Inbamura, Japan is licensed under CC BY 2.0.

\n\n

We will look at many games in this book. So, we will use the history of video games as a guide for our exploration. This history will provide some context to the games that we explore.

\n\n

Our first stop in our history lessons is Spacewar!, originally developed from 1961 to 1962 at the Massacusetts Institute of Technology (MIT) by Steve Russell, with contributions by Martin Graetz, Wayne Wiitanen, Bob Saunders, and Steve Piner. While other games like Bertie the Brain and OXO (tic-tac-toe games), simulations of draughts⁴ and chess, and Tennis for Two were created earlier, Spacewar! is arguably the first video game that was widely distributed.

\n\n

Originally written for the PDP-1 minicomputer by Digital Equipment Corporation (DEC), Spacewar! was ported⁵ to many other platforms. After Russell and his friends created the original version of Spacewar! for the PDP-1, the game was recreated on many other mainframe computers and minicomputers of the time. Spacewar! quickly found its way to microcomputers when they became popular in the 1970s. Spacewar! continues to be ported today to platforms like the Microsoft Xbox 360 and, now, Microsoft MakeCode Arcade!

\n\n

Spacewar! is so important in the history of video games that it was named among the top ten video games to be archived by the United States Library of Congress. In 2018, the Academy of Interactive Arts and Sciences awarded the Pioneer Award to the surviving contributors to Spacewar!

\n\n

Much more about Spacewar! is available on the Internet. You can read an article written by one of Spacewar!’s contributers, Martin Graetz, by using the link code A-SW.⁶ You can play an emulated version of the original game by using the link code G-SW.

\n\n

\nPeek beneath the hood: A look at the code

\n\n

After you have played Spacewar! for a little while to get accustomed to the in-game controls, let’s take a look at the code for this game. A game’s code are the instructions that your computer uses to run the game. A creator writes code to add images to a game, to respond to player actions, to change the score, to display the attract screen, and everything else that the game needs to do.

\n\n

Click the Show Code button at the top of the screen. Your screen should look similar to Figure A-B.

\n\n

\"\" — Viewing the code for *Spacewar!* in MakeCode Arcade.

\n\n\n

There is a lot of code in this game! Do not become intimidated by the code that you see. In time, and with some practice, you will be able to create programs that are just as complex … and even more so!

\n\n

Some of the things to investigate in the Show Code interface are described below:

\n\n

\nScroll bars. Use the scroll bars to move around the canvas.
\nCanvas. The canvas is where blocks are placed to write code for the game.
\nBlocks. Blocks are used to build the code for the game.

\n\n

\n
Lab A-B: Explore Spacewar! code
\n\n
Take some time to explore the code blocks that comprise this game. Look at the different shapes and colors of blocks, how the blocks are organized and arranged, and the words in the different blocks. Just by looking at the different blocks and by reading them, see if you can make some assumptions on what the different blocks do and how they affect the game.
\n\n
Feel free to go back and forth between playing the game in the Simulator interface and looking at the code in the Show Code interface. As you explore the code, take some screenshots and jot down some notes on different blocks. Perhaps you want to understand a particular block more. Perhaps you have an idea of what a certain block does and you want to remember it for later. Perhaps you want to test a hypothesis by changing some code and seeing its effects.
\n\n
You probably will have many questions, and that is OK! By the time you reach the end of this book, you will be able to revisit Spacewar! and understand all of the code blocks that you see.
\n\n

\nTime for a tune-up: Editing a game in MakeCode Arcade

\n\n

If you would like to tinker with the code, click the Edit Code button at the top of the interface. This opens the code in MakeCode Arcade so that you can edit it. Your screen will look similar to the screenshot in Figure A-B.

\n\n

\"\" — *Spacewar!* code open in the MakeCode Arcade editor.

\n\n\n

This is now your own copy of the code, and you can change it however you like. Refer to the notes that you made from the previous section, and investigate the blocks that looked interesting to you. As you go through this book, we will get to know all of the controls that you see in the editor interface. For now, though, just explore on your own.

\n\n

Consider following these steps when you change the code:

\n\n

\nMake note of the code’s current state before changing the code. Use a screenshot or jot down notes so that you can put the code back the way it was, particularly if you make an error.
\nMake note of the changes that you want to make. Jot down the changes that you plan to make to the code, why you want to change the code, and what you expect the changes to do.
\nMake the changes. Alter the code as you planned.
\nRun the game and observe the new behavior. Did the game change as you expected it to? How so, or how not?
\nReturn the code to its original state. If you wish, return the code to its previous state. You do not have to, of course, particularly if you want to see how multiple changes affect the game. It’s your code now! Have fun!

\n\n

\n
Lab A-B: Edit Spacewar! code
\n\n
Spend as much time as you like in the editor. If you make an error and need to open the original code, simply close MakeCode Arcade, and then use the link code M-SW to open a new copy of the game.
\n\n

\nStart MakeCode Arcade

\n\n

Now that you have played with someone else’s code, we will open the MakeCode Arcade environment without code so that you can explore more of the interface.

\n\n

You can open the MakeCode Arcade environment from the book’s web site. You also can use the link code M, or you can visit the following URL:

\n\n

https://arcade.makecode.com

\n\n

When you open the MakeCode Arcade environment without opening a shared game, you will see something similar to the screenshot in Figure A-B.

\n\n

\n\n\n

Some of the elements of the MakeCode Arcade home screen are described below:

\n\n

\nHome button. Just about anywhere within the MakeCode Arcade environment, you can click on the Home button to return to this home screen.
\nSettings cog. Click on the settings cog to adjust the settings of MakeCode Arcade. We will explore different settings as we need them.
\nMy Projects. As you create projects in MakeCode Arcade, they will appear in the My projects section. You may already have a project if you opened the Spacewar! game in the editor.
\nGallery. Below the My Projects section is the gallery. There are a lot of built-in projects here! You will get a chance to explore the gallery in just a moment.

\n\n

\nBuilt-in projects

\n\n

Take some time to explore the gallery on the MakeCode Arcade home screen. For now, do not open any of the projects in the sections called Tutorials, Multipart Tutorials, or Game Design Concepts. We will work with tutorials in the next chapter.

\n\n

There are many projects that you can explore. Some of the projects were created by the MakeCode Arcade team at Microsoft. Others were created by members of the MakeCode Arcade community. Click on any of the gallery images to get an explanation of the project and a link to the game. Some games will open directly in MakeCode Arcade. Others will take you to the MakeCode forums, which are described later in this chapter.

\n\n

\n
Lab A-B: Explore the MakeCode Arcade gallery
\n\n
Feel free to open any of the games in the gallery (again, except for the tutorials; we will come back to those). As with Spacewar!, once you have opened a game in the editor, feel free to alter any of the code to see what the changes will do. As before, you may not understand all of the code that you see, and that is OK. Some of the games in the gallery are very complex! Take your time and enjoy the exploration.
\n\n

\nYour first MakeCode Arcade project

\n\n

Now that you have spent some time looking at code from other creators, it is time to create your own project. You will create a simple game with two images. The player will be able to move one of the images with the player controls.

\n\n

Return to the MakeCode Arcade home screen by clicking on the Home button. If you no longer have the MakeCode Arcade editor open, simply visit the MakeCode Arcade home screen by any of the methods listed earlier in this chapter.

\n\n

\nCreating a new project in MakeCode Arcade

\n\n

\n
Lab A-B: Create a new project
\n\n
From the MakeCode Arcade home screen, create a new project.
\n\n
\n
\n $\"\"$ \n
Creating a new project in MakeCode Arcade.
\n
\n
\n\n\n
1. In the My Projects section of the home screen, click on the New Project button.
2. When prompted, give your project a name.
3. Click on the Create button.
4. The MakeCode Arcade editor opens with a blank canvas.
\n\n

\nExploring the MakeCode Arcade editor

\n\n

Figure A-B is a screenshot of the MakeCode Arcade editor with a blank canvas (i.e. a blank or empty project). In this section, we will explore some of the components of the interface in more detail.

\n\n

\"\" — MakeCode Arcade code editor with a blank canvas.

\n\n\n

\nHome button. The Home button will return you to MakeCode Arcade’s home screen.
\nSettings cog. Use the settings cog to adjust different settings in MakeCode Arcade. You also can use the settings cog to print your project and to delete the current project.
\nSimulator. The simulator plays the current game. You learned how to play games in the simulator earlier in this chapter. When editing a project, there are additional controls beneath the simulator. We will learn to use those controls in later chapters.
\nToolbox drawers. There are many blocks in the MakeCode Arcade environment. The blocks are stored in different drawers in the toolbox. Click on a drawer to open the toolbox and see the blocks in that drawer.
\nProject name. You can change the name of your project with this text box.
\nSave button. You can save a copy of your code as a cartridge with the save button. You will learn more about cartridges later in this chapter.
\nDownload button. MakeCode Arcade can send your code to a hardware device with the Download button. You will learn more about hardware for MakeCode Arcade later in this chapter. Follow your hardware’s instructions on how to download code to the device.
\nCanvas. The canvas contains the code for your project. You add blocks to the canvas, and you can drag blocks around the canvas to organize them. The canvas grows automatically as you need more room for your code.
\nLanguage buttons. You can use the language buttons to show your code in different programming languages. We will use the Blocks language in this book. You can learn about other programming languages in other books in this series.

\n\n

\nPlanning the first project

\n\n

Staring at a blank canvas can be intimidating. Where do we begin? For all projects, the best thing to do is to create a plan before writing any code. We will do that now for our first project.

\n\n

For many projects, we can create a plan by considering the following parts:

\n\n

\nProject name. A descriptive name for the project.
\nProject description. The project description provides an overview of the project.
\nHousekeeping. Housekeeping items are things that we need to create before the game begins, like the player’s image, a timer, and the game score.
\nEvents. Events are things that happen in your game as a result of other actions, such as player input or when a player earns a certain score.

\n\n

We will explore these parts of the project plan in more detail in other projects. We also will expand this project plan as our projects get more complex. In future projects, we will create the plan together. However, for this first project, I will provide you with the plan that we will follow.

\n\n\n\n

\nAdding the first block

\n\n

In this book, we will be using blocks to create our programs. After finishing this book, you can learn how to use other languages in MakeCode Arcade.

\n\n

Let’s add a block to the project. We know we need to add an image that the player can control. For this, we will add a sprite. A sprite is an image with some additional properties that can be manipulated during the game. For now, you will learn just a little bit about how sprites work. You will learn more about sprites in the next chapter.

\n\n

\n
Lab A-B: Add your first block to your new project
\n\n
Follow these steps to add your first sprite to your project:
\n\n
\n
\n $\"\"$ \n
Adding the first sprite to your blank project.
\n
\n
\n\n\n
1. Click on the Sprites drawer. The sprites toolbox opens.
2. Click on the set sprite block in the toolbox. A copy of the block appears on your canvas.
\n\n

Great! We have added our first block to our project. Something looks wrong, though, doesn’t it? The new block seems to be crossed out:

\n\n

\n\n\n

\nBlock types

\n\n

MakeCode Arcade uses several types of blocks. The set sprite block that you just placed on the canvas is called a single block. Single blocks cannot live independently on the canvas. Instead, single blocks must live inside of another type of block, called container blocks. Certain container blocks, called event blocks, can be placed anywhere on the canvas. You will learn more about these types of blocks as you progress through the book.

\n\n

\nThe on start block

\n\n

For now, though, we are going to use an event block that is used in most games: the on start block. The on start block is the first block that runs at the beginning of your program. MakeCode Arcade games can only contain one on start block, and this often is where we place housekeeping items before gameplay begins.

\n\n

According to our project plan for this first project, we will need to add a couple of sprites to our game, and we need to configure one of the sprites to respond to the player’s inputs. We will add these items to the on start block of our program.

\n\n

\n
Lab A-B: Adding first block to on start
\n\n
The on start block is automatically added to your project when MakeCode Arcade creates it. Simply drag your set sprite block into the on start block so that it runs at the beginning of your game. When you drag the block into the on start block, notice that it is not longer disabled.
\n\n
\n
\n $\"\"$ \n
Adding the set sprite block to on start.
\n
\n
\n\n\n
Look at the shape of the on start block. Notice the differences between it and the set sprite block? Because of its shape, you can tell that the on start block is a container block, and you can place other blocks inside of it. Also, the on start block is an event block. You cannot tell that by its shape; you simply learn which blocks are event blocks and which ones are not. In case you forget, there is an easy way to tell which blocks are event blocks. You already have used this technique. Simply drop the block onto the canvas. If the block is disabled when you place it by itself on the canvas, then it is not an event block.
\n\n

\nRenaming a variable

\n\n

Read the set sprite block. It contains the following code:

\n\n\n

1 set mysprite to sprite ' ' of kind Player\n

\n\n\n\n\n

The default name for your sprite is mysprite. That does not sound very descriptive, does it? If you place another set sprite block in your program, can you guess what its name will be?

\n\n

By adding the set sprite block to your program, you have created a variable. A variable is a place in the computer’s memory which is given a name. We can store information in variables; in this case, we are storing a sprite. When we write programs, we often create many variables. To help us keep better track of our variables, we assign them meaningful names. The name mysprite is not very meaningful, so let’s rename our variable to give it more meaning.

\n\n

\n
Lab A-B: Rename the first sprite
This first sprite will be the one that is controlled by the player. With that in mind, what name do you want to give it?
\n\n
\n
\n $\"\"$ \n
Renaming a variable.
\n
\n
\n\n\n
1. Click the down arrow next to the variable name, mysprite. A menu appears.
2. Look past the list of variable names that already exist in your project. Near the bottom of the menu, click Rename variable…. A dialog box appears.
3. Enter your new variable name, and then click OK.
\n\n

\nAutosave in MakeCode

\n\n

Now is a good time to take a break from our first project. You have learned a lot already!

\n\n

MakeCode automatically saves your work. We can see that now: Click on the Home icon to return to the home screen, and you can see your new project in the My Projects space.

\n\n

On the home screen, click on your new project, and you are returned to the editor. This time, though, instead of a blank canvas, you are returned right where you left off with your new project. No manual saving necessary!

\n\n

MakeCode stores your projects in your browser’s data store. The data store a location on your hard drive where web applications can keep data. Because this information is kept in your browser, you will lose your projects (and any other data that MakeCode stores) if you clear your browser’s data store. Also, if you use a different browser or a different computer, you will not see your projects.

\n\n

Later in this chapter, in the section called “Working with projects,” we will learn another way to store your projects.

\n\n

\nAdding another sprite

\n\n

\n
Lab A-B: Add the second sprite to your project
\n\n
Open your project again in the MakeCode Arcade editor. Let’s add a second sprite.
\n\n
\n
\n $\"\"$ \n
Adding a second sprite to your project.
\n
\n
\n\n\n
1. Click on the Sprites drawer. The sprites toolbox opens.
2. Click on the set sprite block in the toolbox. As before, a copy of the block appears on your canvas.
3. Drag the block into the on start block.
4. Rename the variable to give it a meaningful name.
\n\n

\nUsing images from the gallery

\n\n

Take a look at our game in the simulator. If the simulator is not already running, then click on the Play button. We can see from the code that we have added two sprites to our game, but in the simulator, it looks like nothing is happening.

\n\n

When we created our two sprites, we did not change the default image. A default is a value that is set automatically. For sprites, the default image is blank or empty. Let’s change that now by using the image gallery.

\n\n

\n
Lab A-B: Add images from the image gallery
\n\n
\n
\n $\"\"$ \n
Using the image gallery for sprites.
\n
\n
\n\n\n
1. Click on the image box for the player’s sprite. The image editor opens.
2. Click on Gallery.
3. Select an image. It is loaded into the image editor
4. Click on Done in the bottom right corner.
\n\n
After you set the image for the player’s sprite, the simulator restarts, and your new sprite should appear in the simulator.
\n\n
Do the same for the second sprite. After you set the image for the second sprite, the simulator will restart again. Now, you should see both sprites in the simulator, and they should overlap.
\n\n

\nAttaching controls to a sprite

\n\n

To finish our first project, we need to add the ability for the player to control one of the sprites. MakeCode Arcade makes that easy! Follow these steps:

\n\n

\n
Lab A-B: Add controls to the player sprite
\n\n
\n
\n $\"\"$ \n
Adding player controls to a sprite.
\n
\n
\n\n\n
\n
\n $\"\"$ \n
Final code for our first project.
\n
\n
\n\n\n
1. Click on the Controller drawer.
2. Click on the move sprite with buttons block in the toolbox.
3. Drag the new block to the bottom on the on start block.
4. In the move sprite with buttons block, set the sprite variable to the one that you want the player to control.
\n\n
Allow the simulator to restart (press the play button if the simulator is paused). Now, you can control one of the sprites with the arrow keys!
\n\n
Great work! You have created your first project!
\n\n

\nWorking with projects

\n\n

\nSaving your project as a cartridge

\n\n

As mentioned earlier, MakeCode Arcade saves your work automatically to your browser’s data store. This is a useful feature of MakeCode Arcade, but it can fail. Because MakeCode depends on your browser’s data store, all of your work can quickly be erased by clearing your browser’s data store. So, do not think of this as a permanent storage space for your projects. You should get in the habit of saving your work elsewhere.

\n\n

You can save a copy of your project anytime it is open in the editor. MakeCode Arcade can save your project as a cartridge. In MakeCode Arcade, a cartridge is a special image file with your code stored inside of it. MakeCode Arcade saves cartridges as PNG files.

\n\n

\n
Lab A-B: Create a cartridge
\n\n
\n
\n $\"\"$ \n
Creating a cartridge in MakeCode Arcade.
\n
\n
\n\n\n
Follow these steps to create a cartridge of your first project:
\n\n
1. Open your project in the editor.
2. Near the bottom of the screen where your project name is displayed, click on the Save icon.
3. Your browser will download the cartridge and store it in your Downloads folder.
4. Move the cartridge file to an appropriate location in your file system.
\n\n

Keep in mind that this cartridge is a copy of your current code. If you go back into the editor and change any of your code for this project, then your changes will not be reflected in the cartridge. This is a good way to keep previous versions of your projects. Before you make any major changes to a project, save a copy of it. If you make a major error, you can always load the old copy of your code.

\n\n

\nLoading a cartridge

\n\n

\n
Lab A-B: Load a cartridge into MakeCode Arcade
\n\n
Let’s load this cartridge that you just created into MakeCode Arcade.
\n\n
1. Return to MakeCode Arcade’s home screen by clicking on the Home button.
2. Drag your cartridge file into your browser.
\n
1) First, MakeCode Arcade creates a new project in your browser’s data store.
1) Then, it copies the code in your cartridge into the new project.
1) Then, it opens the new project in the editor.
1. Play your new copy of your project for a few moments to make sure it works correctly.
\n\n

Return to the home screen. Notice that you now have two copies of your project in the My Projects area. We do not need this extra copy, so let’s delete one of them.

\n\n

\nDeleting a project

\n\n

Deleting a project removes it from your browser’s data store. Remember that, for this first project, we already have created a cartridge of it. We can safely delete the project from our browser’s data store because we have a copy of it saved on our hard drive.

\n\n

\n
Lab A-B: Delete a project from MakeCode Arcade
\n\n
\n
\n $\"\"$ \n
Deleting a project from MakeCode Arcade.
\n
\n
\n\n\n
Follow these steps to delete a project from MakeCode Arcade:
\n\n
1. From the home screen, click View All next to the My Projects label.
2. Click on the project that you wish to delete. Notice the green check mark to indicate that the project is selected.
3. Click Delete.
4. Confirm that you wish to delete the project by clicking Delete in the dialog box.
\n\n

Notice that MakeCode Arcade warns you before it deletes a project. Deleting a project from your browser’s data store is a permanent action; there is no undo. Be sure you save a project as a cartridge before you delete it from MakeCode Arcade.

\n\n

\nWorking with hardware

\n\n

To work with projects in MakeCode Arcade, all you need is a system with a modern web browser. MakeCode Arcade includes a simulator that will run your projects, and you can play games that others create in the simulator.

\n\n

However, you also can play games on separate hardware that is specifically designed or configured for MakeCode Arcade. Several manufacturers have created boards that work with MakeCode Arcade, including the BrainPad Arcade and the Adafruit PyGamer. Other general-purpose hardware, like the Raspberry Pi and the Adafruit M4, can be configured to run MakeCode Arcade games. You can even build a full-sized, upright arcade cabinet for your MakeCode Arcade games! For more information on hardware that supports MakeCode Arcade, use the link code M-HW.

\n\n\n\n

There are several ways to share your projects with others. You already have learned to create a cartridge for your game. You can share that file with others, and they can load your cartridge into MakeCode Arcade. Another way to share a project is to send a copy to the MakeCode servers to get a custom URL.

\n\n\n

Now that you have a URL for your project, you can share it however you like. You could post the URL to your blog. You can e-mail the link to friends. You can share the link over social media. You can include the link in a digital portfolio. You also can share the link on the MakeCode forums.

\n\n

\nMakeCode forums

\n\n

The MakeCode team has created a Discourse forum for the MakeCode community. Use the link code M-FORUM to visit the MakeCode forum, or visit the following URL:

\n\n

https://forum.makecode.com

\n\n

In the MakeCode forums, you will find information on the live streams that the MakeCode Arcade team conducts. You also will find games and other projects that creators have shared. Many members of the MakeCode Arcade team participate in the forum, answering questions and sharing updates. You will often find me participating at the forum, too!

\n\n

The forum is available to the public, but you will need to create an account in order to participate. If you wish to participate in the forum, it is probably best to create a GitHub account. GitHub is a widely-used service to host code, and you can use GitHub with MakeCode Arcade. We will discuss using GitHub in the Part zero mark II book.

\n\n

Feel free to share your creations with the world through the MakeCode Arcade forum. Be sure to say “Hi!”

\n\n

\nHistory of MakeCode Arcade

\n\n

MakeCode Arcade’s immediate predecessor was TouchDevelop. TouchDevelop allowed creators to build programs using a Windows Phone. It later expanded to a web interface and allowed for input with a keyboard and mouse. Like MakeCode’s Blocks language, TouchDevelop used interlocking blocks to create programs.

\n\n

TouchDevelop was retired in June 2019. Several of the team members behind TouchDevelop are also members of the MakeCode team.

\n\n\n

\nHello, it’s me! (Or is it I?)—Sprites and your hero character

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLearning objectives

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional controls in the MakeCode editor

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDeleting blocks

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nUndo and redo

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nZooming in and out

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWorking with tutorials

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMoving around

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nThe hero character and sprite

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPlayer sprite velocity

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nConstraining sprite movement

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nUsing the image editor

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nScreen coordinates

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nExploring the screen coordinates

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprite coordinates

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPlacing your character

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnimating your character

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nInstalling extensions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCreating a walking animation

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCreating a spinning wheel

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMore complex animations

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMaking a background

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBackground with a solid color

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBackground image

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnimated backgrounds

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nArtwork and prototypes

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional practice with the image editor

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnswers to review questions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhich way did it go? Decisions, conditionals, and basic game physics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLearning objectives

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSoftware development life cycle

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep one: Gathering requirements

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep two: Project analysis

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep three: Project design

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep four: Coding

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep five: Testing

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep six: Operations

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStep seven: Project archiving

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOther software development life cycles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPlanning a project

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nProject documentation

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAlgorithms and structured programming

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFlowcharts

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNassi-Shneiderman diagrams

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPseudocode

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPrincess Pizza\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDocumentation in Blocks programs

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBouncing Burger\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nEvent-driven programming

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprite types

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPong\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPong simplified

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVelocity

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdding sound effects

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDetermining the game’s end

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nThe `on game update` block

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBoolean expressions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCorrecting an error

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAcceleration

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDecision structures

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional tutorials

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnswers to exercises

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhat’s the score? Variables and data types

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLearning objectives

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhich button?

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPong part 2: Complete one-player game

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPong part 3: Complete two-player game

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction to variables

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCreating variables

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNaming conventions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nConstants and literals

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVariable scope

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nGlobal scope

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLocal scope

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nData types in Blocks

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNumber

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nString

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprite and image

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBoolean

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nGuess My Number\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAcey Deucey\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction to the Playing Cards extension

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnswers to exercises

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nZap! Debugging part 1

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPlaying the role of the computer

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nUsing messages for debugging

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nI’ve made some enemies—Introduction to object-oriented programming

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVisual effects

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprite effects

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nScene effects

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDebugging part 2

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOver … and over … and over again—Loops

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWho’s above me? Who’s next to me? Arrays and lists

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBetter than right-click-duplicate—Functions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNaming convention

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLocal variables revisited

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun name :-) - Strings

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWriting text on the screen

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun name :-) - Tile maps and platformers

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTile maps

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPlatformers

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMazes?

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhat’s your name again? Persisting data

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSession object

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStranger, danger! Security and privacy

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIt’s alive! Artificial intelligence

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun name :-) - Searching and sorting

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhere to now?

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional books in the series

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLearn other languages and programming environments

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOther games to try to build in MakeCode Arcade

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOther programming books

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMore on the history of video games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - A Blocks style guide

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nProject description

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVariable and function naming

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFunction description

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Common game structures

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nShoe of cards

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDice

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Stopwatch in Blocks

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPart I: Basic stopwatch

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFinished code

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDeveloping the project plan

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBuilding the project

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNext steps

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPart II: Advanced stopwatch

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFinished code

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdding to the project plan

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIncorporate changes into code

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNext steps

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Common game mechanics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nShuffling

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Advanced graphics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nParallax (sprites with depth)

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Multiplayer games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Vector math

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nRevisiting velocity

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVelocity vectors

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAngles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMeasuring angles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nReview of right triangles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTrigonomotric functions and right triangles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPractice with velocity vectors

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nRepresenting π

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprite travelling in a random direction

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAnother challenge

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFinal challenge

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - A template for Blocks games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSplash screen

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTitles

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nHeadlines

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nInstruction lists

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdding images to the splash screen

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAttract mode

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nButton handlers

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Additional Blocks games (showcase)

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional clones

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCredits and licenses

\n\n

Screenshots of Microsoft MakeCode Arcade include content owned by Microsoft Corporation. Used with permission from Mirosoft.

\n\n

“Signed Pong Cabinet” by Chris Rand is licensed under CC BY-SA 3.0.

\n\n

“Spacewar!-PDP-1-20070512” by Joi Ito from Inbamura, Japan is licensed under CC BY 2.0.

\n\n

“Tennis for Two in 1959” by Brookhaven National Laboratory is released to the public domain.

\n\n

“Magnavox Odyssey Console Set” by Evan-Amos is released to the public domain.

\n\n

“TeleGames-Atari-Pong” by Evan-Amos is licensed under CC BY-SA 3.0.

\n\n\n

\nPart zero mark II: Time to type!

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAbout the cover

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBrief contents

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction to Part zero mark II\n

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAbout the series

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntended audience

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTitles in the series

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAbout the book

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPrior knowledge

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBook web site and link codes

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nHello, World! I’m typing! Introducing JavaScript

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTransitioning from Blocks to JavaScript

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nToolbox

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntelliSense

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTooltips

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nStyle guide

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTo grandmother’s house—Revisiting topics from a JavaScript perspective

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSDLC and documentation

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSprites

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nVariables and scope

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFunctions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nReturn of the Jedi—Object-oriented programming basics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\n‘Round and ‘round we go—Loops and arrays

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nHold this, will ya? Working with GitHub

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction to agile methods

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nPublishing with GitHub

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOur first game—Card game?

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOur second game—Tabletop board game

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOur third game—Return to arcade games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOur fourth game—Another arcade game

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun title :-) - Advanced graphics and physics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nParallax (Revisit of Part zero appendix)

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDrawing directly to the screen

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nHUD

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nSimulating three dimensions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun title :-) - Searching and sorting

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFun title :-) - Introduction to data structures and algorithms

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWhere to now?

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdditional books in the series

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nLearn other languages and programming environments

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOther games to try to build in MakeCode Arcade

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nOther programming books

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nMore on the history of video games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - A TypeScript style guide

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Common game structures

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nShoe of cards

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nDice

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Stopwatch in TypeScript

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nIntroduction

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTypeScript

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nFinished code

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nWorking with the Text Sprite in TypeScript

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nObject-oriented design

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCreating the Stopwatch class

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAdding functionality to the Stopwatch class

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nExtras

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Common game mechanics

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nShuffling

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Lambda and anonymous functions

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Filtering and iterating with method calls

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - A template for JavaScript Games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAppendix - Additional JavaScript games (showcase)

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nCredits and licenses

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBonus chapter: Can I be a computer scientist?

\n\n

A question that I get asked frequently is, “What do I need to know to be a computer programmer?” Or, more simply, “Can I become a computer scientist?” Here are my answers to these and related questions, based on my own experience as a computer scientist as well as working with others in this profession.

\n\n

\nCan I be a computer scientist?

\n\n

Of course! Just like anything else, some people will find it a little easier than other people. However, if you find it interesting, and you are willing to work hard at your skill, you absolutely can be a computer programmer.

\n\n

If you find computer programming interesting, please pursue computer science as a profession. The world is in desperate need of high-quality programmers.

\n\n

\nDo I need to be good at math?

\n\n

Yes … sorta. When I get asked this question, it usually translates to “Do I need to do well in math classes?” You can be good at math and be terrible in math classes … and that usually is because you have had teachers that do not share their knowledge in a way that translates well to you. Nearly everyone can learn math, and nearly everyone has an intrinsic understanding of the basics of mathematics. We all learned how to count, and we all learned how to add, at very young ages, often before entering school. Math is built into almost all of us. Some of us are just able to tap into that basic understanding a little bit better than others.

\n\n

To be a good computer scientist, you do need to be good at math … in that you need to be good at some fundamental skills in math:

\n\n

You need to be good at solving problems. (No, I don’t mean “word problems” or “story problems.”)
You need to be able to recognize patterns.

\n\n

You do not need to be an “A” student in your math classes, though.

\n\n

\nI really like computers, but I don’t really like programming. Are there other things that I can do?

\n\n

Absolutely! Computing is a large profession; not everyone involved in the profession is a computer scientist. The profession needs people to do many different things!

\n\n

If you like computers, but programming doesn’t seem like your cup of tea, then perhaps information technology is more your speed. IT includes areas like network administration and systems administration (i.e. working with “servers”). Or, if you are more artistic-minded, then you might be interested in computer-aided design (e.g. architecture, 3-D modeling, graphics design). If you like building things, then automation (e.g. robotics) may be of interest. If you like numbers, then you may be interested in becoming a data scientist.

\n\n

Most importantly, find something that is interesting to you. The more interesting something is to you, the more you will be willing to work hard at it, and the better you will get at your craft.

\n\n\n

\nGlossary

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nTimeline of video games

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nAcknowledgements

\n\n

Thanks to MakeCode Arcade forum user rymc88 for the inspiration behind some of the content in the Part zero appendix on vector math.

\n\n\n\n

\nAbout the author

\n\n

Alex Kulcsar (“Robo” in his college days) is chair of the computer science programs at American Business & Technology University. He is also CEO and CTO of Robo Technical Group. He holds a bachelor’s degree in mathematics from the University of Michigan and a master’s degree in computer science from American Sentinel University.

\n\n\n

\nColophon

\n\n

The preview versions of this book are created in Leanpub with Visual Studio Code. The final print and electronic versions are produced by IngramSpark.

\n\n

Screenshots were taken in Microsoft Edge.

\n\n\n

\nLink codes

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nBibliography

\n\n\n

This content is not available in the sample book. The book can be purchased on Leanpub at http://leanpub.com/makecode-book.

\n\n\n

\nNotes

Part zero: A history of video games

Introduction to Part zero\n

Hello, world! Introducing MakeCode Arcade

\n\n

\n\n","tocStructure",[843,844,845,846,847,848,849,850,851,852,853,854,855,856,857,858,859,860,861,862,863,864,865,866,867,868,869,870,871,872,873,874,875,876,877,878,879,880,881,882,883,884,885,886,887,888,889,890,891,892,893,894,895,896,897,898,899,900,901,902,903,904,905,906,907,908,909,910,911,912,913,914,915,916,917,918,919,920,921,922,923,924,925,926,927,928,929,930,931,932,933,934,935,936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953,954,955,956,957,958,959,960,961,962,963,964,965,966,967,968,969,970,971,972,973,974,975,976,977,978,979,980,981,982,983,984,985,986,987,988,989,990,991,992,993,994,995,996,997,998,999,1000,1001,1002,1003,1004,1005,1006,1007,1008,1009,1010,1011,1012,1013,1014,1015,1016,1017,1018,1019,1020,1021,1022,1023,1024,1025,1026,1027,1028,1029,1030,1031,1032,1033,1034,1035,1036,1037,1038,1039,1040,1041,1042,1043,1044,1045,1046,1047,1048,1049,1050,1051,1052,1053,1054,1055,1056],{"_79":73,"_43":70,"_71":-5,"_74":75,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":70,"_71":-5,"_74":75,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":73,"_43":85,"_71":-5,"_74":86,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":89,"_71":-5,"_74":90,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":93,"_71":-5,"_74":94,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":98,"_71":-5,"_74":99,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":103,"_71":-5,"_74":104,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":107,"_71":-5,"_74":108,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":110,"_71":-5,"_74":111,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":113,"_71":-5,"_74":114,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":116,"_71":-5,"_74":117,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":119,"_71":-5,"_74":120,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":122,"_71":-5,"_74":123,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":125,"_71":-5,"_74":126,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":129,"_71":-5,"_74":130,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":132,"_71":-5,"_74":133,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":135,"_71":-5,"_74":136,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":138,"_71":-5,"_74":139,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":141,"_71":-5,"_74":142,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":144,"_71":-5,"_74":145,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":147,"_71":-5,"_74":148,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":150,"_71":-5,"_74":151,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":153,"_71":-5,"_74":154,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":156,"_71":-5,"_74":157,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":129,"_71":-5,"_74":160,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":162,"_71":-5,"_74":163,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":165,"_71":-5,"_74":166,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":168,"_71":-5,"_74":169,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":171,"_71":-5,"_74":172,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":174,"_71":-5,"_74":175,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":177,"_71":-5,"_74":178,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":180,"_71":-5,"_74":181,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":183,"_71":-5,"_74":184,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":186,"_71":-5,"_74":187,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":189,"_71":-5,"_74":190,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":192,"_71":-5,"_74":193,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":195,"_71":-5,"_74":196,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":198,"_71":-5,"_74":199,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":201,"_71":-5,"_74":202,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":204,"_71":-5,"_74":205,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":207,"_71":-5,"_74":208,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":210,"_71":-5,"_74":211,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":129,"_71":-5,"_74":214,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":216,"_71":-5,"_74":217,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":219,"_71":-5,"_74":220,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":222,"_71":-5,"_74":223,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":225,"_71":-5,"_74":226,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":228,"_71":-5,"_74":229,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":231,"_71":-5,"_74":232,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":234,"_71":-5,"_74":235,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":237,"_71":-5,"_74":238,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":240,"_71":-5,"_74":241,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":243,"_71":-5,"_74":244,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":246,"_71":-5,"_74":247,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":249,"_71":-5,"_74":250,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":252,"_71":-5,"_74":253,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":255,"_71":-5,"_74":256,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":258,"_71":-5,"_74":259,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":261,"_71":-5,"_74":262,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":264,"_71":-5,"_74":265,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":267,"_71":-5,"_74":268,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":270,"_71":-5,"_74":271,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":273,"_71":-5,"_74":274,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":129,"_71":-5,"_74":277,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":279,"_71":-5,"_74":280,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":282,"_71":-5,"_74":283,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":285,"_71":-5,"_74":286,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":288,"_71":-5,"_74":289,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":291,"_71":-5,"_74":292,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":294,"_71":-5,"_74":295,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":297,"_71":-5,"_74":298,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":300,"_71":-5,"_74":301,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":303,"_71":-5,"_74":304,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":306,"_71":-5,"_74":307,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":270,"_71":-5,"_74":309,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":311,"_71":-5,"_74":312,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":315,"_71":-5,"_74":316,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":318,"_71":-5,"_74":319,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":321,"_71":-5,"_74":322,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":325,"_71":-5,"_74":326,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":328,"_71":-5,"_74":329,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":332,"_71":-5,"_74":333,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":336,"_71":-5,"_74":337,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":340,"_71":-5,"_74":341,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":344,"_71":-5,"_74":345,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":347,"_71":-5,"_74":348,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":350,"_71":-5,"_74":351,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":354,"_71":-5,"_74":355,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":357,"_71":-5,"_74":358,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":361,"_71":-5,"_74":362,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":364,"_71":-5,"_74":365,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":367,"_71":-5,"_74":368,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":370,"_71":-5,"_74":371,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":374,"_71":-5,"_74":375,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":377,"_71":-5,"_74":378,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":381,"_71":-5,"_74":382,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":385,"_71":-5,"_74":386,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":389,"_71":-5,"_74":390,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":393,"_71":-5,"_74":394,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":396,"_71":-5,"_74":397,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":399,"_71":-5,"_74":400,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":402,"_71":-5,"_74":403,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":405,"_71":-5,"_74":406,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":408,"_71":-5,"_74":409,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":412,"_71":-5,"_74":413,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":415,"_71":-5,"_74":416,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":418,"_71":-5,"_74":419,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":421,"_71":-5,"_74":422,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":425,"_71":-5,"_74":426,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":428,"_71":-5,"_74":429,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":431,"_71":-5,"_74":432,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":435,"_71":-5,"_74":436,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":438,"_71":-5,"_74":439,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":441,"_71":-5,"_74":442,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":444,"_71":-5,"_74":445,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":447,"_71":-5,"_74":448,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":450,"_71":-5,"_74":451,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":438,"_71":-5,"_74":453,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":455,"_71":-5,"_74":456,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":458,"_71":-5,"_74":459,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":447,"_71":-5,"_74":461,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":463,"_71":-5,"_74":464,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":467,"_71":-5,"_74":468,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":470,"_71":-5,"_74":471,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":474,"_71":-5,"_74":475,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":477,"_71":-5,"_74":478,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":481,"_71":-5,"_74":482,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":485,"_71":-5,"_74":486,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":488,"_71":-5,"_74":489,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":491,"_71":-5,"_74":492,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":494,"_71":-5,"_74":495,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":497,"_71":-5,"_74":498,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":500,"_71":-5,"_74":501,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":503,"_71":-5,"_74":504,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":506,"_71":-5,"_74":507,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":509,"_71":-5,"_74":510,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":512,"_71":-5,"_74":513,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":515,"_71":-5,"_74":516,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":519,"_71":-5,"_74":520,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":522,"_71":-5,"_74":523,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":525,"_71":-5,"_74":526,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":528,"_71":-5,"_74":529,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":532,"_71":-5,"_74":533,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":535,"_71":-5,"_74":536,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":73,"_43":539,"_71":-5,"_74":540,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":89,"_71":-5,"_74":543,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":93,"_71":-5,"_74":546,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":549,"_71":-5,"_74":550,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":107,"_71":-5,"_74":553,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":110,"_71":-5,"_74":555,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":113,"_71":-5,"_74":557,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":116,"_71":-5,"_74":559,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":119,"_71":-5,"_74":561,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":122,"_71":-5,"_74":563,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":565,"_71":-5,"_74":566,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":569,"_71":-5,"_74":570,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":572,"_71":-5,"_74":573,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":575,"_71":-5,"_74":576,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":579,"_71":-5,"_74":580,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":582,"_71":-5,"_74":583,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":585,"_71":-5,"_74":586,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":588,"_71":-5,"_74":589,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":591,"_71":-5,"_74":592,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":595,"_71":-5,"_74":596,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":599,"_71":-5,"_74":600,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":603,"_71":-5,"_74":604,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":606,"_71":-5,"_74":607,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":609,"_71":-5,"_74":610,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":613,"_71":-5,"_74":614,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":617,"_71":-5,"_74":618,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":621,"_71":-5,"_74":622,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":625,"_71":-5,"_74":626,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":629,"_71":-5,"_74":630,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":632,"_71":-5,"_74":633,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":635,"_71":-5,"_74":636,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":638,"_71":-5,"_74":639,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":642,"_71":-5,"_74":643,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":389,"_71":-5,"_74":646,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":393,"_71":-5,"_74":649,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":396,"_71":-5,"_74":651,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":399,"_71":-5,"_74":653,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":402,"_71":-5,"_74":655,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":405,"_71":-5,"_74":657,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":659,"_71":-5,"_74":660,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":421,"_71":-5,"_74":663,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":425,"_71":-5,"_74":666,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":428,"_71":-5,"_74":668,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":670,"_71":-5,"_74":671,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":674,"_71":-5,"_74":675,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":438,"_71":-5,"_74":677,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":679,"_71":-5,"_74":680,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":682,"_71":-5,"_74":683,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":685,"_71":-5,"_74":686,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":688,"_71":-5,"_74":689,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":691,"_71":-5,"_74":692,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":463,"_71":-5,"_74":694,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":467,"_71":-5,"_74":697,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":699,"_71":-5,"_74":700,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":703,"_71":-5,"_74":704,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":707,"_71":-5,"_74":708,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":711,"_71":-5,"_74":712,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":535,"_71":-5,"_74":715,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":718,"_71":-5,"_74":719,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":722,"_71":-5,"_74":723,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":725,"_71":-5,"_74":726,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":97,"_43":728,"_71":-5,"_74":729,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":731,"_71":-5,"_74":732,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":735,"_71":-5,"_74":736,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":739,"_71":-5,"_74":740,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":743,"_71":-5,"_74":744,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":747,"_71":-5,"_74":748,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":751,"_71":-5,"_74":752,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":80,"_43":755,"_71":-5,"_74":756,"_72":73,"_100":-5,"_101":-5,"_83":-5},{"_79":73,"_43":759,"_71":-5,"_74":760,"_72":73,"_100":-5,"_101":-5,"_83":-5},"publicChapterContent","nextChapter","sections",[],"routes/_store+/_layout","routes/_store+/_readers+/_layout","actionData","errors"]

\nAcknowledgements

Table of Contents

\nNotes about this preview edition

\nPart zero: A history of video games

\nAbout the cover

\nBrief contents

\nA history of video games

\nIntroduction to Part zero\n

\nAbout the series

\nIntended audience

\nTitles in the series

\nAbout the book

\nPrior knowledge

\nBook web site and link codes

\nHello, world! Introducing MakeCode Arcade

\nLearning objectives

\nAbout Microsoft MakeCode

\nAbout MakeCode Arcade

\nSystem Requirements

\nView a MakeCode Arcade project

\nStart your engines: Playing games in MakeCode Arcade

\nGame controls in MakeCode Arcade

\nPeek beneath the hood: A look at the code

\nTime for a tune-up: Editing a game in MakeCode Arcade

\nStart MakeCode Arcade

\nBuilt-in projects

\nYour first MakeCode Arcade project

\nCreating a new project in MakeCode Arcade

\nExploring the MakeCode Arcade editor

\nPlanning the first project

\nAdding the first block

\nBlock types

\nThe on start block

\nRenaming a variable

\nAutosave in MakeCode

\nAdding another sprite

\nUsing images from the gallery

\nAttaching controls to a sprite

\nWorking with projects

\nSaving your project as a cartridge

\nLoading a cartridge

\nDeleting a project

\nWorking with hardware

\nSharing your projects

\nMakeCode forums

\nHistory of MakeCode Arcade

\nHello, it’s me! (Or is it I?)—Sprites and your hero character

\nLearning objectives

\nAdditional controls in the MakeCode editor

\nDeleting blocks

\nUndo and redo

\nZooming in and out

\nWorking with tutorials

\nMoving around

\nThe hero character and sprite

\nPlayer sprite velocity

\nConstraining sprite movement

\nUsing the image editor

\nScreen coordinates

\nExploring the screen coordinates

\nSprite coordinates

\nPlacing your character

\nAnimating your character

\nInstalling extensions

\nCreating a walking animation

\nCreating a spinning wheel

\nMore complex animations

\nMaking a background

\nBackground with a solid color

\nBackground image

\nAnimated backgrounds

\nArtwork and prototypes

\nAdditional practice with the image editor

\nAnswers to review questions

\nWhich way did it go? Decisions, conditionals, and basic game physics

\nLearning objectives

\nSoftware development life cycle

\nStep one: Gathering requirements

\nStep two: Project analysis

\nStep three: Project design

\nThe `on game update` block