I have an idea for a block like this:
That lets a sprite move an amount of steps at a certain speed,
And two blocks like this:
That can help you make scripts like this:
when gf clicked wait (1) secs forever{ wait (1) secs move (10) steps }
teleporting at a certain speed doesn’t make sense. By definition, it is instant.
Is there any use case for your suggestion - why would you need to use that script you showed?
How would you even know what the (done :: sensing block is checking for?
why would you even need the wait block?
(oh god this kinda sounds like ai)
Prob somting like this 
It’s from @sathvikrias Cool Custom Blocks. And for the done block what is being finished?
yeah, that was my question. In @henhen123’s case, it is checking for the wait block. How would snap know what it would be checking for? I have no idea. Why would you need it? no Idea either.
ah, ok. That’s a simplified version of the Animation library block, I believe.
Here’s the thing, it waits till the 1 second is over, to then run the code
Well, then I guess I should learn to pay more attention
But what about the other block, where you can set a certain speed
So do you still want the reporter
I mean then there will be ways to make a simple code like the one you just put in, to turn slightly more advanced
Why not use the simple way instead of making it more complicated then?
well there are multiple ways to do many things on Snap*!*
Then use the simple way it will make your code more efficient then having to use custom blocks you get to use pre-made blocks?
But your using more blocks which = more lag. But with this one it is always checking for a key press but with the other one you have to put it in a forever block with takes more time with makes the project come out slower.
I think henhen123’s way is more efficient. It doesn’t really take any extra time, and it is better performance wise.
If you put a move (10) steps in a forever loop, it will run much more cleaner than if you put it under a hat block. Of course, you could just do repeat until <> { } under a hat block, but I honestly prefer the forever loop so it won’t run when the project is stopped.
EDIT: oh gosh I may have repeated myself a few too many times in this reply.
but it’s laggier; I don’t understand how it’s more advanced. If it isn’t broken works perfectly, why try to perfect it?
The forever if checks every single frame, but the hat block doesn’t. I’m not entirely sure what you mean by more efficient.
okay? but there is no reason to add the suggestion, if those blocks are already there.
exactly.
My final thoughts: don’t overcomplicate code to make it do the exact same thing.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.