Users can exit a function early. There needs to be a method that prevents this.

[ghost]

Oh, just that I did find a clever hack, but it's complicated.

var stuff = function() {
        // Separate the definitions so you can't exit the function
        var behaviorFn = function(me) {
            // <edit>

            // </edit>
            // END
            // ***
        };

        map.defineObject('startDrone', {•••});
        // just some security in case you exit the behaviorFn
        var check1 = behaviorFn.toString().replace(/\n/g, ' ');
        var check2 = stuff.toString().replace(/\n/g, ' ');
        if (!(/E(N)D(.*)\*\*\*/.test(check1))) {
            throw "Function ends too early";
        }
        if (/(\*\*\*).*(E(N)D)/.test(check2)) {
            throw "You can't trick my code into exiting early";
        }

    };
    stuff();

behaviorFn is the code I'm trying to protect. It is used in the definition of startDrone.

But since startLevel is protected, perhaps we level creators could have #START_OF_PROTECTED_FUNCTION# and #END_OF_PROTECTED_FUNCTION# in our levels?

Oh yeah, two AWESOME levels coming up when this is resolved. One is called droneRelay.jsx, you will have to pass the key through four drones before finishing.

[zhykzhykzhyk]

No, not really.

var behaviorFn = function(me) {
            // <edit>
}
// GET OUT OF THE FUNCTION!!!
behaviorFn = function (me) {
            // </edit>
            // END
            // ***
};

[pppery]

The protection of startLevel is only security through obscurity.