This would significantly reduce server storage.
Blocks are stored as a separate .txt file called scratchblocks-[project ID].txt.
Costumes and backdrops are stored as a separate .txt file called vecbit-[project ID].txt.
Sprites and the stage are stored as a separate .txt file called sprstg-[project ID].txt.
Sounds, however, are the only ones not stored as a .txt file.

a json actually holds code though, a .txt does not, no support

No support
This is a coding website, not a word document. JSON can actually save code wheras .txt contains unformatted text and is good for Read Me's but not good for storing coding data

I mean, the txt will be processed by the TXT processor to turn it into code.

0_009 wrote:

This would significantly reduce server storage.
Blocks are stored as a separate .txt file called scratchblocks-[project ID].txt.
Costumes and backdrops are stored as a separate .txt file called vecbit-[project ID].txt.
Sprites and the stage are stored as a separate .txt file called sprstg-[project ID].txt.
Sounds, however, are the only ones not stored as a .txt file.

Idk if I support this or not, but I really like your idea. .txt files are significantly less bytes.

0_009 wrote:

I mean, the txt will be processed by the TXT processor to turn it into code.

yeah but it's easy to just use a json
(also convertors never really work to well)

0_009 wrote:

Costumes and backdrops are stored as a separate .txt file called vecbit-[project ID].txt.

How are you going to store images in a text file? What's wrong with the current asset system?

I don't see how storing the blocks in a text file would improve things. JSON is just a convenient format for storing data in a text file. Switching to a custom format would be challenging and be somewhat pointless.

0_009 wrote:

I mean, the txt will be processed by the TXT processor to turn it into code.

Yeah, I think this would actually cause more problems than it would actually fix..

svg and json are both text files already

since zip compression is applied to the sb3, any non-lossy changes to the parts of a Scratch project are unlikely to reduce server storage significantly

TimothyLawyer wrote:

svg and json are both text files already

since zip compression is applied to the sb3, any non-lossy changes to the parts of a Scratch project are unlikely to reduce server storage significantly

Right.