You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One user has suggested the following (in their words): Idea (that you might not see or be too hard to make): Maybe, with all the custom blocks that Turbowarp uses, add them in scratch, the same way you did with the "is turbowarp" block. Just use custom blocks, so that whenever a turbowarp block is exported, turn it to a random-named bloc, and if it is put back to turbowarp, have turbowarp replace it. It might not actually be a good idea, but I think it might work so that turbowarp projects could be a bit better.
The text was updated successfully, but these errors were encountered:
One user has suggested the following (in their words): Idea (that you might not see or be too hard to make): Maybe, with all the custom blocks that Turbowarp uses, add them in scratch, the same way you did with the "is turbowarp" block. Just use custom blocks, so that whenever a turbowarp block is exported, turn it to a random-named bloc, and if it is put back to turbowarp, have turbowarp replace it. It might not actually be a good idea, but I think it might work so that turbowarp projects could be a bit better.
The text was updated successfully, but these errors were encountered: