Scratch

It looks to me like you're rendering the target AFTER checking to see if you're touching red (see below).

What you're doing:

forever
     clear
     check if touching red  // impossible since you cleared the red target that was rendered last frame
     render red
end

Also, can you figure out why the arrow won't reset? Or why the target keeps disappearing?

bluergh my brain hurts but my guess is that the script wont reset the arrow because it got to finish the loop first?

mythbusteranimator wrote:

MoreGamesNow wrote:

It looks to me like you're rendering the target AFTER checking to see if you're touching red (see below).

What you're doing:

Code:

forever
     clear
     check if touching red  // impossible since you cleared the red target that was rendered last frame
     render red
end

Why do I fail so much? 

Seems like everytime i check you are asking something on help with scripts 

MoreGamesNow wrote:

I "showed" the sprite continuously (instead of only when it should appear) and it never actually touches the gray line.  It is also hidden when you do the sensing, which I believe means that it will always return false anyway.

http://i47.tinypic.com/2vwbng8.png

if it is not sensing grey then you need to check your script, make sure it is set to sense the right colour as well

mythbusteranimator wrote:

MoreGamesNow wrote:

I "showed" the sprite continuously (instead of only when it should appear) and it never actually touches the gray line.  It is also hidden when you do the sensing, which I believe means that it will always return false anyway.

http://i47.tinypic.com/2vwbng8.png

Wait...is it going too fast, so it just skips right over the grey area?

hmm

that is actually possible - set the arrow speed slower?

mythbusteranimator wrote:

MoreGamesNow wrote:

I "showed" the sprite continuously (instead of only when it should appear) and it never actually touches the gray line.  It is also hidden when you do the sensing, which I believe means that it will always return false anyway.

http://i47.tinypic.com/2vwbng8.png

Wait...is it going too fast, so it just skips right over the grey area?

I think the problem is more along these lines:
When you draw the arrow near the right side of the screen, the tip of your arrow ends up too far right, so that, when you sense to see if you're touching the line, your "bow" (the costume you're using to see if you're touching the gray line) is too far right.

Essentially: your bow can only go so far off the screen, and you're reaching that limit when you draw the arrow so that, when you move the bow back to its "sensing position", it isn't far enough right.


The above is just speculation, but I think it is much more likely that that is the problem than that you're "skipping" over the gray line (since you never actually end up past it anyway).  That being said, "skipping" may become a problem once this one is resolved.

Llamalover wrote:

OK, I've downloaded your project and had a quick look at it.
Why is it all one script? I can understand why you might want to make a one-sprite game, but I'm not sure why you'd want just the one script. It'd be a lot easier (and would probably run faster if you broke the script up into chunks (and it would be ten times easier if you used more sprites!)

...

Edit: I've just noticed the title of the project '1s1s1c' - I'm guessing that means 1 sprite, 1 script, 1 c-something? In that case, I guess you won't be wanting to split the script into several parts. I still recommend you try and figure out some ways to lighten the script, if at all possible. Maybe trying using lists? Again, I don't know if that"ll work, I haven't looked properly at the entirety of the script.

I find the easiest ways to code 1s1s is to break the code into pieces and use something like this:

when gf clicked
broadcast [initialize v] and wait
forever
broadcast [part1 v] and wait
broadcast [part2 v] and wait
broadcast [part3 v] and wait

Well, any luck? Have you got everything working?

mythbusteranimator wrote:

MoreGamesNow wrote:

Llamalover wrote:

OK, I've downloaded your project and had a quick look at it.
Why is it all one script? I can understand why you might want to make a one-sprite game, but I'm not sure why you'd want just the one script. It'd be a lot easier (and would probably run faster if you broke the script up into chunks (and it would be ten times easier if you used more sprites!)

...

Edit: I've just noticed the title of the project '1s1s1c' - I'm guessing that means 1 sprite, 1 script, 1 c-something? In that case, I guess you won't be wanting to split the script into several parts. I still recommend you try and figure out some ways to lighten the script, if at all possible. Maybe trying using lists? Again, I don't know if that"ll work, I haven't looked properly at the entirety of the script.

I find the easiest ways to code 1s1s is to break the code into pieces and use something like this:

when gf clicked
broadcast [initialize v] and wait
forever
broadcast [part1 v] and wait
broadcast [part2 v] and wait
broadcast [part3 v] and wait

It just makes it easier to organize and faster to edit the scripts.

I haven't done the suggestions yet, because I have been busy.
But I will try them now.
(and I try to do 1s1s1c because they are more challenging and cooler.  )

Of course.  I use the above script while my 1s1s projects are in development, and then just stick them all together at the end.