New sensing boolean block [Scratcher rank]

gigapouch

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.

Last edited by Paddle2See (March 22, 2016 12:23:56)

ExtremeLogic

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.

spgame05

Support!

There is a report button for mean projects.

gigapouch

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 an extreme.

AonymousGuy

Why would there need to be one for Scratch Team?

That doesn't really make sense to me… It seems like the only use would be giving them extra stuff and features, which is kinda unfair…

gigapouch

AonymousGuy wrote:
Why would there need to be one for Scratch Team?

That doesn't really make sense to me… It seems like the only use would be giving them extra stuff and features, which is kinda unfair…

Not exactly. For New Scratchers or guests, it would be useful to use the block to run the program in non-cloud variable mode. I don't know about the Scratch Team.

AonymousGuy

gigapouch wrote:
AonymousGuy wrote:
Why would there need to be one for Scratch Team?

That doesn't really make sense to me… It seems like the only use would be giving them extra stuff and features, which is kinda unfair…

Not exactly. For New Scratchers or guests, it would be useful to use the block to run the program in non-cloud variable mode. I don't know about the Scratch Team.

I was talking about the Scratch Team one, not the other ones.

gigapouch

AonymousGuy wrote:
gigapouch wrote:
AonymousGuy wrote:
Why would there need to be one for Scratch Team?

That doesn't really make sense to me… It seems like the only use would be giving them extra stuff and features, which is kinda unfair…

Not exactly. For New Scratchers or guests, it would be useful to use the block to run the program in non-cloud variable mode. I don't know about the Scratch Team.
I was talking about the Scratch Team one, not the other ones.

OK. I'll delete that one.

TheLogFather

To detect Scratcher vs New Scratcher, see project in my sig.
(EDIT: sorry, see post below…)

Last edited by TheLogFather (April 21, 2014 09:06:56)

DadOfMrLog

Oh, oops - wrong account!

See project in *this* sig…

derpmeup

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.

chooper100

If the purpose of this is to detect whether cloud data is active or not, wouldn't we just have a block like this?

<is cloud available?> // category=sensing

Although this can be used to detect new scratchers, it is less likely to be used for that purpose.

I don't think I'd support the original ‘is user new scratcher?’ block though.

Last edited by chooper100 (April 22, 2014 11:40:35)

gigapouch

chooper100 wrote:
If the purpose of this is to detect whether cloud data is active or not, wouldn't we just have a block like this?
<is cloud available?> // category=sensing
Although this can be used to detect new scratchers, it is less likely to be used for that purpose.

I don't think I'd support the original ‘is user new scratcher?’ block though.

That's a good idea.

6littleman

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

Anthan

chooper100 wrote:
If the purpose of this is to detect whether cloud data is active or not, wouldn't we just have a block like this?
<is cloud available?> // category=sensing
Although this can be used to detect new scratchers, it is less likely to be used for that purpose.

I don't think I'd support the original ‘is user new scratcher?’ block though.

I absolutely agree. I think part of the point (correct me if I'm wrong) would be to detect whether or not the user can use cloud data, so they can quickly detect whether or not cloud is usable and just omit cloud features if not.

Paddle2See

Note (for reference) that the conversation has, at times, branched out to other topics, as noted in this copy of a post from this topic

TheLogFather wrote:
This has been suggested numerous times – here are some examples:
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/36295/
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/42497/
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/90260/
https://scratch-mit-edu.ezproxyberklee.flo.org/discuss/topic/182401/

It's worth reading through the above discussions about it (in particular, why the more sensible thing to detect is cloud connection, since that's what really matters to a project…)

mrbobbygreathead wrote:
No support, easy workaround.
@mrbobbygreathead: Maybe you know this already – but for the benefit of others reading this…
The ‘workaround’ is not at all obvious (even though it does end up being simple). Most of the ways that people think up for detecting this using cloud variables will not work (because they don't really understand how cloudvars behave…)

AFAIA, this New Scratcher Detector project is the only possible way to do it (technically, it detects cloud connection status, and you can see that more clearly if you look at this cloud connection test project, which has no sprites and no scripts – doesn't even need running to see the result!)

If you see projects trying to detect New Scratcher a different way (e.g. by changing cloudvars, etc.), they are very unlikely to work.

mrbobbygreathead

No support because there is a workaround using cloud data.

pvz_pro

no support

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

Cub56

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.

braxbroscratcher

gigapouch 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 an extreme.

Scratch team can masquerade as Scratchers anyway… if I recall…

Discuss Scratch