i prefer to place em just outside and then destroy them in the layout start up. Create when needed.

This had never occurred to me before. I think i'll play with this when I get home. I have a lot of sprites on certain layouts, and I take it destroying them on Start of Layout and only recreating them when I need to saves processing?

Love the backgrounds, they look really cool, as does the lighting.

Looking forward to seeing some more.

Trying out adding some realtime soft shadows to all solid objects in scene. Adds a bit more depth.

Much better with the shadows. Keep them in if there's not a noticeable performance hit.

Sprite looks good, its mario biker.

I thought it Asian Mario. Genuinely looks like the dude that runs my local Chinese Takeaway. Well, as much as a small pixel character can look I suppose!

I do like your game, it's a good thinking puzzle.

As others have echoed, get yourself stuck in to CS2. I've used both and found that whilst Stencyl was easier to pick up, you get more control over what you want to do in CS2.

It shouldn't take you long to pick up though. The online manual is great, the tutorials section is brilliant and there's always people around on the forums to help you on your journey.

download the manual and glance through it. You won't regret it and may even find new faster and better ways to do what you want to do in your game.

I second this. I have it printed off to look over. Even when i'm not sat at my computer, i'll flick through the pages and often after reading it will say "Oh, that's good. I never knew that.".

This could also be circumvented by a player changing the date/time on the phone if I understand correctly. So you could either take that chance, or have a server setup to query date & time.

This is not meant to solve you problem. Mainly because i dont understand the full problem based on a little snapshot of your code.

This is purely meant as a small-little-teeny-weeny showcase to promote the use of timers. To show how easy they are to manage, they never miss, they are a personal clock for each instance. They are allready a 'once while true', so animations are so easy to start. They are basecaly just functions that you call when ever you need to. They are easaly set up to call/stop each other, therefor easy to make a full and automatic running circle.

https://

drive.google.com/open?id=0B1SSuCVV8v74WmpvMEhXdTJNN2s

Hope this helps you some.

I get that, I just never thought of the use of timers before to be used in this way, probably as i'd not had much exposure to it. It does seem to do what I want though.

Thanks for the example too, cool little capx

Cheers for your advice.

You can do it with a 'wait' action. (I would never).

Make a local variable 'TimeToFight'.

Add aCharH to 'TimeToFight'.

Wait 'TimeToFight' seconds.

I did't test this, but it works in my head.

Works in my head as well in practice, but not in testing! Plus if you would never use it, i'd rather not try any further if it's bad practice. I'm just about to start on the timer to see what I can get working.

Cheers.

Or, it will wait 1 second, and then fire them all with a wait of 1 thiCK.

That's actually what happened using:

Or well, I hit AutoAtkTest, it posted "hit x for x" in the textbox, waited 2 seconds, then gutted the rest of the HP instantly.

I'll redo this section then when i've looked in to timers. Hadn't thought i'd need it for this in particular before. Thanks for the suggestion!

Cheers

Hi all,

Having a Wait action in a Function called by another Function is not going to provide a delay is it? I've been trying to add a delay in a Function calling with it to simulate auto attack speed, but I think i've come to the realisation it's not used for what I thought it would be.

I thought this:

Would dump out to the textbox (aCharH.At(13) is 2, which is the character attack speed in seconds):

You hit x for x damage.

Wait for 2 seconds

You hit x for x damage.

Wait for 2 seconds

etc until tempMob.At(0) =<0, then it stops.

What it does do instead, is instantly gut the spawned mob for all it's health and dumps every line to the textbox instantly:

You hit x for x damage.

You hit x for x damage.

You hit x for x damage.

You hit x for x damage.

with 0 delay until death

I don't think i'm using the wrong loop. I've read the manual on the others but they don't seem to fit what i'm after. I tried repeat also but again, it just instakilled the poor ******** I've searched all posts referencing auto attacking and looked through them all. 1 might have helped but it's a good few years old and the capx for reference is not available. I also went through 38 pages of tutorials, and whilst finding a few awesome bits and bobs, nothing referencing my current plight! Even went out for a walk to clear my head but just ended up getting soaked from the rain!

Any idea on what I could use in it's place?

Thanks.

Cheers boys