Raise it. I need it to be raised. My big project with 14000+ code cannot be completed. Just make it 6Mb instead of 5, thats all I ask!

Crashing Scratch be like: they made the limit for a reason

I was expecting this to be rejected but surprisingly I don't think it is. Also I'm pretty sure that the size limit was implemented for a reason (though then again, seeing as comments are 500 characters but the About Me and What I'm Working On sections are only 200, maybe I shouldn't trust Scratch Team's judgement of how to properly allocate space )

The scratch team have to pay for all the storage. No support.

No support.
Atleast you can make the project in a version of Scratch and upload the project in the desktop, that doesn't help.
The ST has to pay for the storage, disk space, and more. Just opening the limit 1 MB can overload it, and we wouldn't be able to save projects anymore.
You can make your project in Scratch Desktop and share it with other friends who also have Scratch Desktop installed. I don't know if Scratch Desktop has a limit, however.

secretagent123 wrote:

The scratch team have to pay for all the storage. No support.

I don't think increasing project.json limit is really a problem in that regard.

First of all, assets are limited to 10Mb and you can have a lot of them in a single project. Increasing project.json from 5Mb isn't going to change much.

Secondly, when someone draws a costume, saves the project, then decides to partially modify it, does that, saves the project again, then old version of that costume still remains on the server and is never removed. That is a huge problem in terms of storage space, but ST doesn't care.

Thirdly, when you put project in trash and then empty trash, project is not deleted, it is just hidden. People can still view it using Scratch-GUI,Forkphorus or Turbowarp. It remeins in hidden state forever. I know that it's done to prevent people from sharing inapropriate things and then deleting them, but deleted projects are never deleted, even after multiple years, even project that were never shared(projects that I deleted in 2017 are still there). Once again ST doesn't seem to care about this thing that consumes so much storage space.

I doubt that doubling project.json limit is going to affect their costs by any visible amount. Considering that, problems 1-3 exist, which can be fixed and which currently consume A LOT more storage space than this suggestion, but scratch developers simply don't care, storage isn't going to be an issue.


Less that a day ago I ran into a project.json limit in my most recently shared project which has 22941 blocks(most space is taken by scripts).
And about half a year ago I also stopped developing doom recreation because of this reason(most space was taken by lists)

Support. Few projects exceed the JSON limit, but it can be a serious problem for advanced projects. I think 10 MB wouldn't be too much.

What a concidence , I just passed JSON limit, now I have to optimize every part of the script maximally possible

Anyways , I posted a suggestion for adding Textual assets , because a level in my game occupy 15000 bytes of data (I plan 16 levels , so it 5% of total JSON) , and one .obj file I import is occuping about 4000 bytes of data (I plan 300 , so it's about 20% of my JSON), with text assets , all levels, and object data would be counted as asset memory.

Possible solutions:

Only workaround I currently have is to convert all repeating parts into custom blocks…

Also be sure that you delete all data from your lists, and variables, and then show and then unshow them
that's because the graphics part is saved in JSON even if the lists are empty, you have to clear the graphical part.
Also if your lists are generated in start, you can make broadcast which will empty all your lists, and then everytime you want to save , call the broadcast, I know that's pretty annoying that you need to call a broadcast everytime you want to save, but it's currently the only way.

Maximouse wrote:

Support. Few projects exceed the JSON limit, but it can be a serious problem for advanced projects. I think 10 MB wouldn't be too much.

Ok. Pay for all of that

lordibel wrote:

Maximouse wrote:

Support. Few projects exceed the JSON limit, but it can be a serious problem for advanced projects. I think 10 MB wouldn't be too much.

Ok. Pay for all of that

No, I think they're right. As ggenije points out, images and sound can far exceed the amount of space that the JSON can take up without reaching the limit. I don't think that increasing the limit a little bit would kill them.