Hello everyone! I have a suggestion for a block. It's called the creator boolean. This boolean will tell you the creator of this project. It will be mainly used to see if you are the creator or not, and if you are an event will happen.

(creator of this project)

when green flag clicked
forever
say [Don't Spam!]
end

creator of this project ? :: sensing boolean

What happens when someone remixes a project?

Why can't you just use

<(username) = [INSERT CREATOR OF PROJECT HERE]>

mlcreater wrote:

creator of this project ? :: sensing boolean

What happens when someone remixes a project?

It changes to the person who remixed the project.

when green flag clicked
forever
say [Don't Spam!]
end

Super_Scratch_Bros20 wrote:

Why can't you just use

<(username) = [INSERT CREATOR OF PROJECT HERE]>

I think that is a better option.

That way prevents people from hitting Remix-Share without making changes or breaking the project.


<edit desc=“reworded for clarity” my-time=“2020 Jul 11 21:43” />

How would this benefit Scratch? You could just do this

<(username) = [INSEERT USERNAME HERE]> // hey, when you remix put your username here

Basic88 wrote:

How would this benefit Scratch? You could just do this

<(username) = [INSEERT USERNAME HERE]> // hey, when you remix put your username here

Actually, I do not think this would benefit scratch.

If this block is added, it could be used to prevent remixes, as in:

when @greenFlag clicked
nNJMDifmhN :: custom stack
if <(nNJMDifmhN) = [mHJkSr5]> then
make the project not work :: grey stack
end

define nNJMDifmhN
if <<creator of this project? :: sensing boolean> and <not <(username) = [mlcreater]>>> then {
set [nNJMDifmhN v] to [mHJkSr5]
} :: control stack

<edit desc=“added space to separate my signature from the script” my-time=“2020 Jul 12 14:14” />

I don't see what this would solve.
On a side note:

mlcreater wrote:

Basic88 wrote:

How would this benefit Scratch? You could just do this

<(username) = [INSEERT USERNAME HERE]> // hey, when you remix put your username here

-snip-

Actually, I do not think this would benefit scratch.

If this block is added, it could be used to prevent remixes,

Couldn't they just change that when they remix?

This would make it easier for users to restrict content access, which is a reportable offense. Sorry, but this would make it too easy to break the guidelines.

qrcool wrote:

This would make it easier for users to restrict content access, which is a reportable offense. Sorry, but this would make it too easy to break the guidelines.

How would it? The block detects if you're the creator, it doesn't block you from using the project. If you encounter a project that doesn't let you play unless your username is a determined one, you can see inside and tamper with the scripts until you manage to bypass this block or you can report the project if there are bigger problems.

The creator of the project id th only one who can edit it and make changes. Therefore if the creator wanted this block they could just replace it with their username. Besides, how would this be used?

--Explosion-- wrote:

Besides, how would this be used?

I was thinking of using it for debug purposes.

Don't understand. Why does it have to be a boolean instead of a reporter?

Botcho_Otkho wrote:

--Explosion-- wrote:

Besides, how would this be used?

I was thinking of using it for debug purposes.

Or to create special events, for example if you have a platformer and it is winter time you can control to turn snow off or on.

when green flag clicked
forever
say [Don't Spam!]
end

Hey there! Please correct me if I'm wrong, but your idea seems to be a duplicate. Here's the oldest topic I found about this idea:

• Project Owner/Original Creator Blocks (posted Sept. 25, 2013 04:23:13)
  

bigpuppy wrote:

Hey there! Please correct me if I'm wrong, but your idea seems to be a duplicate. Here's the oldest topic I found about this idea:

• Project Owner/Original Creator Blocks (posted Sept. 25, 2013 04:23:13)
  

Thanks for the link! It does look like this is a duplicate topic so I'll close it to keep the conversation all in one place.

Please use the existing topic in the link above.