You sir just made a lot of people really happy! Including me!

Yeah, there'll be a free version. And you'll have to pay for some cool stuff. And we're still making progress. New website is almost ready. We'll start adding more folks soon after.

Ah! Yes, that makes sense, when it comes to random values you need to approach after and every timers in entirely different ways, so I see where you were going.

If you need help with "Every" timers I've got your back! (Image)

@Socks Thank you! That solved the issue.

You are using an attribute called self.time, which is set to zero - and I can see no obvious way in which it is being incremented in any way, so it will always be 0 (so the condition of the rule with

@As Of Latte That rule will trigger once between 1 and 15 seconds after the actor appears on the scene. Is that what you want?

Could you not simply have . . .

Agreed, sometimes people get stuck on the most obvious things, I've struggled for hours with issues trying all sorts of solutions only to eventually notice that I'd missed out a bracket on an expressi

(Quote)

your help and offering to look at my project, much appreciated (Image)

You tried it with a build published through TestFlight? If so and it still didn't work, either your Purchase IDs are wrong or there's a problem with your logic.

Aha! I don't mind waiting for graphene but it seems to me stating html5 game publishing with gs currently is a bit misleading.

When I try to make particles shoot off in random directions (random(0, 360)), it works great the first time the drill actor collides with enemy actors. But the second or third or whatever else time i

One thing I'd mention is that the death condition (when you die / hit a block) is typical of indie games - and a world away from a more polished commercial release - in that when you die nothing happe

Yes you can but if you are commissioned to design a html5 game a client will usually request the actual files. Making gs a less desirable way of creating online content. What ever the reason

Try using a change velocity behaviour with a rule that should be like 'actor receives event --> key --> right is down' and what is inside it could be like: 'change velocity --> d

The difference between showing people the actual rules that that are causing the issue vs having people make guesses at what these rules might be and how they are set up is vast, it's the difference b

P.D: this may be out of topic, but i used to receive email notifications every time any of you guys answered or commented in a discussion i opened, but it seems those mails stopped arriving, is there

drawn-out process largely made up of random guesses ! Lol ! (Image)