I get that Turbowarp makes Scratch run faster, but some people (including me) cannot play on Turbowarp. I get that the game might be big, but that doesn't mean some people can't play it on Scratch. It makes me mad whenever I see a game that forces Turbowarp, and I can never remove the “feature” from the game. I want Scratch to remove the ability to make the game unplayable on normal Scratch so I can enjoy any game.

Why not just See Inside and remove the TurboWarp detecting code?

I tried that, but it's more complicated than just removing a line of code

Wait how do scratch projects detect if you're on turbowarp? Scratchattach?

While I do provide Turbowarp links in case the project itself is rly slow on Scratch or eats up memory (The Still Waters AMV I made actually crashed my entire computer because I left the tab open too long and if you play the project it still takes a GB of RAM :skull: ), I don't make it unplayable on Scratch (after all Turbowarp is also banned in school)

According to my brother, projects check your FPS to see if you're in Turbowarp. Also, I'm not saying you make people play Turbowarp, but some people do.

usually people just use

<is TurboWarp?::custom>

<is compiled?::custom>

https://scratch.mit.edu/projects/414716080/
which you can replace with

<(1)=(1)>

I get your frustration but usually the reason people do this is because their game would be unplayable even if they didn't stop you. Most projects that I see that force you to use TurboWarp are doing something with a technique that is too slow for native scratch but barely playable on TurboWarp.

So even if you could remove it you still couldn't play it because it would be too slow. Any project I've seen that recommends TurboWarp instead usually lets you play it while on scratch but the only ones I've seen that force you are ones that are too laggy even in TurboWarp.

coogicon wrote:

According to my brother, projects check your FPS to see if you're in Turbowarp. Also, I'm not saying you make people play Turbowarp, but some people do.

No , it use a block :

<is Turbowarp?>

which is set to 1 when you are on Turbowarp

Also there’s also a mirror for turbowarp :
https://mirror.turbowarp.xyz/#0

Turbowarp is a fundamentally different engine to scratch. if a game simply refuses to run under scratch, then itll probably run at an unplayable frame rate on scratch.

wait how does the

is Turbowarp? 

block even exist? maybe a custom extension?

JonatasPoliglotakids wrote:

wait how does the

is Turbowarp? 

block even exist? maybe a custom extension?

You go it by just make a custom block and set the name to “is turbowarp?”

JonatasPoliglotakids wrote:

wait how does the

is Turbowarp? 

block even exist? maybe a custom extension?

Its litterally doing

define myblock <is TurboWarp?>

and pulling the block out of the definition. Works in native scratch
See the full explanation by the creator of TurboWarp:
https://scratch.mit.edu/projects/414716080/

I get that some games may run at a low frame rate, but for me, most games run at 30 FPS, and I don't care about FPS unless it drops.

coogicon wrote:

I get that some games may run at a low frame rate, but for me, most games run at 30 FPS, and I don't care about FPS unless it drops.

The problem is the FPS drops on Scratch with these games though??

coogicon wrote:

I tried that, but it's more complicated than just removing a line of code

most turbowarp detectors are simple; they will use the is turbowarp block, which is an undefined boolean in scratch (returning 0) but in turbowarp it returns true (note that scratch if statements consider 0 = false)

There is good reason for a project to be turbowarp only, devs will usually only restrict to turbowarp if they have tested it to be unplayable on scratch

coogicon wrote:

(#1)
I get that Turbowarp makes Scratch run faster, but some people (including me) cannot play on Turbowarp. I get that the game might be big, but that doesn't mean some people can't play it on Scratch. It makes me mad whenever I see a game that forces Turbowarp, and I can never remove the “feature” from the game. I want Scratch to remove the ability to make the game unplayable on normal Scratch so I can enjoy any game.

Even if it's changed to not force you, normal Scratch will never be able to run the kind of projects that force you to use TurboWarp in the first place, because that's the entire reason they force you to do so in the first place. Why can't you access TurboWarp? Is it blocked by your school?

I realise this is just rephrasing what's already been said, but some things simply don't work on Scratch, and do on Turbowarp (usually because Turbowarp is substantially faster). Though I've rarely seen use of Turbowarp be required by a project where it isn't needed - more common is a dismissible warning. Try clicking through anything asking you to use TW, as there's a good chance it lets you use the project.

OKAY GUYS DON'T BE MAD
yes, it is true that some games force you to play TurboWarp because of its extra values and lag, mods and blocks.
it is mainly used for checking games, not for making one.
for making one, you have to import should you want to export it.