(an accidental post)

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.

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.

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.

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!

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.

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.

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

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.

You're taking about in the forums right? Cause I reveal the name of my next project sometimes if I want to by liking and faving it cause scratch is buggy and you can see the project that way without sharing it.

YellowCodes wrote:

You're taking about in the forums right?

Yes, specifically in the Advanced Topics.

Hello. I'm sorry that this is not a question/suggestion about the topic, but i see people that are not ST members/helpers (like you) just post explanations on the discussions, but did you just write this and hope it doesn't get deleted or what? Or did ST choose to do this?

Deelapie wrote:

Hello. I'm sorry that this is not a question/suggestion about the topic, but i see people that are not ST members/helpers (like you) just post explanations on the discussions, but did you just write this and hope it doesn't get deleted or what? Or did ST choose to do this?

the original poster got permission from the scratch team to make this, which is why it's a sticky

This is a really important point for the Advanced Topics. It’s easy to get caught up in the ‘hype’ of a new Scratch Mod or a complex API tool, but without a Proof of Concept (PoC), it’s just an idea, not a technical discussion.

To add to this, if you are a developer who is excited about an idea but hasn't finished it yet:

Use a Design Document: Instead of posting a thread, write down your logic in a private notes app. How will the Cloud Lists actually handle the data? What server-side language will you use?

Wait for the ‘Alpha’: Only post once you have a GitHub repo or a shared Scratch project that demonstrates at least one of your core features working.

Ask Specific Questions: If you don't know how to make a feature (like the profile picture example), don't announce a whole mod. Instead, make a topic asking: ‘How can I use the Scratch API to fetch user assets?’ Quality over hype makes the ATs a much better place for everyone. Thanks for putting this guide together!

DanDanbingobam wrote:

(#114)
This is a really important point for the Advanced Topics. It’s easy to get caught up in the ‘hype’ of a new Scratch Mod or a complex API tool, but without a Proof of Concept (PoC), it’s just an idea, not a technical discussion.

To add to this, if you are a developer who is excited about an idea but hasn't finished it yet:

Use a Design Document: Instead of posting a thread, write down your logic in a private notes app. How will the Cloud Lists actually handle the data? What server-side language will you use?

Wait for the ‘Alpha’: Only post once you have a GitHub repo or a shared Scratch project that demonstrates at least one of your core features working.

Ask Specific Questions: If you don't know how to make a feature (like the profile picture example), don't announce a whole mod. Instead, make a topic asking: ‘How can I use the Scratch API to fetch user assets?’ Quality over hype makes the ATs a much better place for everyone. Thanks for putting this guide together!

This is AI, isn't it… and the profile picture too….

Yeah I'd keep my projects private until they are publicly released.

What about, say, a project that is released, and the core functionality is finished, but may receive new updates (like content updates, bug fixes, ect.)?

DogLover8425 wrote:

What about, say, a project that is released, and the core functionality is finished, but may receive new updates (like content updates, bug fixes, ect.)?

That's fine – you just need to show something that works. This sticky was made because some people announced projects that they hadn't even started working on with a long list of features and a completely unrealistic release date.

Maximouse wrote:

(#118)

DogLover8425 wrote:

What about, say, a project that is released, and the core functionality is finished, but may receive new updates (like content updates, bug fixes, ect.)?

That's fine – you just need to show something that works. This sticky was made because some people announced projects that they hadn't even started working on with a long list of features and a completely unrealistic release date.

There's still a problem with people pulling up with a link to this on projects that DO already exist…. I got this slapped on mine even though I literally gave the link and all so there's gotta be like a rule to not abuse this/??