Community made Custom blocks

AonymousGuy

NolanAwesome wrote:
Ummm, that's not at all what I said. Do you even remember what we are talking about?

Yes, I know what we're talking about. But it's the same thing overall.

“Your work is so useless that we're taking it down!”

NolanAwesome

AonymousGuy wrote:
NolanAwesome wrote:
Ummm, that's not at all what I said. Do you even remember what we are talking about?
Yes, I know what we're talking about. But it's the same thing overall.

“Your work is so useless that we're taking it down!”

Well, whatever. Let's stop arguing.

Zro716

maybe custom blocks should get approval before they are added to the custom blocks library

Scrathygirl

100+ Support

I was thinking something similar expect people could add custom sprites (To be saved In Libary) Same thing with backdrops. And maybe diffrent tools in paint editors and etc .

miles854

Make a delete button so you can delete a block from the custom block tab or maybe make it so there is a delete button and a remove button. The delte button would delete the block and the remove button would remove the block from the custom block tab. Also there should be the option to edit your own block after it has been uploaded to the custom block tab.

miles854

Zro716 wrote:
maybe custom blocks should get approval before they are added to the custom blocks library

I don't support that idea because what if you had been working on a block for a while and wanted it to be uploaded immediately or you have taken a while to finsih a custom block request and didn't want your custom requesting the block to have to wait to see it. Also backpacking a block doesn't really work but there are ways to fix it once taken from the backpack and into the project you want to use it in.

Last edited by miles854 (Sept. 14, 2014 23:26:32)

Fireflew

Azurite wrote:
Chibi-Matoran wrote:
What if someone took the defining script off of the define block of a shared custom block, then used it to make another custom block and took credit?
Well that's their problem. Nothing can be perfect.

As you said, there can be a report button, or you cannot submit duplicates. :-\ Or maybe the code itself can identify with the other user and won't let you share it.

miles854 wrote:
Zro716 wrote:
maybe custom blocks should get approval before they are added to the custom blocks library
I don't support that idea because what if you had been working on a block for a while and wanted it to be uploaded immediately or you have taken a while to finsih a custom block request and didn't want your custom requesting the block to have to wait to see it. Also backpacking a block doesn't really work but there are ways to fix it once taken from the backpack and into the project you want to use it in.

Well, maybe it can go into a huge folder, full of not-yet approved blocks, and people can still view and use them, but there will be some icon on the script or something like that that says it is not yet approved.

BTW, support.

Last edited by Fireflew (April 26, 2016 12:34:42)

AwesomePerson238243

how about a limit to how many blocks you can have in the define script, for example only 10 blocks and up. this would eliminate

define moo
say [moo]

but would cause things like

define move 250 steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps
move (10) steps

this could go either way

TheScratchHobbiest

support

Abstract-

Tildo wrote:
Azurite wrote:
Chibi-Matoran wrote:
What if someone took the defining script off of the define block of a shared custom block, then used it to make another custom block and took credit?
Well that's their problem. Nothing can be perfect.

As you said, there can be a report button, or you cannot submit duplicates. :-\ Or maybe the code itself can identify with the other user and won't let you share it.

miles854 wrote:
Zro716 wrote:
maybe custom blocks should get approval before they are added to the custom blocks library
I don't support that idea because what if you had been working on a block for a while and wanted it to be uploaded immediately or you have taken a while to finsih a custom block request and didn't want your custom requesting the block to have to wait to see it. Also backpacking a block doesn't really work but there are ways to fix it once taken from the backpack and into the project you want to use it in.

Well, maybe it can go into a huge folder, full of not-yet approved blocks, and people can still view and use them, but there will be some icon on the script or something like that that says it is not yet approved.

BTW, support.

Discuss Scratch