hi! i think this would be a cool place to discuss the theoretical limits of scratch.
Using pen, it is possible to create full 3d renderings, and insane things have been created. assuming lag isnt an issue, surely, most, if not all 2d games can be made in scratch. this is, theoretically, true with 3d games aswell.
the only limits that would actually cause major problems are the 50 megabyte limit and, arguabaly more devastatingly, the 1/10 of a second limit for cloud variables, aswell as a lack of cloud lists.
PLEASE ADD CLOUD LISTS SCRATCH TEAM PLEanyways, if you can think of any other limits, this is the place, discuss, and… stuff! yeah!

Variables cannot add by one after 9007199254740992, and wait blocks break ~2^1021 seconds after 1970.

Terminusfinity391 wrote:

Variables cannot add by one after 9007199254740992, and wait blocks break ~2^1021 seconds after 1970.

Let me make sure I understand what you're saying.

Variables cannot be greater than 9007199254740992, and wait blocks break after around 1970+2^1021 seconds.

(“EHM AKSHUALLY” post time!)

Wonkymoon8 wrote:

(#1)
the only limits that would actually cause major problems are the 50 megabyte limit

The 50 megabyte limit was from 2.0.

Wonkymoon8 wrote:

(#1)
PLEASE ADD CLOUD LISTS SCRATCH TEAM PLE

That's rejected.

Steve0Greatness wrote:

(#3)
Let me make sure I understand what you're saying.

Variables cannot be greater than 9007199254740992, and wait blocks break after around 1970+2^1021 seconds.

Wrong.
Variables *can* be greater than 9007199254740992, it's just that they use floating point numbers, so they get less precise as they go larger. 9007199254740992 is the point at which it becomes less precise than integers, meaning they snap to the closest increment of 2, which means adding 1 won't do anything.
For the wait blocks, I think they literally do mean “wait blocks break ~2^1021 seconds after 1970.”, as in, they stop working at dates higher than ~2^1021 seconds after 1970. (IIRC the wait blocks use the system time for timing.)

atlasaurinko wrote:

(#6)
There can only be 8 cloud variables which each can hold 250 digits. That's a problem with e.g. MMO's.

*10 cloud variables with 256 digits each

CST1229 wrote:

Variables *can* be greater than 9007199254740992, it's just that they use floating point numbers, so they get less precise as they go larger. 9007199254740992 is the point at which it becomes less precise than integers, meaning they snap to the closest increment of 2, which means adding 1 won't do anything.
For the wait blocks, I think they literally do mean “wait blocks break ~2^1021 seconds after 1970.”, as in, they stop working at dates higher than ~2^1021 seconds after 1970. (IIRC the wait blocks use the system time for timing.)

Oh, sorry. I was confused by the initial post, I think it I just read it entirely incorrectly.

Also, FYI: the usage of “Wrong.” at the top of the reply makes the post kinda come across as rude. Just thought I'd add that in.

Also lists can only hold 200,000 items.
There can only be 8 cloud variables which each can hold 250 digits. That's a problem with e.g. MMO's.

atlasaurinko wrote:

Also lists can only hold 200,000 items.
There can only be 8 cloud variables which each can hold 250 digits. That's a problem with e.g. MMO's.

1. The list length limit is only in Scratch 3.
2. If the Wiki is up to date, the cloud data limit should be 10 cloud variables per project and 256 digits per variable.

gilbert_given_189 wrote:

2. If the Wiki is up to date, the cloud data limit should be 10 cloud variables per project and 256 digits per variable.

Ok thanks.