Another alternative approach to: https://scratch.mit.edu/projects/799694359/ Parameters are stored in lists, and a broadcast message is sent to all sprites to advertise that a new clone is needed. The `who` list says which sprite needs to clone itself, and is always changed last so that all other parameters will be in place when a sprite sees the list change. There is still no protection against two sprites trying to update the lists at the same time and potentially mixing parameters across clones. The `check` variables and lists try to detect if this ever fails. It should be just fine if there's no preemption.
