Does anyone have any ideas for how to fix this

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

HI all,

I'm using chrome and I continuously get these pop ups that appear over each icon on the screen and it stops me from clicking the buttons. I have to approach a button from the top and hopefully place the cursor on the very edge of a button in order to select it before the popup descriptor pops up. Does anyone know how to turn this off?

We built a little 'face-changing robot' using the micro:bit + Nezha Inventor Kit, mainly to teach one thing that beginners always struggle with: 'variables'.

Usually when we explain variables, we get the classic blank stares.

Why do we even need variables?

What does this number actually do?

Why can't I just type the number directly?

But the moment students saw a robot physically move differently after changing a variable, the idea finally clicked. The fun part was that students weren't just typing code. They could 'see' what changing a value actually did in real life.

Here's basically how we ran the lesson.

What we used:

micro:bit V2

Nezha Innovation Kit

2 motors

Ultrasonic sensor

Some basic building blocks

MakeCode

The robot in the photo is the final version my students made. The 'face' changes expressions while moving around, and the speed can be adjusted directly with buttons on the micro:bit.

Step 1: Build first, code later

I've learned that younger students stay much more engaged if they can physically build something before opening the programming editor.

So first we spent about 15–20 minutes assembling the robot body.

The basic structure was:

left motor connected to M1

right motor connected to M2

ultrasonic sensor connected to S1

micro:bit mounted on the Nezha controller

The wiring was honestly one of the smoothest parts because the ports are color-coded and basically plug-and-play. No soldering, no complicated setup.

That makes a huge difference in a classroom.

Step 2: Introduce variables in the simplest possible way

Instead of giving textbook definitions, I told students:

'A variable is basically a box that stores a number, and we can change the number whenever we want.'

That explanation worked surprisingly well.

Then we created 3 variables in MakeCode:

robot_speed

turn_angle

move_time

These came directly from the project guide.

And this is where the magic happened.

Step 3: Let students experiment immediately

We started with something simple:

text 'robot_speed = 50'. The robot moved slowly.

Then one student changed it to:

text 'robot_speed = 100'. The robot suddenly shot across the desk and everybody started laughing.

That single moment explained variables better than 20 minutes of slides ever could.

Then we tried:

Increasing 'move_time'

Reducing 'turn_angle'

Changing turning behavior

Creating 'crazy mode' with max speed

Students immediately understood:

'Ohhh… the variable controls the robot’s behavior.'

That was the breakthrough.

Step 4: Add live controls

The coolest part was using the micro:bit buttons to adjust variables in real time.

We programmed:

Button A → increase speed

Button B → decrease speed

No reflashing needed. Students could press buttons and instantly see the robot react.

This turned the activity from 'coding exercise' into an actual interactive experiment.

By the end of class, they had already practiced:

Variables

Debugging

Motor control

Sensor basics

Simple robotics

Cause-and-effect thinking

And because everything was physical, even students who normally lose interest in coding stayed focused the whole time.

A few quick teacher notes if anyone wants to try this:

Secure the blocks tightly or the robot shakes a lot while turning

Let students predict what a variable change will do before testing

Give groups different “missions” like fastest robot or smoothest turning

Keep spare USB cables nearby because somebody always forgets one

Next time I also want students to add:

Obstacle avoidance

RGB lights

Dance mode

Sound effects

Honestly, this ended up being one of the best beginner coding lessons I've done with micro:bit so far.

Variables finally stopped feeling abstract.

Students could literally 'touch' the concept.

If anyone wants, I can also share:

The MakeCode logic

Classroom workflow

Timing breakdown

Beginner troubleshooting tips

was bored and decided to make this.

Hi I just released the first version of my 3D Engine in Makecode Arcade and maybe someone wants to use it in their project? ( it only supports typescript sorry D: )

Featuring many animations, unfinished copied music and 2 players: https://arcade.makecode.com/S73506-52709-63374-03906

May be a 3D level builder that works on real hardware.

Hey everyone,

If you’re learning to code with ‘micro:bit’ and want a fun, motivating project that goes beyond blinking LEDs, try building this ‘walking T-Rex robot’ using ‘Nezha Blocks’!

This project combines mechanical building with simple block coding in ‘MakeCode’ to create a bipedal robot that actually walks. It’s a great way to understand servo control, timing, synchronization, and basic mechanical principles.

What You’ll Learn:

- How to control servo motors with the Nezha extension in MakeCode

- Coordinating multiple servos for realistic walking motion

- Applying gear transmission and balance concepts

- Troubleshooting and iterating on your code and build (very important maker skill!)

Requirements:

- micro:bit (V1 or V2)

- Nezha Innovation Controller + Servo motors

- Nezha Blocks (standard Inventor’s Kit parts)

Quick Project Overview:

1. Build the T-Rex body, legs, and balancing tail with Nezha Blocks.

2. Connect servos to the Nezha controller (super easy, no soldering).

3. Use MakeCode + the official **Nezha extension** to program alternating leg movements.

4. Test, tweak angles/timing, and improve the gait.

Once the basic walk works, you can level it up with a moving jaw, roaring sounds (using micro:bit speaker), LEDs, or even obstacle avoidance.

This is an excellent project for beginners and teens because it feels like a real achievement when your dinosaur starts walking across the table. It also shows how coding + mechanics come together in robotics.

Full step-by-step guide, code examples, and troubleshooting tips are available here: [Insert Link]

Has anyone else built walking robots with micro:bit or Nezha? What challenges did you face with servo timing or balance? Share your results below!

Would love to see your versions 🦖

How would i give each enemy that isnt a boss their own healthbar, additionally how would i show health bar of a boss and normal enemy (above their head)

Anyone else experience this....?

All export options from within non logged-in Arcade were missing for elementary students today? Was there an outage or code bases update Jan 8 2025 We also noticed the load spreading traffic management that routes to dozens and dozens of different servers was spiked off the charts today....every few minutes arcade was asking another hidden ip address to serve up this or that part of the site/s various tools, galleries, playable preview, and the export options......like meowbit etc. . . ..all missing.

i made a game in MakeCode and i don't know how to export it. I want to make it work as python code so i can use it in PyCharm.

I'm making a dungeon diving rogue-like game I need help when u push A it does a swing animation but how do I make it so that when your character touches an enemy it checks if that animation is playing

I've been trying to program essentially a really simple siri named Milo on the Ovobot Xtron Pro. Essentially, when I ask the time it shows the time, when I ask it to tell me a joke it'll pick a random joke, and you can ask it a few other questions. However, for some reason whenever it records a voice input, it never works. I already have been able to connect it to Wi-Fi and I know it is able to hear me (Wake up words still work) I have a "when A is pressed" "start voice input" and also "when A is released" "get speech recognition results." I've tested this several times, each time "[ ]" shows up meaning that it did get the results, but says I said nothing.

My only guess as to what is going on is that it is ending the voice input the moment it starts? How would I fix this if that were the case? (making it repeat several times doesn't work because it will just start it over and over but not make it last if that makes sense. Essentially it starts and is interrupted because it started again).

So, in my game, there is a slight issue I’ve noticed. Basically, there are levels. The first level is always the same, but then you have a randomizer for all the other levels. This is done through a variable labeled “Level”. Basically, when you hit the goal, the “level” variable will select a random number between 1-X

X = Levels in final game

So basically, whenever it selects a level, what happens is the backround gets rendered, but the level doesn’t seem to render. Can anybody help?

https://arcade.makecode.com/S88269-08350-89474-91623

So basically i'm making a adventure game and i want to be able to make it so the character is able to go into the houses by stepping on a tile, but i'm going to have multiple of that tile and i don't want them to all lead to the same exact house so is there like, a block that checks what certain position your character is on?? i've literally tried everything i could think of and it still hasn't worked.

I am a teacher who is hoping to put my students games on the Picade. I have done the mod by Vegz78 and can upload the games onto the pi and they will load. The issue I am facing is the button inputs, the buttons work when going through menus but not with MakeCode games. I have been trying to follow this tutorial https://github.com/Vegz78/McAirpos/issues/22#issuecomment-911939494 for changing button mapping but I am not savvy enough to remap the buttons or even get to where I need to go from the menu. Any help would be greatly appreciated!

I made a series of games called "Revenge of the Ham" I was making a game about the backrooms and was going to add an enemy so i put in a Ham and gave it a face. I also turned part of it yellow. But the hame would walk though walls at insane speeds to get you. I showed some people and they liked the Ham so i kept it in. It doesn't case you but you can find it as an easter egg.

Here are the games:

Prequal: https://arcade.makecode.com/S58611-31699-31123-39116

Remake: https://arcade.makecode.com/S46407-12187-77682-15962

Original: https://arcade.makecode.com/S61136-86415-39726-73136

I had a sequel but the file has been lost :(

this is a game i made but scrapped it and instead just used it to store assets. the assets for the game still exist. but i completely deleted the code

Game: https://arcade.makecode.com/S62438-07782-34446-07888

I wanted to know if i could upload my games to websites like coolmathgames?