Scratch

laser314 wrote:

amcerbu wrote:

Well, if Scratch had greater computational speed (in other words, no built-in delay), I would use a recursive function, but unfortunately, loops are slow.

I don't think turbo mode has the delay.

That's correct, but making programs for turbo mode is harder; I've been experimenting with it on my test account, but you have to implement a feature that keeps the framerate constant.  This restricts your programming: no "glide" blocks, no "wait _ secs" blocks, and no "play _ until done" blocks.  I don't think Firedrake969 wants to build a project suited only for turbo anyway.

EPICPIKAGUY wrote:

EPICPIKAGUY wrote:

fetzer wrote:

Ya, i might also suggest making the wall a bit thicker?

Yep,that is a great idea,but what if u wanna make a wall thin?first you have to make a maximum velocity(your caracter cannot go faster than a certain speed),then make your sensor as thick as your maximum velocity(e.g. Max vel. Equals 5,u make sensor 5 pixels(if u don't know that measure,just estimate)).

No offense,of corse!

The wall thickness is NOT the problem.

wahoo77 wrote:

it should work with only one if/else block

That may be possible, but would definitely be difficult.  I've simplified the script though.

when gf clicked
forever
set [d v] to ((distance to [mouse-pointer v])/(length of sprite))
point towards [mouse-pointer v]
set[bool v] to [false]
set [x v] to (x position)
set [y v] to (y position)
repeat until <<(distance to [mouse-pointer v]) < (length of sprite)> or <(bool) = [true] >>
move (d) steps
if<touching [wall v]?>
go to x:(x) y:(y)
set [bool v] to [true]
else
set [x v] to (x position)
set [y v] to (y position)
end
end
if<(bool) = [false]>
go to [mouse-pointer v]
if <touching [wall v]?>
go to x:(x) y:(y)
end
end

Edit: oops, it appears to be glitching when I try it, and I won't have any time to fix it today.  Sorry guys.

Last edited by MoreGamesNow (2012-06-18 08:15:28)

Does this require only one sprite?

Make sure it moves back a greater distance than it moves forward. Also, make sure it checks for walls as often as it checks for movement keys pressed. I hope this helped! (:

Did you try my script?

You would need to go into color sensing and velocity, which is a whole nother topic.

If you come look at my game, Frigate, you'll see what color sensing+velocity is. 

Download and look at one of the character sprites. Basically, we have velocity, and we have another costume with colors on each side of the sprite. Then, when the script runs, it detects to see if any of the colors are touching a wall. If it is, then the script tells the velocity variables to reverse direction and bounces the sprite back.

If my script is too confusing, I'll write up  a simplified one.