Scratch

mythbusteranimator · 2012-11-02 18:40:31

In ONE SCRIPT, please show me how to do this.

I want to be able to move my ball after it switches to the costume, but the "point in direction" and then "move 2 steps" script isn't working. Is there some trig you do to change x and y by using the direction? I need help. tongue

mythbusteranimator · 2012-11-02 19:42:30

See? I get the trig right for one bounce in this project, but then it starts to keep tailing to the right. What is wrong? hmm

MoreGamesNow · 2012-11-02 20:59:19

I personally find it easier to deal with x and y velocities (and ignore direction) if you're dealing with only walls either parallel or perpendicular to the x axis (like you are).

when gf clicked
forever
draw paddle
go to [whereever the ball is supposed to be v]
change x by (xvel)
change y by (yvel)
if<touching color [color of bass]?>
set [yvel v] to ((-1)*(yvel))
change y by (yvel)
end
if<([abs v] of (x position)) > [240]>
set [xvel v] to ((-1)*(xvel))
change x by (xvel)
end
check for goals, etc.

mythbusteranimator · 2012-11-03 08:23:26

Okay. I'll try that. hmm

mythbusteranimator · 2012-11-03 21:43:34

Just curious, but when a sprite flashes in test mode (while moving) but hides in presentation mode, what will it do after being uploaded?

mythbusteranimator · 2012-11-03 21:57:26

And the bal won't show. Any help, guys? sad

MoreGamesNow · 2012-11-03 22:29:36

I'm probably the wrong guy to talk to about stuff like this, but the key to rendering multiple things with one sprite is the slight built-in delay between the end of the loop and the beginning. This means that you'll probably end up seeing whatever is rendered at the end of the loop. It also means that when you clear it, you need to make sure the "clear" block is above the rendering script (so the slight delay occurs after rendering, not after "clearing")

mythbusteranimator · 2012-11-03 22:37:00

MoreGamesNow wrote:
I'm probably the wrong guy to talk to about stuff like this, but the key to rendering multiple things with one sprite is the slight built-in delay between the end of the loop and the beginning. This means that you'll probably end up seeing whatever is rendered at the end of the loop. It also means that when you clear it, you need to make sure the "clear" block is above the rendering script (so the slight delay occurs after rendering, not after "clearing")

The "clear" block is at the top of the script, if that is what you mean.

mythbusteranimator · 2012-11-04 08:00:39

mythbusteranimator wrote:
MoreGamesNow wrote:
I'm probably the wrong guy to talk to about stuff like this, but the key to rendering multiple things with one sprite is the slight built-in delay between the end of the loop and the beginning. This means that you'll probably end up seeing whatever is rendered at the end of the loop. It also means that when you clear it, you need to make sure the "clear" block is above the rendering script (so the slight delay occurs after rendering, not after "clearing")
The "clear" block is at the top of the script, if that is what you mean.

MoreGamesNow · 2012-11-04 08:52:59

I'm looking at your script, and I'm a little confused. Could you tell me exactly what you're trying to accomplish, and why you're using a list when it appears you are only using the first item?

mythbusteranimator · 2012-11-04 20:24:14

MoreGamesNow wrote:
I'm looking at your script, and I'm a little confused. Could you tell me exactly what you're trying to accomplish, and why you're using a list when it appears you are only using the first item?

Right now, the list thing should not be a problem; it is only keeping the length of the score for later in the script (and it works). I want to figure out to show the ball, as it hides in presentation mode/uploaded, but it flashes in test mode.

MoreGamesNow · 2012-11-04 21:28:14

Put a "stamp" before you "hide" your ball. I think I got it working but I can't seem to upload a picture and it is way too long for me to type up tongue

BTW, you can just do this for collisions. If you move only along the x axis, you can be sure that you're hitting either the left or right side (resulting in a reversal of x velocity). Likewise, if you move only along the y axis (or, in this case, after you've moved along the x axis), you can be sure that you're hitting one of the horizontal objects.

change x by (xvel)
if<touching [edge v]?>
set [xvel v] to ((-1)*(xvel))
change x by (xvel)
end
change y by (yvel)
if<<touching [edge v]?> or <touching color [color of paddle]?>>
set [yvel v] to ((-1)*(yvel))
if<touching color [color of paddle]?>
add point; make more difficult, etc.
else
if<(y position) < [0]>
lose a life, if >5 stop all, etc.
end
end
change y by (yvel)
end

Last edited by MoreGamesNow (2012-11-04 21:34:41)

mythbusteranimator · 2012-11-05 08:09:37

Thanks a TON! I got it working now; I'll be sure to give a lot of credit! big_smile

Paddle2See · 2012-11-05 11:34:13

Closed by request of the topic owner.

Scratch

archived forums

#1 2012-11-02 18:40:31

Direction Help!

#2 2012-11-02 19:42:30

Re: Direction Help!

#3 2012-11-02 20:59:19

Re: Direction Help!

#4 2012-11-03 08:23:26

Re: Direction Help!

#5 2012-11-03 21:43:34

Re: Direction Help!

#6 2012-11-03 21:57:26

Re: Direction Help!

#7 2012-11-03 22:29:36

Re: Direction Help!

#8 2012-11-03 22:37:00

Re: Direction Help!

MoreGamesNow wrote:

#9 2012-11-04 08:00:39

Re: Direction Help!

mythbusteranimator wrote:

MoreGamesNow wrote:

#10 2012-11-04 08:52:59

Re: Direction Help!

#11 2012-11-04 20:24:14

Re: Direction Help!

MoreGamesNow wrote:

#12 2012-11-04 21:28:14

Re: Direction Help!

#13 2012-11-05 08:09:37

Re: Direction Help!

#14 2012-11-05 11:34:13

Re: Direction Help!

Board footer