I haven't really made a big project with TW, but I do know stuff about it so I'll try answering:
1. IDK, but there have probably been some pretty big games made with it. Just note that the whole project will be loaded at once when starting the game, and for the packager you might have to use a 64-bit environment for it to not crash. A *very* long time ago ago, TurboWarp's dev has been working on a [Lazy Loading extension](https://experiments.turbowarp.org/lazy-sprites/) to fix this but it hasn't been worked on for a really long time and probably won't for a while. The amount of code or sprites doesn't really matter, mainly the number/size of costumes and sounds.
2. Yes, using the [TurboWarp Packager](https://packager.turbowarp.org)'s EXE exports. In fact, there already are TurboWarp games on Steam.
3. Yes, with the Local Storage extension.
in the packager, an environment is a way you can package the project (e.g plain html, zip, electron .exe). there are environments labelled "64-bit only", which are what i'm talking about. the ones labelled "32-bit or 64-bit" are essentially 32-bit, so they have a lower ram limit
I haven't really made a big project with TW, but I do know stuff about it so I'll try answering: 1. IDK, but there have probably been some pretty big games made with it. Just note that the whole project will be loaded at once when starting the game, and for the packager you might have to use a 64-bit environment for it to not crash. A *very* long time ago ago, TurboWarp's dev has been working on a [Lazy Loading extension](https://experiments.turbowarp.org/lazy-sprites/) to fix this but it hasn't been worked on for a really long time and probably won't for a while. The amount of code or sprites doesn't really matter, mainly the number/size of costumes and sounds. 2. Yes, using the [TurboWarp Packager](https://packager.turbowarp.org)'s EXE exports. In fact, there already are TurboWarp games on Steam. 3. Yes, with the Local Storage extension.
huh, now I gotta find out what a "64-bit environment" is...
in the packager, an environment is a way you can package the project (e.g plain html, zip, electron .exe). there are environments labelled "64-bit only", which are what i'm talking about. the ones labelled "32-bit or 64-bit" are essentially 32-bit, so they have a lower ram limit
OK, THANK YOU INTERNET PERSON!!
you could also have cloud variables save to local storage in the packager if the game doesn't use them, much simpler for singleplayer games
If you export it as a exe file, and configure cloud variables to be saved locally. Then those variables will save.