I've built a program that runs in 1.4. It takes text input and parses it, grabbing some values from it. Uploading breaks it. The fix is to decrease the letter number by 1, an easy fix.

Is there a way to detect which version of Scratch is in use so I can put in a little snippet that fixes this bug automatically?

@Fix: Open the project in the 1.4 editor, do your changes, and re-upload. It'll replace the project with the newer version.

@DetectVersion: There is no way to detect the Scratch version, per se, but you can see obvious differences in 1.4 projects apart from 2.0 projects. 1.4 has only one description, “Notes and Credits”, while 2.0 has two, “Instructions” and “Notes and Credits”. Also, only on 1.4 projects is there a Download 1.4 Code button in the Share To tab.

I know how to fix it. The issue is that fixing it means maintaining two versions which seems like a lot of hassle. If there's no way of doing that then it'll just have to be this way. I plan on recreating the code in something else when I get around to learning to code properly.

Flamekebab wrote:

I know how to fix it. The issue is that fixing it means maintaining two versions which seems like a lot of hassle. If there's no way of doing that then it'll just have to be this way. I plan on recreating the code in something else when I get around to learning to code properly.

Then delete the older version.

Why would delete the old version? I want to keep a backup copy of my 1.4 version rather than just storing it locally.

I much prefer to work in a local environment and until a 2.0 client is released I'm sticking with 1.4.

Flamekebab wrote:

Why would delete the old version? I want to keep a backup copy of my 1.4 version rather than just storing it locally.

I much prefer to work in a local environment and until a 2.0 client is released I'm sticking with 1.4.

Save it as something like backup.

eaglgenes101 wrote:

Save it as something like backup.

Yeah, I know how to do all that. The point isn't how to do it, it's figuring out whether there's a way that means it can be avoided.

Building two versions of the project every time I create a new version is needless hassle. I'll create a workaround instead.

I'll create a toggle at the top of the code that I can manually set before uploading.