Eon and his dad already know that in BeamNG the crash-test dummy "falls out" and the cars crumple — "it's not real life," Eon laughs, "it's a Barbie." But last time they could only smash cars by hand. Today they want more: they heard you can pre-program a scenario — two cars crashing into each other — by pressing one key. So they load up a race track, wait through the long graphics load, and go hunting for the hidden tool.

F11: from player to game developer

The secret is F11. Press it and the screen fills with menus — road tools, an AI editor, a vehicle list. "We enter into the game development mode," Dad explains, "and we can do all sorts of crazy stuff." That's the big idea Eon keeps coming back to all video: in the normal game you drive the car, but in the World Editor you're the game developer who controls everything — spawning vehicles, deleting them, even bending the rules of the world.

While the cars load, they spot something neat. One vehicle shows up as a plain gray shape with no color. "It's loading meshes," Dad says. "The mesh is like when you're doing the model — we don't have the texture yet." So Eon learns the order a 3D object comes to life: first the mesh (the bare shape made of connected points), then the texture (the skin painted on top). They even debate a little antenna on one car — is it a radar that "sends out waves like a satellite"? — before the real experiment begins.

Spawn new, not replace — and the undo button

Their first goal is simple: get two cars so they can crash. Dad shows the rule that matters most: when you add a car, choose "Spawn new, not replace." Pick "replace" and your current car becomes the new one; pick "new" and you get a second car beside it. "We want as many cars as possible," Eon decides.

Then comes the lesson that stings. Deleting cars they don't like, they click one too many — "Oh no. Did we delete our vehicle?" Dad reaches for the rescue button: Undo. But undo only takes back your last action, and they'd done more since, so it can't bring the car back. "We just lost it," Dad shrugs. "Doesn't really matter — we can spawn another." It's a real computer lesson: undo is powerful but short-memoried, so it's safer to add than to delete the thing you care about.

Record a path, then press play on a loop

Here's the trick that makes "pre-programmed" crashes work: the Script AI editor. Eon picks a car, hits record, and drives it forward into a crash. Then he stops recording — and the route is saved. Now when he clicks execute scenario, the car drives that exact same path by itself. "I'm not even pressing it," Eon says, holding his hands up. "It's a simulation!" That's how the wild crash videos on YouTube are made: record the trajectory once, then replay it perfectly every time.

He goes further. There's a loop button — turn it on and the car resets to its start and runs the route again and again, no clicking at all. Eon switches to first person ("dash-cam footage!") and watches his own car get smashed over and over until he's dizzy. He even learns why the car can't be steered during playback: "You can't control it because it's already scripted." To drive freely again, you have to delete the script first.

Bonus: turn off gravity

Because he's the developer now, Eon starts changing the world itself. He finds the gravity setting and cranks it strange — and a Mustang suddenly flies upward instead of falling. "What? How?" he yells. "I believe you still got negative gravity — I didn't see the car fall." Changing one rule (gravity) and watching what breaks is exactly how you figure out what that rule normally does.

All through the chaos, Dad keeps slipping in a real-life note: "If you don't have a license yet, don't go drive." In the game you can crash a pretend Lamborghini a hundred times and reset — in real life, you can't. The editor finally jams on the last try ("we'll solve this tomorrow"), but Eon has already learned the whole loop: set it up, run it, watch, fix it.

Try it

Open BeamNG and press F11 to enter the World Editor. First, spawn new (never "replace") so you keep two cars. Pick one, open the Script AI editor, hit record, drive a short path, then stop — and press execute to watch it drive itself. Now change one thing and run it again: try a heavier truck, a sharper angle, or flip the gravity. Each time, predict out loud what will happen before you press play, then see if you were right. That's you being the game developer — and a scientist.