k0d3rrr wrote:

I've fixed the block. Here's what it might look like:

shake screen for [1] secs at [10] intensity:: motion

I now support this idea because it could make a cool explosion-shaking effect.

twogadugary wrote:

I feel like this wouldn't be versatile enough for it to fit in Scratch - every Scratch feature can be used in many ways and often teaches a part of real programming. While this block would add a feature that's incredibly painful to recreate without it, there's not many scenarios where this would be needed, and it'd end up being one of those blocks many users go their entire time on Scratch without using.

The Design Principles for Scratch says the following:

Low Floor & Wide Walls

In order to encourage a varied and diverse set of interactions, we explicitly include elements and features that are easy for kids to understand (low floor), but general enough to support diverse uses (wide walls).

twogadugary wrote:

I feel like this wouldn't be versatile enough for it to fit in Scratch - every Scratch feature can be used in many ways and often teaches a part of real programming. While this block would add a feature that's incredibly painful to recreate without it, there's not many scenarios where this would be needed, and it'd end up being one of those blocks many users go their entire time on Scratch without using.

-Levitating- wrote:

I support this, as long it doesn't get used for inappropriate content

k0d3rrr wrote:

Ahh, ahh, ahh, ahh, bumping topics, bumping topics!
Ahh, ahh, ahh, ahh! Bumping topics.. Bumping, topics!

LAVEna_THe_NicE_Guy wrote:

is this a motion block for backdrops

define shake effect (start x) (start y) (intensity x) (intensity y) <fade out?> (time)
reset timer
set [Intensity Y v] to (intensity y)
set [Intensity X v] to (intensity x)
if <fade out?::More_Blocks> then 
set [Start Y v] to (intensity y)
set [Start X v] to (intensity x)
repeat until <(timer) > (time)>
go to x: ((start x) + (pick random ((intensity X::variables) * (-1)) to (intensity X::variables))) y: ((start y) + (pick random ((intensity y::variables) * (-1)) to (intensity y::variables)))
set [Intensity X v] to ((Start X) / ((time) / (timer)))
set [Intensity Y v] to ((Start Y) / ((time) / (timer)))
end
else
repeat until <(timer) > (time)>
go to x: ((start x) + (pick random ((intensity X::variables) * (-1)) to (intensity X::variables))) y: ((start y) + (pick random ((intensity y::variables) * (-1)) to (intensity y::variables)))
end
end

qloakonscratch wrote:

k0d3rrr wrote:

I've fixed the block. Here's what it might look like:

shake screen for [1] secs at [10] intensity:: motion

I now support this idea because it could make a cool explosion-shaking effect.

When thinking of suggestions, I don't think it's recommended to make suggestions for blocks that only have one way to be used.

This being said, I don't see many other ways to use this. Maybe an Earthquake or (though farfetched) a tornado? Then again, you stated a moderate workaround in your original post that could be used in all of the sprites to make a shaking effect.

I feel twogadugary explains this quite well:
-big snip-
If you go to https://scratch-mit-edu.ezproxyberklee.flo.org/developers and scroll down a bit, you'll find the design principles for Scratch, which they follow pretty strictly. Let me quote it directly, specifically the 2 that matter most in this case:

-big snip part 2-

This tells us that Scratch prefers to include elements and features that are easy for kids to understand, but general enough to support diverse enough uses. I don't think would fall under “diverse enough” or just “diverse” in general, according to Scratch's standards.

spocite wrote:

define shake effect (start x) (start y) (intensity x) (intensity y) <fade out?> (time)
reset timer
set [Intensity Y v] to (intensity y)
set [Intensity X v] to (intensity x)
if <fade out?::More_Blocks> then 
set [Start Y v] to (intensity y)
set [Start X v] to (intensity x)
repeat until <(timer) > (time)>
go to x: ((start x) + (pick random ((intensity X::variables) * (-1)) to (intensity X::variables))) y: ((start y) + (pick random ((intensity y::variables) * (-1)) to (intensity y::variables)))
set [Intensity X v] to ((Start X) / ((time) / (timer)))
set [Intensity Y v] to ((Start Y) / ((time) / (timer)))
end
else
repeat until <(timer) > (time)>
go to x: ((start x) + (pick random ((intensity X::variables) * (-1)) to (intensity X::variables))) y: ((start y) + (pick random ((intensity y::variables) * (-1)) to (intensity y::variables)))
end
end

k0d3rrr wrote:

That's a really complicated workaround, and not a lot of people know how to do that. Just saying. (I'm not mad.)

point towards x: () y: ()::motion 

solomonw2440 wrote:

SUPPORT
this could be an extension.

-Valtren- wrote:

so basically you're suggesting camera control?

DASniperIC wrote:

Now, I know that this script exists

go to x: ((0) + (pick random (-10) to (10))) y: ((0) + (pick random (-10) to (10)))

but that only shakes sprites, and making the entire project screen shake in a game isn’t easy or possible altogether. Instead, why not have the entire project screen shake with a script?
It would probably look like this:

shake screen for [1] secs [10] intensity:: sensing

It basically acts the same as the

go to x: ((0) + (pick random (-10) to (10))) y: ((0) + (pick random (-10) to (10)))

script but it shakes the entire project screen, with a black background underneath the screen.
the intensity part is the same as the intensity of the ‘pick random’ numbers in a sprite shaking workaround script

Send link to original suggestion if this was already suggested