Hey, this is awesome astronaut. With the recent success of my game bounce, I have been in a hurry to get new game developed. One of these games is a retro style, shooting, platforming game set in space.

First issue solved! sprites no longer overlap on side of the screen.

Now I am dealing with improving the collisions. I got my scripting from the wiki. The side and bottom collisions work fine, but the top collisions do not work. I think it may not be working because I adjusted the original scripting from x and y scrolling to just x scrolling.

Is the project shared?

BTW £ is the pound sign in the UK, # is known as hash here

deck26 wrote:

Is the project shared?

BTW £ is the pound sign in the UK, # is known as hash here

Firstly no. I don't see why you'd need to have it shared because it is just basic scrolling, and is on the wiki.

Secondly, I am an American, and it is still called the pound sign, or number sign.

Yes but you've tried what it says on the wiki and had a problem with it. If you want help with what you've done it makes sense to share it unless you get help from someone else who has also followed the wiki and not had a problem. If you're unwilling to share it you may not get the help you need but that's obviously up to you - generally speaking it is easier to help people on this forum when they share the project.

Okay, I shared the project. Here it is: http://scratch.mit.edu/projects/49514782/

I take it you mean the grey line that appears between the background sprites sometimes. Try using 479 instead of 480 in the sprite scripts.

deck26 wrote:

I take it you mean the grey line that appears between the background sprites sometimes. Try using 479 instead of 480 in the sprite scripts.

no. I mean how the sprites overlap on the edges, because scratch refuses to let sprites exit the console. Most people solve this by just making a border around the edge, but I think that would hinder the gameplay experience.

As far as I know there are 3 solutions.

1. Mask the edges - you say you don't want to do that which I can understand

2. Make the sprites bigger by adding single pixels offset at either side. If you can work out the correct colour they should stay hidden well enough. To do this you'll probably have to move the centre of the costume to access the area currently outside the costume and move the centre back. This only works in vector mode as in bitmap mode moving the centre loses the edge of the image. I'd be tempted to start with visually obvious additions to try the idea and then think about disguising.

3. Work with overlapping sprites so you can hide the sprite as soon as it gets to the position where it refuses to move any further.

deck26 wrote:

As far as I know there are 3 solutions.

1. Mask the edges - you say you don't want to do that which I can understand

2. Make the sprites bigger by adding single pixels offset at either side. If you can work out the correct colour they should stay hidden well enough. To do this you'll probably have to move the centre of the costume to access the area currently outside the costume and move the centre back. This only works in vector mode as in bitmap mode moving the centre loses the edge of the image. I'd be tempted to start with visually obvious additions to try the idea and then think about disguising.

3. Work with overlapping sprites so you can hide the sprite as soon as it gets to the position where it refuses to move any further.

I don't know. I think I will attempt my own method, since all of these seem to cause restrictions on the gameplay or graphics.

OK, if you come up with something can you log the details here so others can take advantage?

deck26 wrote:

OK, if you come up with something can you log the details here so others can take advantage?

I found the answer. I merely modified the script on the wiki so that instead of 480, it was a little under 465.

Now what I need help with is improving the collisions. They are also from the wiki.