New sensing boolean block [Scratcher rank]

SuperMarioHome

Cub56 wrote:
Support. For people saying how you could be mean, people can easily find loads of other ways to be mean…
if <(username) = [ someone's username ]> then
    
say [you stink]
end
There are plenty of other ways people can be mean anyway.

Also it might mess up multiplayer games if new scratchers accidentally corrupt the system.

I once found a project where the creator got priority access while I had to wait so long that I ended up turning on turbo mode.

7salad3salad

I can't find any way this would be used for good. I can see this being used to descriminate against New Scratchers.

VedanshS933

7salad3salad wrote:
I can't find any way this would be used for good. I can see this being used to descriminate against New Scratchers.

Even I think that

Scratch On!

MasterBot-X

gigapouch wrote:
It would be nice to have blocks like this:
<user is New Scratcher?>
<user is Scratcher?>
They are supposed to have pointy edges.

Oh, and I deleted the <user is Scratch Team?> block because there is no use for it.

It Would Be Nice, But There Is Cloud data to detect it

scratch_man4581

There's actually a workaround for this that I discovered:

when green flag clicked
set [☁️ Test v] to [0]
set [☁️ Test v] to [1]
if <(☁️ Test) = [1]> then
...
else
say [This user is not a New Scratcher.]

Its primary purpose, however, is to test if a user is connected to the cloud. Notice that

(☁️ Test)

is a cloud variable.

beanyboy512

to everyone saying its abusable then look at these:

if <(username) = [Random scratcher the creator hates]> then
say [LOL Your a noob] 
else
...
end
when I receive [HATED SCRATCHER v]
say (item (pick random (1) to (10)) of [Insults v] :: list)

all these scripts would be reported

Last edited by beanyboy512 (Feb. 21, 2022 14:43:30)

TheElementGuy

pvz_pro wrote:

no support

if <user is new scratcher?::sensing> then
say [HAHAHAHAHAHAHAHA YOUR A NOOB AND CAN'T PLAY!!!!!]
else
broadcast [play v]

It's not like this button doesn't exist.

(Report :: custom)

TheElementGuy

Maybe make it one block.

<status is [scratcher v] ? :: sensing>
<status is [new scratcher v] ? :: sensing>
<status is [scratch team v] ? :: sensing>

(Just have a dropdown.)

Tunde123

VedanshS933 wrote:
-snip-
1. New Scratchers/Scratchers can be blocked
2. There is currently not ST reporting
3. Scratchers might get confused
4. A project can say that you are New Scratcher pls become Scratcher to enter. Then the New Scratcher might get angry and ask everywhere how to become Scratcher

No support for reasons provided.

7salad3salad

I would like to see at least 2 examples of this having a good use. This block seems pointless.

beanyboy512

7salad3salad wrote:
I would like to see at least 2 examples of this having a good use. This block seems pointless.

if <user is New Scratcher?> then
say [No cloud mode activated] for (2) secs
end

Jackson49_test

Bump

Marc92020

workaround: change a cloud variable checker from 0 to 1.
if the variables stays at 0 that means the user trying to play is a new scratcher

k7e

Do both blocks need to exist? You can just use the not block.

gdfsgdfsgdfg

lapisi wrote:
when green flag clicked
if <not <user is [Scratch Team v]:: sensing>> then
…
else
say [Sorry, Scratch Team members aren't allowed] for [2] secs
end
in order to prevent the ST from seeing inappropriate projects

you forgot that see inside exists
so you can defeat the boolean
also ST can delete the project with this bool
same for the username or the anti report sprite

Last edited by gdfsgdfsgdfg (Nov. 12, 2023 13:21:00)

undeterminstic

no support there is no usage

k7e

minecraftmanpp_tutor wrote:
no support there is no usage

Tutorials, explaining why you can't use cloud, etc.

Roblox888i

Marc92020 wrote:
workaround: change a cloud variable checker from 0 to 1.
if the variables stays at 0 that means the user trying to play is a new scratcher

Problem: Cloud variables do not work

lapisi

gdfsgdfsgdfg wrote:
(#96)
lapisi wrote:
when green flag clicked
if <not <user is [Scratch Team v]:: sensing>> then
…
else
say [Sorry, Scratch Team members aren't allowed] for [2] secs
end
in order to prevent the ST from seeing inappropriate projects
you forgot that see inside exists
so you can defeat the boolean
also ST can delete the project with this bool
same for the username or the anti report sprite

true, but people would still try that (though they'd admittedly fail horribly), and such a detector doesn't really have a purpose for anything else

MagicCoder330

erm actually… there is a workaround. /j

Yeah, having a workaround, especially a complex one like the one you need for this, is not a valid reason to reject a suggestion.

But yeah, this seems like a good suggestion. This would definitely have a niche, but it would be useful for cloud projects. also maybe something that only new scratchers can access just for the funny.

Discuss Scratch