Unfortunately, I CANT go the simple way. Also please remember that all
the code in my initial post is an EXAMPLE of what I need to do, NOT a snippet.

Once all the entities get created (by ents_startup), there will be multiple
other functions and actions that form links directly to some of these entities
BY REFERENCE, rather than be ents-index-number.

Because of this, I am unable to ent_remove any of these entities without risking crashes.
Thats why Ive gone with the ent_morph, which is a new function for me.
Ive always gone for the ent-remove & ent_create combo before now.

Seeing as I now KNOW that ent_morph 'breaks' the ent_clone,
then YES it is obvious that ent_clone followed by ent_morph is a waste.
And as I said before, ent_remove is not available to me.


So I think my next option is to try playing with ent_purge and ent_preload.
Maybe by juggling with one or both of them I can find a way to flush out the
ent_clone'd data and be able to reuse its memory space...
eg: "ent_create; while{ ent_purge; ent_morph; ent_clone; wait;}" ... or something.