Objects & Blueprints: Proving Two Objects Don't Secretly Share a Value
Two objects made from the same blueprint look identical until you change one. Here's how to actually check they're separate.
The Objects & Blueprints set's challenges make more than one object from the same blueprint and expect each to hold its own values independently. It's a reasonable worry to have while learning it: if two objects come from the same description, does changing one somehow change the other? The honest way to answer that isn't to assume -- it's to make two objects, change only one, and show both.
Press Run to see what your code does.
That prints green, then blue -- changing carA a second time never touched carB, even though both came from the exact same BLUEPRINT Car. Each CREATE Car AS ... line makes a genuinely separate object with its own copy of every property the blueprint defines; the blueprint is a description used to build objects, not a value the objects go on sharing afterward. If a bug in one of these challenges looks like "changing one object changed another," the far more likely cause is a typo that has both names pointing at the same object -- CREATE Car AS carB never actually running, for instance -- not a genuine sharing mechanism, because pseudocode, Python, and JavaScript all give each object its own independent copy of the blueprint's properties.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.