title is self explanatory.
Right. And you cannot even select "Turtle sprite" in the block's dropdown if it is in the Stage's scripting area. So you had to somehow artificially fabricate this situation, e.g. by dragging the block with this selection of from a sprite's scripting area and dropping it onto the Stage's icon, or - my favorite - using metaprogramming. You know, I mostly do value your bug reports, but this one isn't in your usual ball park. You can do better thank this!
yeah.
I need this so that I can create a new empty sprite, do you know of any other way to do this? (it has to work from the stage's scripting area and work when there are no other sprites.)
thats what I tried, but then I needed to use it in the stage and then it errored. thats why I
Why does it have to be done in the stage? Can't you just assign this task to some particular sprite?
I have a feeling it's for when there is no other sprite.
You can use it in the Stage's scripting area, but you need to have another sprite in the project (which you could also hide).
yeah. does this mean it is impossible?
Scisnap to the rescue!
I don't think this really constitutes as a valid bug report—this is obviously unintended behavior
Do you mean intended?
Edit: I finally understand the reasoning behind this: the stage can't be the parent of the new clone. So even if all you really want to do is create a sprite via cloning, you can't have that intermediate step because all clones must have parents. Thus, the SciSnap! block skips that step and there are no problems.
yes, but that was why I was so confused about the lack of turtle sprite in stage
-- the turtle sprite clone has no parent!
yes, that's the point of the "Turtle sprite" option -- to make a new sprite that is, actually, not a clone at all, but an independent new sprite without any inherited links to any other sprite.
yes, but that is why I was confused as to why it wouldnt work in the stage.