Try 'For each' statement. It a bit resource consuming and tricky though.

Inspiring :)

Thanks for reply!

So, Node-webkit generates an .app file. When I try to run it this thing shows up:

<img src="https://dl.dropboxusercontent.com/u/66358591/screenmac.png" border="0" />

It says: The application quit unexpectedly. Click relaunch to launch the application again... Ignore, Report, Relaunch.

I'm using Lion. MacBook pro late 2011, if it helps.

Process:        node-webkit [11552]

Path:            /Users/USER/Desktop/myapp.app/Contents/MacOS/node-webkit

Identifier:      com.intel.nw

Version:        1.0.0.0 (1.0.0.0)

Code Type:       X86 (Native)

Parent Process: launchd [140]

Date/Time:       2013-07-01 12:05:24.674 +1100

OS Version:      Mac OS X 10.7.5 (11G63b)

Report Version: 9

Interval Since Last Report:          934263 sec

Crashes Since Last Report:           8

Per-App Crashes Since Last Report:   8

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

idk

Using r136, not working :(

Great tip, mate!

Try system condition Create object and set it to players position. Work fine for me.

I tried your 'code', and it works too. Show us you capx please

http://www.scirra.com/manual/149/function

capx

This is a rough sketch of one of the gazillion ways you can do it. Hope it'll help

The Ghosthouse with Boo is missing ;)

Up!

Ludum Dare 26 is approaching! Anyone to participate?

I've been working on powerups for my Hobo project this week. This is an example of one of the many uses for Beardomancy.

<img src="http://img687.imageshack.us/img687/7158/hobo2.gif" border="0" />

That's... just... surreal

Before you will attempt to create such game as RTS, please read this brilliant post from Deadeye:

I know you probably don't want to hear my advice, but I'll give it anyway because it's good.

I've seen you start and stop a couple different projects in a very short amount of time. You seem to be suffering from an advanced case of what is known as Big Game Fever. This happens to a lot of people just starting out making games. It happened to me. Hell, it still happens to me.

This is always the result:

<a rel="nofollow" href="http://www.youtube.com/watch?v=jyC0j2lUaEw">http://www.youtube.com/watch?v=jyC0j2lUaEw</a>

There is only one cure for Big Game Fever. Don't make a big game. It's that simple. Put those ideas on hold for a while.

What you want to do is make a small game that you can actually complete, just so that you have the experience of knowing what it takes to finish a game. Make Asteroids, or Pac Man, or Space Invaders, or a small arena shooter. Something like that. Nothing more complex than, say, Super Mario Bros. In fact, Super Mario Bros might even be too complex to start with considering the number of enemies that you would have to create.

I am being totally serious here. This is good advice. Literally THOUSANDS of developers have struggled through trying to make their Big Game when they're just starting out, and they have all fallen flat on their faces. They will all say the same thing... start small.

Make a small, complete game with everything in it. Title screen, a couple of levels, game over, scoring, music, sound effects, etc. Put a little polish on it. Completing the thing will do wonders for your experience, even if it's a small, stupid game. And it's a HUGE moral booster. Your Big Ideas will still be there when you're done with the small game, and you will have a MUCH better idea of what it takes to turn your Big Idea into a reality.

If you keep starting and quitting Big Game after Big Game, you won't learn anything.

The only problem is that nobody ever listens to this advice. Big Game Fever apparently affects their hearing as well. Perhaps this time it will be different...

You WILL learn all necessary techniques if you'll MAKE a bunch of smaller games. Read tutorials for smaller games and at one point you will able to make your big project without any help.