(I checked for dupes, didn’t find one. If there is one, please correct me. Also, this is a little different from giving the JSON size. The JSON also holds pre-determined amounts for variables and lists.)
(Note that TurboWarp isn’t a browser extension, nor are TurboWarp Addons/nm
Also, adding onto that, there are browser extensions for it, but please don’t mention them due to the policy. Nothing has has been said about browser extensions in terms of names, but I’m sure that workaround will be suggested instead)
(Before you say to right click, look in https://scratch-mit-edu.ezproxyberklee.flo.org/projects/10128407/ and use that method)
Have you ever been working on a project, than wondered how many blocks your have? Not just in 1 sprite, rather, in the whole projects?

Perhaps you’ve wanted to see if a project getting some optimizations wsoukld be fruitful. Now, you could use Turbowarp, however, with the upcoming update, you may not have that as an option without sharing it, potentially up to an hour. While you could unshare it, that could spoil upcoming projects. All due to being curious of how useful minor optimizations would be. It could also be interesting to see how many blocks you have, even if it serves no real use past entertainment.

This suggestion is to add an option to the editor to see the exact block count. This is especially useful for larger projects with more sprites, given the limitations that would otherwise be held of adding 10+ block counts together. This could be toggled on and off by an option by the green flag and stop sign. It could be shown in the top right of the editor, as well.

Pros:
-Makes it easier to see how many blocks you have in a project
-Will work w/o sharing on TurboWarp
-Wouldn’t be to much coding, i imagine.
-Wouldn’t require browser extensions.
-Helps with larger projects(projects with more sprites)

Cons:
-Could be used for bragging, but the same could happen with many things, such as cloud variables. Besides, as stated in post 2, the less blocks the better

Edit: Fixed a typo and added more details

A certain browser extension actually has a feature that totals how many blocks you have in your project, so yes, it is definitely doable. However, I've had no real use for it other than people flexing on others about how many blocks they have. That shouldn't be a flex anyway, programming should be done with as few blocks as possible (and still be readable) to accomplish a task.

For now though, there is a workaround. You can click the empty space on where you place your scripts and see this.
It totals all the blocks inside that sprite. So in the image, the sprite has 648 blocks. That means, to get the amount of blocks in the project, you do that for every sprite and the backdrop, and then sum it up.

RL1123 wrote:

A certain browser extension actually has a feature that totals how many blocks you have in your project, so yes, it is definitely doable. However, I've had no real use for it other than people flexing on others about how many blocks they have. That shouldn't be a flex anyway, programming should be done with as few blocks as possible (and still be readable) to accomplish a task.

For now though, there is a workaround. You can click the empty space on where you place your scripts and see this.
It totals all the blocks inside that sprite. So in the image, the sprite has 648 blocks. That means, to get the amount of blocks in the project, you do that for every sprite and the backdrop, and then sum it up.

You do have great points here. However, there are a few things I do disagree with
With the flexing part, it could be helpful to decide if you need a workaround that you’re not sure will work, IE,

forever
if <key [1 v] pressed?> then 
  
else
Et cetra 
end
end

That’s something(generally proven to work, however, if it’s already a project with a lot of blocks, you may decide with this to condense it into this:

forever
if <key [(k3y) v] pressed?> then 
broadcast [(k3y) v]
else
set [K3y v] to (item ((index) v) of [list v] :: list)
change [Index  v] by (1)
if <(index) > (length of [list v] :: list)> then
set [Index v] to [1]
end
end
end

I may not be confident in that, and with less blocks keep it, but compress it for larger blocks scripts(I know there are a few flaws, just an example)
And, for the calculating, geo projects with more sprites, it could get annoying

25Freyst wrote:

With the flexing part, it could be helpful to decide if you need a workaround that you’re not sure will work, IE,
…
That’s something(generally proven to work, however, if it’s already a project with a lot of blocks, you may decide with this to condense it into this:
…
I may not be confident in that, and with less blocks keep it, but compress it for larger blocks scripts(I know there are a few flaws, just an example)

Yep, that's true for all programming. Simple code is better code. However, why does having a block counter help decide what workaround you're not sure about? That's why we debug, to fix issues with code that doesn't function right.

25Freyst wrote:

And, for the calculating, geo projects with more sprites, it could get annoying

I can't argue with that. It will take a long time to manually sum the number of blocks in 30 sprites.

RL1123 wrote:

25Freyst wrote:

With the flexing part, it could be helpful to decide if you need a workaround that you’re not sure will work, IE,
…
That’s something(generally proven to work, however, if it’s already a project with a lot of blocks, you may decide with this to condense it into this:
…
I may not be confident in that, and with less blocks keep it, but compress it for larger blocks scripts(I know there are a few flaws, just an example)

Yep, that's true for all programming. Simple code is better code. However, why does having a block counter help decide what workaround you're not sure about? That's why we debug, to fix issues with code that doesn't function right.

You may be more inclined to make more efficient code if i you already have a lot of code, otherwise, since it works, if you’re inexperienced with the work around, it could get pretty annoying.

RL113 wrote:

25Freyst wrote:

And, for the calculating, geo projects with more sprites, it could get annoying

I can't argue with that. It will take a long time to manually sum the number of blocks in 30 sprites.

The bane of mst users existence.
(Finally fixed, luckily)

Bump. Actually,
Whats the use of bumps? Bumps are over-used. Why? An old Scratch Tradition. But, i say, we stop them. I say we make a better bump. This topic hasn’t been bumped. It has been…
YEETed

No support, you can just right click its simple.

Roblox888i wrote:

No support, you can just right click its simple.

For one sprite, however, for larger projects, it could get tedious

25Freyst wrote:

Roblox888i wrote:

No support, you can just right click its simple.

For one sprite, however, for larger projects, it could get tedious

Yes. I have a project with over a 100 sprites, and the only way to see how many blocks there are it to use [[[[[the extension]]]], to do what @Roblox888i suggested, or to go to TimMcCool's scratch stats project, which is down most of the time and requires you to share your project.

Support.
This would have helped me realize that I made a project with 4,950+ blocks in it before TimMcCool made that project.

Inactive bump
Hold up. This is the Bump Revolution. Normalize something new! Something less used! Lets use…
Yeet!!

Bump, aka, yeet

Yeet(AKA, Bump)

bump? no.
Yeet? Yeah!!

No support.

Right click.
You can see how many blocks are in the sprite (next to delete).

If you accidentally click delete press CTRL-Z or CMD-Z

Easy-peasy, no need for the complicated dev process

Joyoforigami wrote:

Right click.
You can see how many blocks are in the sprite (next to delete).

Ever had a project with 100+ sprites and wanted to do this? This is not an effective workaround.

Joyoforigami wrote:

No support.

Right click.
You can see how many blocks are in the sprite (next to delete).

If you accidentally click delete press CTRL-Z or CMD-Z

Easy-peasy, no need for the complicated dev process

That’s easy, until you have a larger project. I might actually have one or two with over 20 sprites, and the challenge of counting them is harder than expected. TurboWarp is the only real workaround to this, however it also isn’t gonna work with unshared projects soon.

25Freyst wrote:

TurboWarp is the only real workaround to this, however it also isn’t gonna work with unshared projects soon.

(Sorry of offtopic) How do you see the total amount of blocks in a project through turbowarp? I’ve heard it was possible but never really found out how to do it.

25Freyst wrote:

musicROCKS013 wrote:

25Freyst wrote:

TurboWarp is the only real workaround to this, however it also isn’t gonna work with unshared projects soon.

(Sorry of offtopic) How do you see the total amount of blocks in a project through turbowarp? I’ve heard it was possible but never really found out how to do it.

Go to (removed), and look up counter. There’s a block counter feature(also turn on cat blocks if you didn’t already, not necessarily important for the counter, but important)

Please do not name browser extensions.

Tunde123 wrote:

25Freyst wrote:

musicROCKS013 wrote:

25Freyst wrote:

TurboWarp is the only real workaround to this, however it also isn’t gonna work with unshared projects soon.

(Sorry of offtopic) How do you see the total amount of blocks in a project through turbowarp? I’ve heard it was possible but never really found out how to do it.

Go to (removed), and look up counter. There’s a block counter feature(also turn on cat blocks if you didn’t already, not necessarily important for the counter, but important)

Please do not name browser extensions.

They mean the tab in Turbowarp that's called that.