I was thinking about how scratch has a 300 clone limit but I was thinking maybe we could add a setting to change clone amounts for a project with a warning for anyone trying to get more than 300 clones you can also reduce the clone limit for smaller clone applications. Here's some setting modes for the clone limit I thought of: 50(smallest limit) 100(very basic applications) 150(default for new scratchers) 200(decently sized projects) 250(slightly less clones) 300(default for scratchers) Anything above 300 I have a solution to right now. A clone amount part of creating a scratch account that you can change anytime and if the project clone limit is greater than the users set clone limit then for that user it automatically goes down to their specific clone amount. Back to clone limit ideas: 350(for more advanced projects that need extra clones) 400(for projects that need a very high amount of clones)
450(the limit of clones any regular scratcher can use) 500(only for scratch members since no average scratcher with potential evil intentions should have this much) 550(only for members because of the same reason) 600(true maximum and only for members). Do I think this is a bit extensive for clone amounts. yes do I think this will be rejected? Yes would this be hard to code. Definitely yes do I think this would be bad? Kinda. But even just having the option to reduce clone amounts for a project or extend it to 400 I would say would be pretty good for scratch. I still think scratch would take this down and direct me to the rejected suggestions so here. This is the full rejected list including increasing the clone limit(thats at section 2.4) anyways here you go the rejected list. https://scratch.mit.edu/discuss/topic/343602/ have a good day! and read the entire list so you can make not rejected suggestions for scratch!

Rejected

TLORS wrote:

2.4 Increase the 300 clone limit
The clone limit is set in place to prevent projects from becoming unplayable. Otherwise, users could create a large number of clones very quickly and crash someone's browser page. Plus, the Scratch Team wants to make sure that all projects run smoothly for as many people as possible. Increasing the limit to even 500 clones might make the project run slowly on some users' devices.

My idea was you could set you default clone amount when creating a project or viewing a project allowing you to change it anytime and any project with a higher clone amount than what your default is it would automatically decrease the clone limit so you have a smooth experience tho I do think it would be hard to code in JavaScript

No support.

Members are not supposed to get extra blocks and features (extra clones)

Why would we need to limit the max clones (some users may not get it)? Just keep it at 300 and just don't make 300 clones

I think a suggestion similar to this was already rejected so it won't happen

No support. It's rejected AND members aren't supposed to get extra features.

But ST is unrejecting so many things that The Official List of Rejected Suggestions (TOLORS) became The List of Rejected Suggestions (TLORS) so it might just be unrejected for members-only.

No support, not only is this rejected, this would also mean the Scratch Team is paywalling features for members. Which leads to a ton of backlash in the community.

collapse^rejected

reporting to be closed as it is rejected

next time read TLoRS

Closing as this is (currently) rejected.