Turbowarp can manage to speed up projects which lag in scratch, even while in the editor. And projects that REALLY want to wait before an action can be executed in a normal manner without speed-ups. So I don't understand why scratch projects can't do the same.

good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

EEU1180Nathan wrote:

good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

Hmm… that's difficult but still.

EEU1180Nathan wrote:

(#2)
good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

Not really, because TurboWarp is open-source. However, due to how TurboWarp's compiler works, it prevents seeing the changes of edited scripts while they're running, which the ST probably doesn't want.

CST1229 wrote:

EEU1180Nathan wrote:

(#2)
good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

Not really, because TurboWarp is open-source. However, due to how TurboWarp's compiler works, it prevents seeing the changes of edited scripts while they're running, which the ST probably doesn't want.

Why does it hide that?

ABC124816 wrote:

CST1229 wrote:

EEU1180Nathan wrote:

(#2)
good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

Not really, because TurboWarp is open-source. However, due to how TurboWarp's compiler works, it prevents seeing the changes of edited scripts while they're running, which the ST probably doesn't want.

Why does it hide that?

If you make changes it won't apply until you restart the program, because compiling means converting to JS but you can't re convert again mid run

ABC124816 wrote:

(#5)
Why does it hide that?

Basically, TurboWarp compiles scripts to JavaScript, and JavaScript code can't really be edited while it's running (unlike vanilla Scratch, which manually interprets every block individually).

EEU1180Nathan wrote:

good idea but then you would need scratch to recreate the engine without breaking everything and ruining cloud variables

Or just ask garbomuffin for help.