Part 4 of my earlier list of suggestions

4: Update Log
Oh my goodness, an Update Log would be so helpful to many more seasoned Scratchers. Instead of silently placing small features into the existing Scratch 3.0, there can be an update log displaying major updates, new features, and different patches.
This is for Scratch as a whole (Scratch 1.0, 2.0, 3.0), not just in individual projects.

The Unofficial Scratch Update Log
You can say that the one above it good enough, but with the ST controlling it, they can put out patches and silent updates that the community won’t know otherwise.

Can't you already do this with comments inside the project or in the description of the project?

musicROCKS013 wrote:

Can't you already do this with comments inside the project or in the description of the project?

I’m talking about the Scratch Team having an Update Log for Scratch as a whole.
If they already have one, then please, show me.

I'm pretty sure this already exists on the Scratch Wiki. It's not run by the Scratch Team though.

I'm fairly certain that you can find the meaningful updates in the announcements forum as well.

If you're tech savvy enough, you might be able to understand the changes on the Scratch Team's GitHub organization. There's a link to it here.

jackson49 wrote:

I'm pretty sure this already exists on the Scratch Wiki. It's not run by the Scratch Team though.

Ok, ok good to know, but these are just bigger changes, and the community only know what the ST tells them. If there’s an official Scratch Update Log, then there can be smaller things, like patches, and silent updates (except they won’t be silent with the update log).

AGamer_S wrote:

jackson49 wrote:

I'm pretty sure this already exists on the Scratch Wiki. It's not run by the Scratch Team though.

Ok, ok good to know, but these are just bigger changes, and the community only know what the ST tells them. If there’s an official Scratch Update Log, then there can be smaller things, like patches, and silent updates (except they won’t be silent with the update log).

ScolderCreations wrote:

If you're tech savvy enough, you might be able to understand the changes on the Scratch Team's GitHub organization. There's a link to it here.

My link above shows every change there is. Usually, you're going to want to pay attention to “releases”, which usually have patch notes for pretty much everything. I don't know if they do releases there, but if they do it'll help you a lot. Never mind, they don't have releases. Instead, you should pay attention to Pull Requests, which are people requesting changes to be added. There you can see future features that will be added potentially, and when they are “merged”, that means they are features that have been accepted and are going to be in Scratch.

AGamer_S wrote:

Part 4 of my earlier list of suggestions

4: Update Log
Oh my goodness, an Update Log would be so helpful to many more seasoned Scratchers. Instead of silently placing small features into the existing Scratch 3.0, there can be an update log displaying major updates, new features, and different patches.
This is for Scratch as a whole (Scratch 1.0, 2.0, 3.0), not just in individual projects.

The Unofficial Scratch Update Log
You can say that the one above it good enough, but with the ST controlling it, they can put out patches and silent updates that the community won’t know otherwise.

I support

Don't just say you support without providing a reason, all it does is clutter up the forum topic without actually providing any reason for the ST to implement the suggestion. Speaking of the suggestion, to the original poster, did you ever read my post showing off a helpful workaround? It's probably what I'd recommend people use, as it is the definitive way to see what's going on with the scratch website, aside from secret server stuff, but that would only change stuff like the API and storage.

AGamer_S wrote:

jfmpatrick wrote:

They should put the enter key in the key pressed blocks.

when green flag clicked
forever
if <key [enter] pressed?> then
do something cool
end
end

I have come up with a way to make sprites activate witht the enter key. It's this: see it in action here: https://scratch.mit.edu/projects/714005473

when green flag clicked
set [enter] to [enter]
forever
if <key (enter) pressed?> then
do something cool
end

That’s a nice workaround for that problem. Although, can you please reply in the correct thread? Your solution is unrelated to the suggestion at the top, so can you please go reply to the correct thread?

I wasn't replying to anyone. I was making a new subject.

jfmpatrick wrote:

AGamer_S wrote:

jfmpatrick wrote:

They should put the enter key in the key pressed blocks.

when green flag clicked
forever
if <key [enter] pressed?> then
do something cool
end
end

I have come up with a way to make sprites activate witht the enter key. It's this: see it in action here: https://scratch.mit.edu/projects/714005473

when green flag clicked
set [enter] to [enter]
forever
if <key (enter) pressed?> then
do something cool
end

That’s a nice workaround for that problem. Although, can you please reply in the correct thread? Your solution is unrelated to the suggestion at the top, so can you please go reply to the correct thread?

I wasn't replying to anyone. I was making a new subject.

Either way, please don't post anything unrelated on this thread.