Please don't announce projects before you release them.

gilbert_given_189

(an accidental post)

Last edited by gilbert_given_189 (April 28, 2025 14:15:12)

gilbert_given_189

Since I accidentally \clearpage'd this topic, I'd like to bump this post that got wiped from it.

PokeDinoChu77 wrote:
I mean, it's still nice to make trailers, teasers, and demos for your upcoming projects. You probably don't have a definite release date, but you could at least show a piece of the future project. Even if people don't really check them out, it's still fun to build up hype! Plus, it's nice practice for if you work for a company and you can only share sneak peaks of upcoming projects for now.

This was supposed to be an essay on why this isn't generally a good idea. But now that I think about it, announcing a pre-release project could work, if these conditions are met:

There must be some evidence that the project is in development. Either by screenshots or videos or a link to the source code or something else, people should know that the project exists, and that it has progressed.
Be as open as possible. Tell the people what you did & will do about the project. It could be about an upcoming change on your project. Or it could be about taking a break, slowing down development, or even ending the project.
This also applies to released projects as well.

Put it simply, making devlogs could work.

Last edited by gilbert_given_189 (April 30, 2025 01:50:44)

JBlueBird

gilbert_given_189 wrote:
Since I accidentally \clearpage'd this topic, I'd like to bump this post that got wiped from it.

PokeDinoChu77 wrote:
I mean, it's still nice to make trailers, teasers, and demos for your upcoming projects. You probably don't have a definite release date, but you could at least show a piece of the future project. Even if people don't really check them out, it's still fun to build up hype! Plus, it's nice practice for if you work for a company and you can only share sneak peaks of upcoming projects for now.
This was supposed to be an essay on why this isn't generally a good idea. But now that I think about it, announcing a pre-release project could work, if these conditions are met:
There must be some evidence that the project is in development. Either by screenshots or videos or a link to the source code or something else, people should know that the project exists, and that it has progressed.
Be as open as possible. Tell the people what you did & will do about the project. It could be about an upcoming change on your project. Or it could be about taking a break, slowing down development, or even ending the project.
This also applies to released projects as well.
tl;dr: making devlogs could work.

Yeah, devlogs are pretty perfect for that matter.

SidewaysCoder

Paddle2See wrote:
After a number of mods were announced that turned out to be imaginary - we have been asking folks to show some proof of their mods if they are announced here.

Would this be useful to add to the post? It's from a moderator, so it should add credibility to this sticky.

ultrabomb205

A forum siggy is the text that is below the grey line.

Redstone1080 wrote:
You should add that if you're itching to create a topic, at least get a prototype done. That's what I did with Snazzle lol

How did you get the forum siggy? I want it on my posts!

Maximouse

ultrabomb205 wrote:
How did you get the forum siggy? I want it on my posts!

Go to the forum home page (Discussion Home) and scroll to the bottom – there's a link to change your signature.

Xavi2314

scratch :: events :: hat
imagine :: sensing
program :: control
share :: extension

The scratch block starts the scratch era
the imagine block makes you imagine
the program block programs everything
and the share block is from a custom extension where it interacts with the whole project except the code.

AlexDF16

You can announce a project when it is about 3/4 done. That is how some people do it.

Like I am making this game and it has a cat and its pixelated, way better than it's predecessor, but is 1/8 done. So I can't for another 5/8 of the game.

when green flag clicked
if <not shared> then 
say [do not show it off] for (2) secs
play sound [fart v]
else
say [we can share it!] for (2) secs
play sound [yay!!!! v]
end

scratchcode1_2_3

gilbert_given_189 wrote:
Since I accidentally \clearpage'd this topic, I'd like to bump this post that got wiped from it.

PokeDinoChu77 wrote:
I mean, it's still nice to make trailers, teasers, and demos for your upcoming projects. You probably don't have a definite release date, but you could at least show a piece of the future project. Even if people don't really check them out, it's still fun to build up hype! Plus, it's nice practice for if you work for a company and you can only share sneak peaks of upcoming projects for now.
This was supposed to be an essay on why this isn't generally a good idea. But now that I think about it, announcing a pre-release project could work, if these conditions are met:
There must be some evidence that the project is in development. Either by screenshots or videos or a link to the source code or something else, people should know that the project exists, and that it has progressed.
Be as open as possible. Tell the people what you did & will do about the project. It could be about an upcoming change on your project. Or it could be about taking a break, slowing down development, or even ending the project.
This also applies to released projects as well.
Put it simply, making devlogs could work.

This is what I think is better. I got this link crammed into my topic of my Scratch mod, and it was kind of annoying because I had been waiting for enough time for the mod to actually be released as a live site and have plenty of changes before making topic about it… yet…. the link was still plastered on my topic. I understand people are just trying to help, but it kinda made me feel sad.

Discuss Scratch