Scratch

billyedward wrote:

The long line of text method is a 1.3 bug. It was fixed in 1.4.
There is only one 1.4 bug I know of:

In the default cat sprite, make another costume to be a single pixel (the colour doesn't matter).
Then, set the sprite to be 54000% in size.
Now, just switch to the cat costume...
You will see a red walkback window entitled 'space is low'
Be sure to delete that offending cat sprite and then set it to 100% soon; those errors are there for a reason.

If by chance it causes a squeak memory dump (denounced by an unflattering text-filled white rectangle in the top left corner) then try it again with a smaller size. (ie: 2000%, etc. 54000 is the largest it will allow for a single pixel)

Please do not advertise this method outside this forum, because if the scratch team gets wind of it, they will be sure to fix it. And we all know how precious these bugs can be.

Thanks! I went from there, pressed some buttons, typed some stuff and now I have the (pi) block and the (point to x[ ] y[ ]) block! Thanks so much!!!

billyedward wrote:

I will make an unofficial 1.4 open-source soon...

Ok!

Adamman715 wrote:

I saw a bunch of projects by TheoMarr ( http://scratch.mit.edu/users/TheoMarr ) about going into Squeak and changing block specs to show new blocks (pi, Point To X[] Y[], etc. I tried it, but it wouldnt work! He said to copy a long line of text, paste it into a block, and it would open Sqeak. Again, It didnt work, and I really want to get those blocks, so what is the easiest way to get into debug mode???? (besides TheoMarr's way)




Thanks,

Adamman715

http://scratch.mit.edu/users/Adamman715

There is another way to do this now (Which is quicker). Export a sprite with the comment block in (From Scratch 1.2 Beta) then open the sprite and ta da! Then go for the next steps of my tutorials.

Last edited by TheoMarr (2009-09-02 05:40:47)

billyedward wrote:

I will make an unofficial 1.4 open-source soon...

that won't work as good as the real source because without the .changes file, you won't be able to see comments or variable names (they are replaced with t1, t2 ect. ). That will be a pain to programming.

ThePCKid wrote:

Best way to get the Squeak error message (DO NOT TELL THE SCRATCH TEAM)
make a new sprite
do not add any scripts
right click in the scripts area
click "Save picture of scripts"
Then, BOOM!
the error message

Hint - if you want somebody to look at something, just put DO NOT LOOK at the top 

Lightnin wrote:

Huh? What? Did somebody say "Do Not Tell the Scratch Team?"   

ARRGGGGH!!!!!!! I just want to know what Squeak looks like inside of Scratch.
I'm not tring to HACK Scratch, OK?

henley wrote:

Paddle2See wrote:

ThePCKid wrote:

Best way to get the Squeak error message (DO NOT TELL THE SCRATCH TEAM)
make a new sprite
do not add any scripts
right click in the scripts area
click "Save picture of scripts"
Then, BOOM!
the error message

Hint - if you want somebody to look at something, just put DO NOT LOOK at the top 

Busted.

Huh?

another great glitch:
<when green flag clicked>
<forever>
<point in direction( 10(carrot symbol)<pick random(1 )to(360)
<end>

put this in sprite1 and click the green flag. You might have to click the green flag a few times for it to work

Last edited by TobiOlivers (2009-10-18 19:06:06)

TheoMarr wrote:

TobiOlivers wrote:

another great glitch:
<when green flag clicked>
<forever>
<point in direction( 10(carrot symbol)<pick random(1 )to(360)
<end>

put this in sprite1 and click the green flag. You might have to click the green flag a few times for it to work

Please post something which relates with the topic. And if it doesn't leave a red walkbalk window, then what's the point of posting it? 

sorry, I didn't clarify what I was saying, this is another glitch that lets you get to the error screen and to the debug mode. It seemed like people needed a glitch to get to the debug mode on 1.4. If I am wrong and there is countless glitches to get to the debug mode, heres another.    my computers gone for a bit so I'm using a Palm Pre.

Last edited by TobiOlivers (2009-10-19 21:57:03)

Shift-click the "R" in the "SCRATCH" logo>>Turn fill screen of>>click on white space>>open...>>browser. That should help! 

Whats up with not wanting the Scratch team to see it?
Why not just ask them to add a Debug console for we, the "advanced users"?
They lose nothing by us "breaking" into anything in scratch, as it's open source anyway...
So instead of using so much energy to not letting them find out (on a public forum...) just ask them to add a "big red button" that opens up a console for our uses...
no?