Hi murdock

instead of setting the position, you should spawn the bullet.

Instead of using the scrollto behaviour use the system action scrollto.

Simple example:

System: every tick /walking = true -> system: scrollto player.x,player.y

System: every tick /driving = true -> system: scrollto car.x,car.y

darktoad

You'd still want another condition in there to make sure that during game-play gold could get under 100 without the while loop starting to run.

I found this example on the forum:

simple-water

I would make a boolean variable called start as well so that when 100 gold is reached you could set start to false and add that to the condition. Else during the game everytime it gets below 100 this event would fire.

Every 0.05 seconds - if gold is < 100 - start = true - add 1 to gold

if gold = 100 - set start to false

System every tick - Set text to "gold :"&player.gold

mchulet

You are making it hard on yourself by using touch input and mouse input. You can use just the touch input (It's set to accept mouse input as touch). So when you left click inside your game it will be seen as touch input. That way you won't have to make different events for different devices. Your last event has "is touching", you should change this to on object touched.

I'll have a look at other things I notice, but for now this could be a good start, for I don't know if your events for different devices are hurting eachother.

I would like to help, but I can't open your capx, because it has add-ons I don't use. (html pode div) and (chrome console).

I don't quite understand what you mean by touch-display.

These things can be different for different games.

Maybe this will work. On drop sprite z-order move to bottom of layer, that way the object will be behind the other dragdrop object so you can move the one that was behind it.

elafreat

What you've done until now is make a background, a sprite spawning bullets and a zombie floating towards the sprite spawning bullets..

I played for three minutes and killed every zombie coming towards me without even having to move..

I love making graphics and would love to help you when you're a little further along in creating the game.

In touch there is no cursor. And it is impossible to follow anything that doesn't exist. You could compare touch (at least single touch) to a mouse only working when the left mousebutton is down.

Dropping an object in touch-mode usually means taking your finger of the screen, so all input is lost. You could try to use events to change between dragging objects, but that really depends on how your game is set up.

touch.x and touch.y only have a value while touching. If your finger is not touching the screen the value will be 0

Mouse.x and mouse.y however always have the value of where the mouse-pointer is regardless of if the button is clicked.

So when making something for a touch device, you should always be aware that there is only input while touching.

mchulet,

It sounds strange, I know, but on sprite drag start seems to (sometimes?) fire before on touch start. But the touch start is dragging example seems to work every time..