On the other hand it's only been two days. So maybe people haven't used it that much yet. I vote give it a couple of days more. No need to rush it.

This thing you're doing, taking existing game-making methods and converting them to construct plugins; it is incredibly usefull so keep on doing it!

Great tutorial for beginners!

The else condition is fantastic! However, i actually found the "bad" version most interesting. Before i used Else i had similar workarounds, but even worse, so if i for some reason don't get else to work now at least i have a clean (more or less) workaround to fall back on.

Kickass!

no nO NO! don't encourage this! This is not a "challenging" game. This is an incorrectly balanced game! It is the most common mistake ever, It's bad and it needs to be corrected.

But we're not talking about a sprite here... the hotspot for the box of the plasma object can't be moved, and how the source is resized doesn't seem to depend on the hotspot.

I'm basically going for a larger fire. Increasing the speed only stretches it on the length if I'm not mistaking. But maybe that combined with changing the transparency. Well, I'll try some more, but if anyone understands how to work around the weird resizing let me know.

I have a black screen with a plasma fire in the middle. Some gaming is going to take place around the fire and as you progress the flame should slowly grow from very tiny to pretty huge.

Question is: What is the best way of making the flame grow. I've tried just changeing the width/height, and it looks right, but it seems like the source is resizing in a different way then the box, so eventually it moves out of the box.

I don't understand the plasma object fully yet, so if there's some other method of making the fire bigger feel free to suggest them.

Link broken again...

Edit: Sorry didn't realize how old this thread was.

I think this tutorial looks great, however, I'm not in need of something like this right now, and it looks to complicated for me to do right now just for fun.

HOWEVER. It's a quality tutorial from someone who has a clue, and that's worth a lot. I, and many others who have been using construct for a while will always think these things are interesting since it presents a challenge and something new to understand. It does not teach or clarify something you already knew you could do in construct, but it pushes the boundaries further. Getting a tutorial like this is just as exciting as a new feature being implemented in construct.

I think many people download it, and as soon as they look at the code their brain starts to boil and they quickly shut it down. But that's probably not be the people this tutorial is made for. But the few people who can tackle this will appreciate it very much.

It seems like a perfectly fine game, but i think you made the common mistake of judging the difficulty from your own experience. Since you test the game hundreds of times it seems easy for you, but i think most people will give up on this game as soon as the monster starts chasing you since it's too hard.

You need to make it REALLY easy in the beginning, just enough to be a little challenging to a first-time-player. And you also need checkpoints as minor said.

Saving needs to be sorted out, when using system save to file and load file to save and load game states, on load copies of objects such as lights end up in completely different positions to where they should be.

It also freezes the platform movement in my game (not reproduced in a clean .cap though). It's the first time now when I've come to the point in a game where i need to be able to save, but to encourage people to finnish games without too much trouble this feature should work flawlessly.