Quick answer: Construct 3 instances of the same sprite type all showing the same instance variable value despite being set independently? You may have grouped them in a Container by accident.
Two enemy clones; setting one’s HP to 50 sets both. They share a Container that links instance variables across types.
Container vs Instance
Construct 3 Containers link multiple object types so they spawn / pick together. Instance variables on Container members can become shared in unexpected ways when picking goes wrong.
Pick Correctly
Use Pick instance — nth or Pick by unique ID for individual changes. Without explicit picking, “Set HP” applies to all instances matching the event scope.
Per-Instance Setup
On a Spawn event, the new instance is auto-picked — perfect time to set initial vars. Setting them later requires explicit picking.
Family Conditions
Family conditions filter across multiple types. Combined with picking, you can target one specific instance among many.
Verifying
Setting an instance variable affects only that instance. Damage / state changes don’t leak across copies.
“Shared state across clones is a picking problem. Always pick the instance you intend to change.”
When in doubt, add a quick “Pick by unique ID” debug check at start of event — you’ll catch picking scope bugs in seconds.