This is in 0.96.2 .

That's fast. *thumbs up*

Haha, overall looks OK, but unlike with 3d, it's a bit tough to get the third dimension looking right. But, I did make a bunch of zombies that went with just fine with it. I love Construct's containers

On the other hand... maybe I'll scrap the project altogether since a great zombie sandbox game just got advertised on TIGSource

Lol, from your other tutorials, I expected you to give a CAP with a solution in the end

Wow. Normally I don't bother to rate tutorials or anything, but this one was wonderful. I learned more from it than from the Ghost Shooter tutorial.. and even a little about using sub-events

On a similar topic, is there any way to adjust the inaccuracy of the bullet behaviour using events?

Doppel, that CAP doesn't seem to work for me. It says that ELSE is not allowed as the first condition. I'm using version 0.96 of Construct; any ways for me to fix that?

Jayjay, experimenting with using some very basic skeletal animation for a zombie game. Construct seems to handle them much better than most game making software

Ah, so it is true that 0.96 added some bugs to the sprite editor? I was spending the whole of last night figuring out why I couldn't copy-paste pics into Construct anymore. Guess I won't report that bug

Hmm.. true, I find most of the bugs seem to happen when copying or with the image editor. I just downloaded the new version of Construct and I found at least 3 bugs yesterday. I uninstalled it, used 0.95, and none of the bugs were there. Time to make quite a few bug reports

Ah, thanks. Lol, I expected them to work the same way, seeing how the physics example uses a gradient. Someone should put up a warning or something

Hmm.. I find the whole of Construct's sprite drawing rather buggy to the point of being barely usable So, here's what I do. I draw all my sprites and animations in MMF2 and copy and paste or import them into Construct.

Maybe you guys could check opacity, I found out that most of the tools weren't drawing because they were somehow set completely transparent.

But really, I think the picture editor is Construct's biggest flaw. It's best to use a 3rd party one. Even MS Paint isn't half bad if you get used to it.

Well, against common advice, I have 2 major projects planned for Construct and I'd rather get started with them now while I'm excited instead of wait a few months/years and lose steam. Also, most game design components can't be done without a bit of programming first and the art sometimes can't be done without the engine and so, yeah.

If possible, I want to build up the engine first; everything else can be done outside Construct. Which components of Construct are particularly buggy and/or prone to change? Are there any behaviours, objects, effects, or features I should avoid?

Here's what happened for (2):

http://legendkpr.startlogic.com/abstrac ... p-Muz1.rar

The file doesn't make sense though, just a random experiment with construct features

Yup, gravity enabled. It looks like a collision detection problem with the physics I think.