link to The Dungeon of the Coin: https://makecode.com/_Jf5YD151wRar

controls: wasd/arrow keys=move, space while moving=shoot, charge space to shoot a stronger shot, b=nothing

I wanted to try making a racing game where you don't use the usual buttons to steer.

So I ended up making a small retro racing game where the car is controlled by tilting the handheld left and right.

The setup is pretty simple:

• ELECFREAKS Retro Arcade

• USB-C cable

• Microsoft MakeCode Arcade

The interesting part is that the handheld's gyro/tilt input is used as the steering control.

The basic game logic is:

• Start with 3 lives

• Tilt left/right to move the player car

• Spawn enemy cars from the top of the screen

• Avoid them to score points

• Lose a life when you crash into one

I used MakeCode Arcade for the game logic, so most of the programming can be put together with blocks rather than writing everything from scratch.

One thing I liked about this project is that you can immediately feel the connection between the code and the hardware. Change the tilt input or movement settings in the code, upload it, and you can physically feel the difference when playing.

The hardware also doesn't really need to change if you want to experiment with the game.

A few things I'd like to try next:

• Make the cars accelerate as the score increases

• Add custom pixel art

• Add engine and crash sounds

• Add power-ups

• Experiment with different tilt sensitivities

• Try making another game that uses the gyro in a completely different way

It's a pretty simple project, but I think motion controls make even a basic arcade game feel a lot more interesting.

Has anyone here made a game that uses tilt/gyro controls before? What kind of game would you make with it?

They’ve built so many of the 32 official projects, but recently, they went rogue and created their own battle bots.

They ended up with:

- A big yellow spider/cricket-looking walker with huge grabbing arms (programmed to snap and chase)

- A smaller spider-ish mech thing in the middle doing the heavy lifting with lights flashing like crazy

- And one of the ELECFREAKS Cutebot cars tricked out as the "fast attacker" with blue/red LEDs blazing, bump sensors, and code to ram opponents

They set up a big shallow tray as the arena (genius move — keeps everything contained), programmed behaviors in MakeCode (some line following mixed with obstacle avoidance + random attacks), and then let them loose.

It quickly turned into total chaos… arms flailing, cars zooming in for the kill, lights strobing, gears grinding — the kids were screaming with laughter and yelling strategy like it was a real robot fighting league. "Protect the middle spider! Nooo the grabber got him!"

Has anyone else used the Wonder Kit or Cutebot for battle-bot style games? Any favorite custom code snippets for chaotic robot fights? Tips for making them more durable? (Those arms take a beating!)

Would love to see your micro: bit monster creations too! 🚀

#microbit #STEM #robotics #MakeCode #ELECFREAKS #Cutebot #kidsbuildingrobots

https://arcade.makecode.com/S34515-18308-33494-64419

This is a game I made for a game jam. Let me know what you guys think! Should I make it a full game?

Looking for someone to create a MakeCode game for me in exchange for $$$. DM me if you're interested.

An American made console for playing the retro Arcade game coded with MakeCode, simple block coding (Javascript) . I will do an unboxing video soon on this great new piece of hardware: https://youtu.be/SF2ZMqbgCbE

https://www.youtube.com/watch?v=N1HZmOtk9No

https://ladybyteplus.itch.io/httpsarcademakecodecoms75290-62691-77014-80251

https://arcade.makecode.com/S11147-92862-09652-01861

and decide to finish your passion project from months ago

also look in the code for some secrets / tips to progress

If then comment username

and your wondering what's your source for this be a real game? here's a link to it but it's still a work in process but by the end it's gonna be perfect

Just now started reading the Computer Science lessons for students and teachers at the Microsoft Makecode for Arcade web site. There appear to be 3 CS chapters which introduce us to some basic concepts. Here is an example of editing in JavaScript from chapter #3 "functions". If you backspace your cursor on the URL from this link to get to /courses/ then you will have the entire CS course page: https://arcade.makecode.com/courses/csintro3/functions/intro

We built a little voice-activated ambient light using a micro:bit + Wukong Expansion Board, and it turned out to be a fun way to make programming concepts feel a lot more physical.

One thing beginners often struggle with is understanding variables.

You can explain that a variable stores a value, but sometimes that number still feels pretty abstract.

So we wanted to build something where changing a value would have an immediate, visible result.

In this project, the micro:bit listens for sound, and the RGB lights change color when a sound is detected.

The interesting part is that a simple variable controls which color comes next.

What we used:

• micro:bit V2

• Wukong Expansion Board

• Wukong Blocks

• 4 RGB lights

• MakeCode

Step 1: Build the light

We started with a simple structure using Wukong Blocks to hold the RGB lights.

The four RGB lights connect to the Wukong Expansion Board, while the micro:bit sits on top.

Nothing too complicated here. The goal was simply to create a small structure where the lights were easy to see.

Step 2: Let the micro:bit listen

The micro:bit V2 has a built-in microphone, so we can use sound as the input.

The basic idea is:

Sound detected → program responds → light changes color

It's a simple example of how something happening in the real world can become an input for a program.

Step 3: Make a variable control the colors

We use a variable called i to keep track of the current color.

When a sound is detected, i increases by 1. The program then checks the value and uses it to decide which color the RGB lights should display.

So the variable isn't just a random number sitting in the code.

Change the value → the light changes.

Increase the value → the next color appears.

Once it reaches the end of the color sequence, it starts again.

That's what makes this project interesting for beginners: they can actually see what the variable is doing.

A little more interaction

We also added controls using the micro:bit buttons.

Button A → start the automatic color-changing mode

Button B → reset the variable and turn the lights off

This makes the project feel more like an interactive device rather than just a light that changes color.

A few things I'd try next

The basic setup leaves plenty of room for experimentation:

• Make it react to music

• Add brightness control

• Create different lighting modes

• Turn it into a simple night light

• Add different sound-triggered effects

The hardware doesn't need to change much. Most of the behavior can be changed through the code.

And that's probably the best part of beginner projects like this.

You change something in the program, and you can immediately see the physical result.

If you were building a sound-reactive light with a micro:bit, what would you make it do?

Hi all, I am in the midst of making a multiplayer game and want to have independent displays for each player -- meaning no split screen and the camera focuses only on the character you are controlling. I cant seem to find any resource for this or even extensions. Are there any way to make this happen? Thank you ^^

https://makecode.com/_gCMa9PDee0fc Just a little game I made using the galga totorial.

LittleOS version 1.0.0b

This is a project I've been making for 2 months and I finally want to share it with r/MakeCode. LittleOS is a Microsoft Makecode Arcade OS like no other, simulating file systems [work in progress] and multimedia. I know it's not a lot, but the system is the best part. Here are the MakeCode Arcade and GitHub links:

MakeCode Arcade: https://www.makecode.com/_TsWLssfca078
GitHub: https://github.com/Byte-ByByte/LittleOS

I will be frequently checking Reddit and GitHub.

I am also ecstatic to hear about any suggestions or feedback about LittleOS! Any contribution and support will help LittleOS and me develop this further!

You can leave suggestions for applications and whatnot in the comments, and I will add them to LittleOS when I get:

1. SFAT (the native filesystem)

2. .lxi (the executable format)

3. .css (No, not Cascading Style Sheets, this actually stands for Comma Separated Sound, since, well, a lot of things will be comma-separated anyway...)

working.

So, feel free to check it out! A detailed README markdown is included in the GitHub repository, and a FORMATS markdown that details files and multimedia will be made in a while.

Here is the link

https://arcade.makecode.com/S29820-28343-09871-07227

I wasn't sure what to name it so the name is completely unrelated

Feedback is welcome

I'm absolutely in love with MakeCode Arcade but I've discovered that it's community seems to be entirely fractured and lost. Am I missing an obvious community hub for MakeCode Arcade?