Discuss Scratch

scratchyone
Scratcher
100+ posts

Ban Hacked Blocks

braxbroscratcher wrote:

MathlyCat wrote:

braxbroscratcher wrote:

Sheep_maker wrote:

Hacked blocks like the red square with the two dashed lines shouldn't be allowed, but blocks that are hacked into inputs where they aren't supposed to be in (i.e.
set (var) to (0)
) should be allowed. Also, extension scripts aren't technically hacked (though they show up as “undefined” when it is not installed but Scratch already prevents you from sharing projects with extension scripts), so I think they're OK.

Support for allowing reporters to be put into all dropdowns and boolean inputs.
Not true. Put extension blocks in an already-shared project. It works.

Now then, think. Using the above block, if (var) wasn't the name of an already-made variable, it would create a variable, again, being dishonest by lying to users.
Wait how is it lying?

I'm with Sheep_Maker now
See above. It hides a list, variable, or other thing. It's like hiding something from the police. It's lying by omission.
By that logic,
hide variable [ v]
should be banned too.
Oh wow that post was quite a while ago

Last edited by scratchyone (April 19, 2016 07:53:27)

braxbroscratcher
Scratcher
1000+ posts

Ban Hacked Blocks

scratchyone wrote:

braxbroscratcher wrote:

MathlyCat wrote:

braxbroscratcher wrote:

Sheep_maker wrote:

Hacked blocks like the red square with the two dashed lines shouldn't be allowed, but blocks that are hacked into inputs where they aren't supposed to be in (i.e.
set (var) to (0)
) should be allowed. Also, extension scripts aren't technically hacked (though they show up as “undefined” when it is not installed but Scratch already prevents you from sharing projects with extension scripts), so I think they're OK.

Support for allowing reporters to be put into all dropdowns and boolean inputs.
Not true. Put extension blocks in an already-shared project. It works.

Now then, think. Using the above block, if (var) wasn't the name of an already-made variable, it would create a variable, again, being dishonest by lying to users.
Wait how is it lying?

I'm with Sheep_Maker now
See above. It hides a list, variable, or other thing. It's like hiding something from the police. It's lying by omission.
By that logic,
hide variable [ v]
should be banned too.
Oh wow that post was quite a while ago
No, because the variable still exists in the project without running it. Show and hide are fine, because the variable isn't created or deleted, but being able to create variables is bad.

Powered by DjangoBB