I don't understand this rule
Would my script, of which creates clones and goes to specific points on the stage to store data, violate this rule?
To mr_owlssssnap2:
What I mean is no empty or relatively empty sprites. By relatively empty, I mean the sprite can't have only 2 short scripts while the other sprites have 10 long scripts. If there is only one sprite, you can completely disregard the rule.
To bh:
Yeah, you are right with your argument about lists. I will change rule #1 to this: You can't use any blocks from the variables section (you can still use lists), but you can't use any other blocks with built-in variables (idk what else to call them), like:
To cycomachead:
That is probably something I will do in the future.
You can still use non-custom blocks which have a variable block in its definition.
Alright, here is my attempt:
Use WASD to move, and press space to shoot. Your goal is to pop the balloons, and there can't be more than 20. Try to get the highest score possible!
I think this violated it not-so-technically.
I would say that in snap, lists is different, so you should make the title of the topic no variables or lists blocks.
I changed that rule:
you mean upvars? or block vars?
Oh ok then. Try to make a piano.
Blocks like these:
Aight bet. Just give me a day or two (or maybe more).
Ok. Cant wait!
um I don't think you need a variable at all for that in any way, I can't think of a reason why you do need to use one.
i'm guessing you mean upvar?
It s just a project idea. And you can put variables in any project.
this is a no variables challenge, I was just wondering where you would normally use variables in your project idea.
Maybe to store values for key sounds? (E.g. note #'s or Hz values)
I would say something about ask [What is your name?] and wait, but giving it some thought, I wouldn't actually count it. (Although, it is basically a set [ V] to [] for (answer) , just using user input for the value instead.)
But if that was the criteria (any reporter whose value can be changed with a block), I suppose any primitive variable that has some sort of corresponding block to change its value (like costume [ V] and switch to costume [ V]) would be against the rules.
basically already counted for, although you could do the same thing just with a not-empty costume.
Hm? What do you mean by this?
They mean that I already thought about it and made a rule against it
Alrighty then. Changing the rule to "No empty costumes or costumes that are unused".
Technically you can just use the "Audio Comp" library for the piano.
(I barely had time to start on the piano, just saying)