I can't figure it out either; i know that if you raise an exception in the area you can edit, it gets caught a few levels up where the toString representation of whatever you threw is parsed into status update info, with newlines interpreted correctly. But after that, even if you input chars that could build a bridge, it's not persisted to the next attempt :/

After a lot of trial, error, and attempted code injection, I found that it was much easier than I had expected. It can in fact be solved with a single character.

Hmm. Damn.

I actually figured something out with this which is weird, because I don't think it has to do with exceptions. I passed in a new object of an undeclared type and just walked across the water, which I can't explain.

Can anyone help?

I'm trying with

    player.killedBy(function(){throw new Exception();});

...but then that just means I get killed by "function(){throw new Exception();}".

Edit: never mind, got it. Overriding onCollision helps. :)

https://gist.github.com/anonymous/2868beb0cee19259ebb5

I think that's the purpose, the filename says something about "exception".

Remember in of the earlier levels when who-ever is talking to us, said that the name of the level could come in handy? Try using that ;)

The level filename is a hint.

you can close the bracket and inject some more commands… although you don’t have many characters in which to do it.

Overriding a certain method may help ;)