I agree with the others that you need to understand the basics of image editing to make games, if for no other reason than you need to know what to as for when you have others make graphics for you and to make little tweeks when you get them.

Depending on how you came by the graphics, you may be able to ask to get them with a transparent background, or to get an alpha mask that you can use in image editor to remove the background.You may be able to get someone to make the changes for you, but it is a LOT easier if they have the original files.

As usual, there are many ways to do this.

I think one of the easiest ways is to put a Platform behavior on your enemy, but turn the default controls off. Then when an event occurs you can simulate jump, left and right controls. If the player gets within a certain distance of the slime, simulate right if player.x is greater than slime.x and left control if player.x < slime.x. Here is an example (created with release 93):

Slimed.capx

If you haven't checked out JohnnySix's patrolling example in the arcade, you should. Very cool example, and you can download the capx to see how he did it.

I'm not sure if this is what you want. There are comments to help you understand it. I made the bars different colors to make it easier to see what is going on, but that doesn't change the event sheet at all.

Muchosprite

Ashley was not suggesting adding solid behavior to your airplane sprite, but that you turn it off on the wall that the plane is colliding with if you don't want it to bounce at that time.

In my example the ball goes through the walls when you left click (which turns off bounce off walls) only because the ball was placed in the layout before the walls. If you want it to go over the walls, just move the walls to the bottom of the z order. (Or you could put the ball on a layer above the wall layer.)

I updated the project so that it has the walls at the bottom. The ball flies right over the walls when you left click, and bounces off the walls when you right click.

Note that any changes you make to one bullet behavior you should make to the other bullet behavior. That is why I copied the angle of motion from one to the other when switching behaviors. That would also apply to speed.

You can also create two bullet behaviors on your sprite -- one with bounce enabled and one disabled as in the following capx.

DoubleBullet.capx

Left click to disable bounce, right click to enable. Try to reach the key.

You can also use a bunch of solid sprites to create a boundary. Sort of like the platforms in the Rotating Platform example (in the Construct2 Examples directory). The good thing about that approach is that you can move/remove them if you want the excluded area to become accessible (for example if your player makes a boat or a bridge...)

Here is an example that I did for someone who had problems with everyone shooting at the same time. Everything happens randomly. You may find it useful.

RandomExperiments.capx

On start of layout, creates a random number of enemy sprites at random locations, and then randomly creates new or destroys existing enemies. At random intervales choose an enemy and has it shoot in a random direction. (Ignore the part about the local variable. That was to demonstrate how to handle another problem he was having.)

I don't see the pictures. What kind of game are you trying to make? Do you want to move all of the sprites, or some of them or one of them? Are you using any behaviors on your sprites (like platform or 8-direction)?

Do you have a .capx you can post in dropbox? That is the easiest way for someone to help you.

I'm happy to help you if you give a little more information.

Create a group and also create actions to activate or deactivate that group.

If you try to change the action to a group that doesn't exist an error is generated, which is as it should be.

However, if you change the name of the group, the actions are not changed to correspond to the new name, so you can end up with a situation where you are trying to activate or deactivate a group that doesn't exist, with sometimes amusing results.

GroupNameBug.capx demonstrates the problem. Run it and sprite is created on touch. Now try changing the name of the group. The actions are not changed, and when you run the behavior is quite different from before.

While this is counter to C2's normally excellent consistency checking, I would rank it fairly low priority in the general scheme of things since, even though you can get some strange behaviors as a result, you don't actually lose anything other than time (or possibly your mind. <img src="smileys/smiley2.gif" border="0" align="middle">)

Cute game. I played it all of the way through, and there were two annoying things I noticed:

1) The Drop button keeps moving from level to level -- and maybe even within levels. Not sure. Anyway, IMO the Drop button should always stay in the same place so player doesn't have to reposition mouse and can keep eyes on the dinosaur. That the button moved around made it seem like you didn't pay as close attention to details as you could. (I would use the same graphic for the drop button on all layouts, too, but that is a matter of preference, and not an annoyance.)

2) There was not indicator that I saw of what level I was on. It seemed like there was an intermediate screen that flashed by so quickly that I couldn't see it at all, but that might be some annoying flash from switching layouts. I was hoping for something that would always be on the screen saying what the level was.

Those are pretty minor problems. I liked it!

Thanks! I posted the link to a new project (RandomNosPush.capx) that shows how to generate a unique random number on demand. You'll find it along with a brief explanation at the very bottom of the Generating random numbers without duplicatestutorial. It is a more complete example. Hopefully you'll find the comments enough to explain what is going on.

Read my tutorial on Generating random numbers without duplicates.   I made it just for you! <img src="smileys/smiley2.gif" border="0" align="middle">

Basically, each time you generate a random number you will check to see if it is in an array and if it isn't you will insert it into the array and use it for your game. If it IS already in the array, try again.

Since you don't know the size of your array to begin with, you might want to push the value onto the end of the array. I'll try to post a variation that shows that today. When I do it will be #3 under the end notes.