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

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.

Bump.

k0d3rrr wrote:

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

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

I semi-support this idea, as shown by the pros and cons of this idea:

Pros:
-Helpful for making a meme or an explosion effect.
-Shakes the WHOLE screen and not just the sprites.
Cons:
-If set at high intensity, it could give someone who has epilepsy seizures.
-It might also lag slow computers and mobile devices.

Then don’t set it at high intensity

what about a limit (probably 1/2 or 1/4 of the size of the axis)
more (probably useless) blocks:

shake screen [left-right v] with intensity [10] :: motion // can only shake up to 120
shake screen [up-down v] with intensity [10] :: motion // can only shake up to 90
shake screen [all v] with intensity [10] :: motion // can only shake up to 105

stop shaking [left-right v] :: motion
stop shaking [up-down v] :: motion
stop shaking [all v] :: motion

bump

You could actually very easily do this.

First, go to the stage.
Make two global variables: shakeX and shakeY.
You can set these to random values between -N and N whenever you want to shake the screen.

Now, say you have a movement script for each sprite. It's going to a certain x-position and y-position, right?

go to x: (foo) y: (bar)

Simply add shakeX and shakeY to foo and bar (or whatever they might be):

go to x: ((shakeX) + (foo)) y: ((shakeY) + (bar))

Bituvo wrote:

You could actually very easily do this.

First, go to the stage.
Make two global variables: shakeX and shakeY.
You can set these to random values between -N and N whenever you want to shake the screen.

Now, say you have a movement script for each sprite. It's going to a certain x-position and y-position, right?

go to x: (foo) y: (bar)

Simply add shakeX and shakeY to foo and bar (or whatever they might be):

go to x: ((shakeX) + (foo)) y: ((shakeY) + (bar))

sure , it'll be fun doing that in 100 sprites.

Support as long as there is an epilepsy warning when you start up a project similar to ones seen when the username block in any project that uses the block

all of your ideas are pretty good ( @Bituvo ’s is the smartest idea). the ‘bump’ ones seemingly provide no context to me whatsoever

and yes, i support the idea of adding an epilepsy warning or a limit to how shaky you can make the screen.

Bituvo wrote:

You could actually very easily do this.

First, go to the stage.
Make two global variables: shakeX and shakeY.
You can set these to random values between -N and N whenever you want to shake the screen.

Now, say you have a movement script for each sprite. It's going to a certain x-position and y-position, right?

go to x: (foo) y: (bar)

Simply add shakeX and shakeY to foo and bar (or whatever they might be):

go to x: ((shakeX) + (foo)) y: ((shakeY) + (bar))

What if people don't know how to make this complicated coding? And sure, they can just use this, but how would they understand it?
But if it already has a script to it, then I am not sure about adding this block. It will simplify doing it, though.

i mean idk choice is cool but it personally makes me feel rather uncomfortable

Banana

This topic has been brought back to life.
In other words, bump.

What's this? A bump!
And not:
Bring
Up
My
Post
Instead, it's bump, as in “Bump this topic to the top of the page!”

OH NO! I forgot what a bump is!
*goes to Advanced (Off-)Topics*

AT (Advanced (Off-)Topics) wrote:

Umm, bump stands for:
Better
Use
Modified
Python

That wasn't helpful at all!
*goes to Questions about Scratch (or Random Stuff)*

Questions About Scratch (or Random Stuff) wrote:

Person 1 wrote:

A bump is an area in the ground that is not even with the ground

Person 2 wrote:

Person 1 wrote:

A bump is an area in the ground that is not even with the ground

No, no, check out this article that talks about what a ‘bump’ is!

k0d3rrr wrote:

Person 2 wrote:

Person 1 wrote:

A bump is an area in the ground that is not even with the ground

No, no, check out this article that talks about what a ‘bump’ is!

Thanks! I'll close this topics now…

And that was the end of… whatever that thing was.
Anyways, that was a long bump.

Bump!

you could make every sprite have the shake script and then make the backdrops a sprite so you can ummm make the whole screen shake

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.

so, would this be an entirely new block or an extension?