мой медвежий мир wrote:

(#1)
Note: Please do read the topic first and make sure this actually applies before directing the OP of it here.

When you get an idea for a new project, you are probably very excited about it, and therefore want to create a topic about it to announce it. However, when you do this, you are likely to get backlashed, and your topic may even get closed.

Why?

Here is an example topic someone could create in the Advanced Topics.

SuperbSpectacularScratcher wrote:

Hello! I'll make a Scratch Mod called “Glitter”! It will have the following features:

([mybearworld]'s profile picture :: sensing)

(cloud list :: list)

I will make it tomorrow.

You can probably notice the central issue with this - the blocks are very difficult to create. Getting a Scratcher's profile picture wouldn't be hard, you could just use the API, but putting it into a Scratch project is. As the post does not go into any detail of how this would work, it's clear that this wasn't very well thought through. Cloud lists would imply that the person creating the mod has a server on which cloud variables can be stored, on which projects can also be shared, which is also done in a way that would allow advertising in Scratch. Without any further details, this would be impossible to create. Also, it is suggested that this would be made in one day, but has not been made yet. This is way too low of a timeframe.

Issues like these are pretty easily spotted by ATers, but they might not be for someone new to the ATs who is excited to share their project idea. However, this causes ATers to be pretty unhappy, as they might've actually been very excited for this project, only to realize that it does not exist yet and is also not thought through.

Therefore, it is recommended not to prematurely announce your project ideas to the world. Instead, try making the project - if it goes well, then you can make the topic. This also ensures that there is less clutter in the ATs, and only real, currently usable, programs.

(Good!::operators)

this is a fake operator block.
code:
(Good!:perators)

mybearworld wrote:

I added a note to the beginning because it is already getting sort of misused

DifferentDance8 wrote:

(#24)

mybearworld wrote:

I added a note to the beginning because it is already getting sort of misused

Wait how is it being misused? The only times I've seen this ever be linked are relevant.

DifferentDance8 wrote:

(#24)

mybearworld wrote:

I added a note to the beginning because it is already getting sort of misused

Wait how is it being misused? The only times I've seen this ever be linked are relevant.

mybearworld wrote:

(#26)

DifferentDance8 wrote:

(#24)

mybearworld wrote:

I added a note to the beginning because it is already getting sort of misused

Wait how is it being misused? The only times I've seen this ever be linked are relevant.

Ultiwrap, mostly - as I see it, they were asking how to make these blocks, and the main point wasn't announcing that they'll make a mod.

. . .::grey hat

mybearworld wrote:

SuperbSpectacularScratcher wrote:

Hello! I'll make a Scratch Mod called “Glitter”! It will have the following features:

([mybearworld]'s profile picture :: sensing)

(cloud list :: list)

I will make it tomorrow.

i_eat_coffee wrote:

(#30)
Is the new edit really needed?

i_eat_coffee wrote:

(#3)
That topic says that I should announce my projects after I make them, and this project is already made – just not released.

mybearworld wrote:

i_eat_coffee wrote:

(#30)
Is the new edit really needed?

Quoting you:

i_eat_coffee wrote:

(#3)
That topic says that I should announce my projects after I make them, and this project is already made – just not released.

mybearworld wrote:

The project is done, but you want to build up hype. The problem with this is that it's very hard to be sure that the project is actually done if you're viewing the topic. The user could actually not have started with their project at all, and just said it's done so they're not redirected to this topic.

i_eat_coffee wrote:

(#32)
I said that, but, why is the change needed?
Edit: It seems like you changed it just to make me unhappy. There's no need for such change.

mybearworld wrote:

This also ensures that there is less clutter in the ATs, and only real, currently usable, programs.

i_eat_coffee wrote:

(#33)

mybearworld wrote:

The project is done, but you want to build up hype. The problem with this is that it's very hard to be sure that the project is actually done if you're viewing the topic. The user could actually not have started with their project at all, and just said it's done so they're not redirected to this topic.

Okay, how about if the user shares proof (screenshots, screen recordings, etc.) of the project?

mybearworld wrote:

i_eat_coffee wrote:

(#32)
I said that, but, why is the change needed?
Edit: It seems like you changed it just to make me unhappy. There's no need for such change.

I changed it to clarify. This was my intent when making this topic, and you can tell this by looking at the final sentence (before the new part):

mybearworld wrote:

This also ensures that there is less clutter in the ATs, and only real, currently usable, programs.

mybearworld wrote:

i_eat_coffee wrote:

(#33)

mybearworld wrote:

The project is done, but you want to build up hype. The problem with this is that it's very hard to be sure that the project is actually done if you're viewing the topic. The user could actually not have started with their project at all, and just said it's done so they're not redirected to this topic.

Okay, how about if the user shares proof (screenshots, screen recordings, etc.) of the project?

If the project is in a state where this is possible without issues, then artificially delaying its release can just be annoying as it is completely unnecessary.

i_eat_coffee wrote:

(#37)
That's called creating hype, and it should be allowed since the creator might have worked really hard for the project and wants other users to be excited when using it for the first time.

mybearworld wrote:

i_eat_coffee wrote:

(#37)
That's called creating hype, and it should be allowed since the creator might have worked really hard for the project and wants other users to be excited when using it for the first time.

Wouldn't you be more excited if you saw what the mod can do with a “Try it now” link so you can actually try it for yourself?

i_eat_coffee wrote:

(#39)
No. Creating hype would make people more excited since they've been waiting for a long time.