New sensing boolean block [Scratcher rank]

fdreerf

Scratchperson1000000 wrote:
T-the block doesn't detect the username it detects the rank

The same logic still applies; you can prevent users from using a project using it. It's just that not everyone is a terrible person who hates new scratchers.

Navy147

ExtremeLogic wrote:

spgame05 wrote:

ExtremeLogic wrote:

VoltageGames wrote:

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
    
say [you stink] for (2) secs
end

My changes to that:

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
    
say [you stink] for (2) secs
end
if <user new scratcher? :: sensing> then
    
say [get off of this project] for (2) secs
end

Then they would be being mean to themselves.

They could fix that.

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
if <(username) = [their username]> then    
do nothing
else
say [you stink] for (2) secs
end
end
if <user new scratcher? :: sensing> then
    
say [get off of this project] for (2) secs
end

Please dont say you stink thats a mean comment, i already reported it

Navy147

https://assets.scratch.mit.edu/f2cb8096bc3cbbc3ed65142e325b0918.svg

Scratchperson1000000

Navy147 wrote:

ExtremeLogic wrote:

spgame05 wrote:

ExtremeLogic wrote:

VoltageGames wrote:

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
    
say [you stink] for (2) secs
end

My changes to that:

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
    
say [you stink] for (2) secs
end
if <user new scratcher? :: sensing> then
    
say [get off of this project] for (2) secs
end

Then they would be being mean to themselves.

They could fix that.

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
if <(username) = [their username]> then    
do nothing
else
say [you stink] for (2) secs
end
end
if <user new scratcher? :: sensing> then
    
say [get off of this project] for (2) secs
end

Please dont say you stink thats a mean comment, i already reported it

they only used it for an example lamac

portalpower

set [test v] to (☁ test)
change [☁ test v] by (1)
if <(☁ test) = (test)> then
new scratcher script::custom
else
scratcher script::custom
end

Scratchperson1000000

mega bump

PoIygon

ExtremeLogic wrote:
No support. This use would be abused and a lot of people with no hearts would just limit their projects to a specific rank, which wouldn't be fair.

They already do that with could variables.

derpmeup wrote:

VoltageGames wrote:

if <user scratch team? :: sensing> then
    do nothing
end
if <user scratcher? :: sensing> then
    
say [you stink] for (2) secs
end

That's why i don't support.

That’s why you can report.

6littleman wrote:
ExtremeLogic wrote:
No support. This use would be abused and a lot of people with no hearts would just limit their projects to a specific rank, which wouldn't be fair.
no affense but I agree if I was a new scratcher there could be games that I could not play and well… scratch is for all

They already do that with could variables.

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]

That’s why you can report the project.

ThatExplosivePigeon

For the argument that this could be abused, that is irrelevent. There are at least 9 blocks that can be abused like

create clone of [ v]
forever

end
delete this clone
(☁ player)

and several others. For the suggestion, support! Would make adding a warning to a game that new scratchers can't use mualit player easier!

monomial

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]

That’s why the report button exists.
mockups:

<user is a [scratcher v]? ::sensing>

<user is a [new scratcher v]? ::sensing>

<user is a [ v]? ::sensing> //always returns false

TurtleLegos

bump

SmartCat3

No support.
This would prevent people from using a project.

Zelfen

TOLORS wrote:
1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.
(number of [loves v] :: sensing)

this falls into the same category, so it's rejected (kind of)

SuperMarioHome

Hmmm… This would work for some projects:

when green flag clicked
if <New Scratcher? :: sensing> then
    say [You must be a Scratcher to use cloud variables.]
else
   . . .
end

But bad for others:

when green flag clicked
if <Scratcher? :: sensing> then
    say [You suck.] // I don't believe that. Nah.
else
    say [Hello!]
end

Last edited by SuperMarioHome (Oct. 24, 2021 20:48:53)

TurtleLegos

Zelfen wrote:
TOLORS wrote:
1.5 Social action reporter blocks
This block could be used to obtain the current number of loves, favorites, or views of the project. Similar blocks could return the number of loves or followers that the user or creator has. But, project creators can easily use these blocks to prevent Scratchers from playing unless the project is given enough loves, favorites, and the like. These blocks could also make people think that getting these social actions are important, or that Scratch is about fame. In reality, if a user presses the love button on a project, it should be because they enjoyed the project, not because they are trying to reach some sort of goal.

This suggestion extends to all social actions, including views, loves, favorites, remixes, comments, and followers.
(number of [loves v] :: sensing)
this falls into the same category, so it's rejected (kind of)

Reported to be closed

dave-alt-4

ExtremeLogic wrote:
No support. This use would be abused and a lot of people with no hearts would just limit their projects to a specific rank, which wouldn't be fair.

I support , if they do that , you could just report and/or click see inside and remove that block :>

Jbear_

No support, people shouldn’t have something different happen depending on their rank

VedanshS933

Why do you need to detect if they are Scratcher?

User is [Scratcher v]? :: sensing boolean
User is [New Scratcher v]? :: sensing boolean

So you can do this?

if <User is [New Scratcher v]? :: sensing boolean> then 
broadcast [User Blocked//New Scratcher v]
say [You are New Scratcher, you can't access this project] for (2) secs
stop [all v]
else
broadcast [User Allowed//Scratcher v]
hide
end

or will they be reporters?

User Status? :: reporter sensing

For this, currently, No Support.
Please consider these Cons.

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

Scratch On!

Last edited by VedanshS933 (Feb. 17, 2022 08:53:33)

k0d3rrr

No support, as the reasons are given above.
And I can see why there wouldn't be a Scratch Team option, because someone might do this:

when green flag clicked
if <user is [Scratch Team v]:: sensing> then
…
else
say [Sorry, non-Scratch Team members aren't allowed] for [2] secs
end

coder2045

ExtremeLogic wrote:
No support. This use would be abused and a lot of people with no hearts would just limit their projects to a specific rank, which wouldn't be fair.

Every cloud variable project is restricted to Scratchers. Also, with your reasoning, basically every boolean block in Scratch should be removed because you can use them to bully people.

lapisi

k0d3rrr wrote:
(#78)
No support, as the reasons are given above.
And I can see why there wouldn't be a Scratch Team option, because someone might do this:
when green flag clicked
if <user is [Scratch Team v]:: sensing> then
…
else
say [Sorry, non-Scratch Team members aren't allowed] for [2] secs
end

or this:

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

VedanshS933 wrote:
(#77)
Why do you need to detect if they are Scratcher?

to detect if they can use cloud variables

~snip~
For this, currently, No Support.
Please consider these Cons.

1. New Scratchers/Scratchers can be blocked

but there really isn't any negativity towards New Scratchers or Scratchers, and it can easily be bypassed with see inside, perhaps a warning could be given before the project starts similar to the

(username)

block, and perhaps an option for the user to disable it could be present next to the project

2. There is currently not ST reporting

because it can only be used to get around moderation and can't be used for anything useful

3. Scratchers might get confused

explain how?

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

once again, it is extremely unlikely that it would be used like that, see above for more information

Scratch On!

that concludes this post

Scratch On!

Discuss Scratch