ENIGMA Development Environment

Particles would probably be best done as an extension.
Pixel-perfect collisions should go in Collision_Systems.

Catch the clown is written with EDL-specific language that is not available in GML. Notice the "alarm0--". -- is EDL, not GML. By default, when you load a GM .gmk (such as catch-the-clown), the Enigma Compiler Settings set everything to GML. This is why you are getting the error.

I've been starting to realize recently that catch-the-clown may not be the best first example, but nobody's really suggested anything better to replace it yet, so it's stuck. At the very least, it should probably be adjusted so that it works in both GML and EDL.

Anyways, to solve your problem:
Once you have opened Catch the Clown in LateralGM, you must then go into Enigma Settings (either through the ENIGMA menu, or by double clicking on the Enigma Settings tree node at the bottom left). In this subframe, you will see a bunch of radio buttons all set to the left. Switch them all to the right. This will switch you from GML to EDL. Click OK, and then go ahead and try Running again.

EDIT:
Alternatively, redownload the Catch the Clown game, as I just now updated it so that it should behave properly in GML mode.
http://dl.dropbox.com/u/9975312/Games/Catch_the_Clown.gmk

Our resident webadmin, sirmxe, has finally gotten his personal matters together long enough to log into server, uninstall and then reinstall the exim mail service, and then log back out (hopefully).

That said, the mail server works now, and some of you may or may not have suddenly got a few emails from it that it still had on queue.

I just wanted to share that the checksums have now been combined into one file:
http://dl.dropbox.com/u/9975312/enigma-dep/update.md5

Apparently you can just chain the binaries onto the end of md5sum and it outputs a newline for each, and then -c will check all lines. It still has the nuisance of outputting the relative path, but I worked around that by just CD'ing first.

Here's the new release.sh

#!/bin/sh
DB=~/Dropbox/Public/enigma-dep
WORK=~/enigma-dev

if [ "$#" -gt "0" ]; then
 echo $1 | grep l > /dev/null 2>&1
 if [ $? = 0 ]; then
  cp ws-git/LateralGM/lgm16b4.jar $WORK/lgm16b4.jar
  cp ws-git/LateralGM/lgm16b4.jar $DB/lgm16b4.jar
  echo lgm16b4.jar
 fi
 echo $1 | grep e > /dev/null 2>&1
 if [ $? = 0 ]; then
  cp enigma-dev/pluginsource/enigma.jar $WORK/plugins/enigma.jar
  cp enigma-dev/pluginsource/enigma.jar $DB/enigma.jar
  echo enigma.jar
 fi
fi

cd $WORK
md5sum lgm16b4.jar plugins/enigma.jar plugins/shared/jna.jar > $DB/update.md5

I worked around the problem of including the directories to the binaries by copying them to my working copy and then md5summing the binaries in there.

Anyways, at this point, all that's really left is the updater code. Just toying with the code, it would probably look something like this:
#!/bin/sh
url=http://dl.dropbox.com/u/9975312/enigma-dep
curl -silent $url/update.md5 | md5sum -c --quiet 2> /dev/null
# Next, trim the ": FAILED" from each line
# For each line:
#curl -O $url/$line (might need to do some splicing to not include the relative paths in the url)


Edit:
After some discussion on the IRC between TGMG (mac), bobtheblueberry (oddly), and myself (ubuntu), we've found some tools that we have in common that we might use to develop an update script.

• md5 - Mac only.
• md5sum - Ubuntu only.
• openssl md5 - Both.
• grep - Both.
• wget - Linux only.
• curl - Both.

Here's an example of openssl md5:
$ openssl md5 lgm16b4.jar plugins/enigma.jar
MD5(lgm16b4.jar)= febec82e1498ebfab21751764e2e16d3
MD5(plugins/enigma.jar)= b5f6de84285a0795ad74f03c32bccafd

The updated version yields the same results as the other two now.

surface_is_supported() returns 0.

Account Settings (top right) > SSH Keys

[bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet][bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet][bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet][bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet][bubble=red][bubble=orange][bubble=yellow][bubble=green][bubble=blue][bubble=purple][bubble=violet]TITTY SPRINKLES[/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble][/bubble]
You just read that in Morgan Freeman's voice.

Looks good to me. I can't think of any particular need for ambiguity resolution. And I don't think anybody really cares what you name it, as long as it's not too hard to remember/look up and doesn't take 10 seconds to type, like enigma::instance_event_iterator