Small bug : Scaling while holding shift didn't work properly when i tried from the top right vertex. Not a big problem, scaled properly from the top left.

Confirmed, but I think I know why. Anytime object is rotated 90 degrees (and other rotations) via its common properties, shift-resizing goes haywire.

Let's just see how long it takes...

They come from, you guessed it, Yahoo and Google. They're archivers. They are the sole reason one day everybody who types "Oh, that crazy SoldjahBoy!" into Google is gonna come up with this page right at the top of their search results.

The States aren't as bad as the media might lead you to believe. Wouldn't give it up for anything, my friend.

Perhaps the whole point of this forum is permanence, though. In which case, yeah.. small, isolated demos would be best here. No need to have my WIP stuff held on Scirra servers.

<img src="http://www.strouperman.com/Special/screen/SS-04.22.2008-08.05.22PM.jpg">

Hahaha ^

+CONDITION

-DirectSound: Play music from file "path\to\Music.mp3";

If you use paths, be sure they are backslashes [\] in Windows.

Does that help, or are you doing something more specific?

<img src="http://www.strouperman.com/Special/screen/Programs_and_Features-04.22.2008-03.42.10PM.jpg">

Probably.

Any other limitations? If I were to use this for future iterations of my development journal, each example set is getting near 5-10 megs or so. In the case I'm willing to share a full-blown demo with sounds and high quality graphics, is this the proper venue or shall I use an alternative host?

That' a good idea, but I myself have no experience working with scripts, much less exporting and reintegrating them later. I was thinking I'd wait until the wiki had more information before I began exploring that.

Another way I've considered is through INI files, although that's much more like translating from a translation.

O, i c wut u did thar.

Actually, Why don't you just take the mathwork out of it and create "no transform" zones built into your levels?

If you're worried about overlapping a wall on one side (or two adjacent, in a corner) you can run a simple distance check in your cardinal directions. Alternatively, write a push algorithm so that your monster can transform in "safe to transform" areas without worrying how close to the wall he is.

I just think the whole "let's write thirty-thousand detectors" thing is an awful lot of work to accomplish what can otherwise be planned for and convincingly faked.

I wish I could help you, but by this point I am entirely confused. I understand if you want your project kept in the dark, but by doing so - I mean, not even giving us a hypothetical use for this - then all I see is a web of box objects set in a container and positioned/valued on creation. In a sense, I'm doing something similar in my own project. Deadeye was able to give me a boost here:

Look for the cap file. I think it might help at least the part of your problem where you want to assign container objects an ID upon creation.