As I said, I probably won't be changing this project just to keep it pure to its one month restriction, but if I ever use the engine again, friction and air control would be very easy to change since I didn't hard code them in. But I will say that everything was a breeze and a pleasure to code in Construct. The only thing I couldn't figure out how to do was have objects follow a predefined path easily, and I'm sure I just missed something there. Plus, with families and event sheets, I could probably easily export some of the movement routines for future usage.

Mostly, though, I just wanted a few people to have a bit of fun. Sorry if the controls are too frustrating; they do take a bit of adjusting to. And ironically, Doppel, I was thinking about adding some sections of icy platforms that had literally no friction, but I never got around to it.

I indirectly found out about Construct through SomethingAwful's fourth Game Development Challenge. I decided to participate and I also decided to give Construct a go. The rules of the challenge were simple enough: make the game however you want, with as many people as you want, as long as it revolves around the theme. This time around, the theme was: Deals with the Devil, and their horrible and inevitable consequences.

I actually surprised myself with the quality of the result, considering I technically had never used Construct before (although I was quite familiar with various Clickteam products), and also am generally not a graphics/sounds guy. However, I made every part of this game from scratch in the course of one month, and thought it would be worth showing off a Construct creation in the official forums.

I will, however, warn you that the general consensus is that the controls are too difficult. I didn't realize most people would find it so hard, since I can navigate the in-game world rather gracefully, but I guess my best advice is as follows: You have very little control over your character while in the air. Try to get the momentum you need, which is usually very little, before jumping, as you won't be able to greatly alter your trajectory mid-jump.

That being said, here's the download link for anyone who wishes to play it: http://home.comcast.net/~hammerbro/Penance.zip

Comments and questions are welcome -- I'll gladly respond to any questions about the inner mechanics, although I don't habitually browse these forums, so my posts might be slightly few and far between. And although I could very easily extend on the game (I find it's rather short once you get the hang of the physics) or make it easier, I'm not going to actually modify this particular project, in order to preserve the sanctity of the one-month restriction. Even if I did spend more than half of that month goofing off at friends' houses. Enjoy!

Ah, thanks, locking the layers will work nicely. But if anybody does know the keypress combo, it might be worth noting, as I'm sure the issue will arise same-layer at some point. It'll probably just be less common, so less vital.

Back to laying out level!

First, I'd like to say that Construct is great, and I hope the word continues to spread because I heard about it at random just a while ago, and it's exactly the kind of thing that I like.

Right now I'm designing a platformer, and would like to use invisible TiledBG objects for collisions and sprite objects on top of them for display. However, I want to resize a TiledBG that is behind a couple of sprites. The problem is, I can't click on it; clicking where I can see it in the layout editor just selects the overlapping sprite objects, since it's within the sprite's bounding box. I could move the sprite object, then resize the TiledBG, then move it back, but that'd be mighty inconvenient; especially since I need the TIledBG to be resized to be as long as the sprite objects I've got laid out right now.

So, my question is, how do I select something in the layout editor that's behind something else? If it helps, it's also on a separate Layer.