How do you "set the collision mask to bounding box", exactly? I had the same problem myself. <img src="smileys/smiley5.gif" border="0" align="middle" />

*sigh* Got it working. No idea how, but it's working. <img src="smileys/smiley5.gif" border="0" align="middle" />

Thanks for the responses and sorry for wasting your time, I guess!

Yeah, but that doesn't seem to be working either... I'd post a .capx, but there's literally nothing in the project but this one single sprite. <img src="smileys/smiley36.gif" border="0" align="middle" />

Hey all, (hopefully) a simple question here. The 16-bit sprite I'm using looks really blurry during run-time; according to one of Ashley's posts I found, this is because I put the hotspot in between two pixels, so it isn't rendering properly. However, I can't find a single place to put it that doesn't make it blurry! What am I doing wrong?

Well... In an unfortunate turn of events, it seems my decision was made for me. The new laptop I got during my hiatus has a GTX graphics card, which I'm just now learning causes massive problems with CC. That settles that, then; C2 it is. <img src="smileys/smiley24.gif" border="0" align="middle" />

EDIT: What exactly is the difference between the free version of C2 and the licensed ones? Are there sizable features missing from the free one?

Thanks for the quick replies everyone. I'll check out the free version of C2 and see for myself. :)

I worked extensively with Construct Classic and was in the middle of my first huge project when C2 was announced. Needless to say, I was in a bit of quandary trying to decide whether or not to start over in the new program or keep working with the old one. My ultimate decision? Neither. I kinda just stopped working altogether. <img src="smileys/smiley18.gif" border="0" align="middle" />

So my question is, many months later, is C2 up to the functionality of Classic yet? Would I be better off sticking with Classic, jumping over to C2, or waiting even longer for C2 to catch up?

Gahh, I did the same exact thing when I started out! Took me forever to get all of it back. Turns out that you can click the buttons in the Home tab at the top to bring them up again -- the Layout, Project, Properties, Objects, and Animator tabs will all be back where they should be.

Alternatively, I think deleting the persist file will have the same effect. The Persist file saves settings for you, like where you placed the tabs and such, so everything looks the same when you open up the cap file again. If you delete the persist, everything will go back to its default settings.

Hopefully one of these will work out fine for you. Don't worry about the mistake -- like I said, I did the same thing.

The editor isn't always entirely intuitive at times, so you might just have to work around this. I'm not an expert of course, so a solution might exist somewhere out there.

Welcome to Construct, by the way.

You can invert conditions if you right click them, so make another condition where they overlap and invert it. An inverted "This overlaps this" means "This doesn't overlap this".

Alright, I think I get what you mean. You want the sound to keep playing while the spell is over the enemy, and then stop once it's off, right?

That's a little trickier than a normal sound effect, but it's doable. You should load the second effect into a specific channel first and set it to loop(make sure the effect actually sounds good when looping!), and play it while the spell overlaps the enemy. Add another condition that says when the spell DOESN'T overlap the enemy, stop playing that channel.

It's possible there's a simpler way to do it, but I did a similar thing in my own game using this and it works fine.

but how do I make it so the sound doesn't play once the object has gone off the other object?

Not quite sure what you mean by this. Are you not destroying the bullet when it hits the object in the first place? If you aren't, you probably should (unless you're not doing it on purpose), but either way the problem would probably be solved by using the Trigger Once condition.