DIAVLODUDE wrote:

I agree! FULL SUPPORT!

Please say why.

assuming there is 500 million projects in total and each one has full json file size then the total size is 5 x 500 million (2.5 billion). if they increased then limit to 6mb it would be 3 billion mb (again, assuming each 500 million projects are full). considering most projects dont even go past 100kb (500kb on 3.0?) so the result will be something like 24.5 TB.

conclusion: increasing size limit will effecttively do nothing

Myst-- wrote:

Support as long as this isn't widely used to try to crash scratch's servers.

i agree!

Support as long as this isn't widely used to try to crash scratch's servers.

yeah it would just be an extra 1024 kilobytes more. 1 megabit is less than a floppy disk!! thats should indeed be possible

Increase it to 8, and the asset limit to 16. Round numbers

Bump

I hope to see some acknowledgement by the scratch team about stuff like this, even if nothing is truly changed.

Support to the extreme, if they increase the project json that'll be something i find nifty, moist even

dertermenter wrote:

(#9)
Ah, this is hard. This would be nice for massive projects that need 1 extra MB, like paper Minecraft. However, this may affect the servers a lot, and like @mtech22 said, most projects does not even hit the 5MB limit. From this, I think the cons outweigh the pros.

bro ScratchOS 3.0 was almost hit the 5MB limit

mtech22 wrote:

5 is a nice, round number, and it'd take up more server space if this happened. Most people don't make projects that exceed the size limit anyway

The amount of server space needed from the small amount of projects that would use the extra megabyte is nothing compared to all the all the costumes and sounds already on scratches server. The limit is 10MB per sound/costume.

This suggestion's been around for awhile but I still think something like this should be done. I don't really see why it couldn't be (and like 3 of my projects had to be moved to exclusively TurboWarp because they just barely went over the 5mb limit)

What’s json

windows-11-pro wrote:

dertermenter wrote:

(#9)
Ah, this is hard. This would be nice for massive projects that need 1 extra MB, like paper Minecraft. However, this may affect the servers a lot, and like @mtech22 said, most projects does not even hit the 5MB limit. From this, I think the cons outweigh the pros.

bro ScratchOS 3.0 was almost hit the 5MB limit

Super Mario Maker 4 can no longer be updated (or at least until the amount of code is reduced to be more space effective) because it hit the 5MB limit.

1MB is a very low amount, but it would help a lot. There are massive projects on Scratch that usually hit the 5MB limit. Increasing the limit by 1MB would multiply the max size of those projects by 1.2, which with the size of those projects is absolutely huge. And very few projects like this are made, meaning that it wouldn’t take as much space. Full support.

I think any increase of the current limit would be a good idea; If someone wanted to put stress on the servers, they could already just make a bunch of heavy assets. There are no downsides to this being implemented.

Maximouse wrote:

I don't believe this would cause any problems for the servers. They can already store 10 MB sounds, so why not 10 MB code? And the number of projects is unlimited, so this doesn't affect storage space at all, just the server performance.

this is true

support this would help a lot but it may effect the scratch servers performance

Maximouse wrote:

I don't know why the limit for project.json is smaller than that for assets.

code doesnt take up nearly as much space

cookieclickerer33 wrote:

Maximouse wrote:

I don't know why the limit for project.json is smaller than that for assets.

code doesnt take up nearly as much space

Advanced projects have a LOT of code.

Support, for the following reasons:
1. Assets are already 10MB, and you can upload almost as many as you want, meaning that even just adding 1 10MB asset will already be roughly twice the size of project.json, and thats just 1 asset.
2. Most projects don't reach the 5MB project.json limit anyway, meaning that this won't really impact server performance drastically
3. The existence of this limit inhibits the creation of impressive projects, removing it would help the few people who do hit the limit actually create the projects they want

1159661667 remember this number
Every project has a .json file of 5 mb. Since there are about 1159661667 projects, this adds up to 5.7 PETABYTES of data. That's only for.json storage for each project
Multiplying the number by 2, and you get 11.5 petabytes. That's the storage capacity for all images, files, sounds, etc.
Adding both, that's 17.3 petabytes of storage.
But adding a sixth megabyte can make the servers run out of storage faster, meaning 6.9 petabytes of storage for every project (total storage), or 1.15 petabytes if the .json file size was raised by a megabyte/project.
Even though this suggestion was from 2021 and whoever wrote OP is probably gone, I still find this interesting. No support.