Developer Mode

Developer Mode is the unrestricted version of the Console, which allows every command available in scripts able to be executed in real time. It's intended purpose is to allow debugging of levels, such as reviewing script variables, teleporting ahead in the level, and generally forcing unusual conditions. The primary use for many people, however, is the ability to execute cheat commands, which allow features such as deathless, super jumping, or becoming another character.

Depending on your version and third party addons, you will likely not be able to engage in Online Multiplayer while Developer Mode is active; only LAN, or Singleplayer gameplay.

Activating Developer Mode


To launch Halo Custom Edition with Developer Mode, all you need to do is add parameters to Halo's startup; if you're running from a shortcut, which you likely are, this is quite easy.

Right click the shortcut, properties, and under the shortcut tab, you simply add the parameters at the end of the Target textbox. To enable Developer Mode, you require console as well, and depending on your addons, the console parameter may potentially enable developer mode as well.

Simply add

-console -devmode to the end of your Target.

Using Developer Mode
By pressing the ~ key (Located on your keyboard, top left, directly under the escape key) while halo is running, you will access the Console; Developer Mode is just full access to all commands in the console.

At this point, you can start using any script commands, or adjust any global variables. If you press tab, it will suggest results, and begin auto-completing. For instance, if you write cheat_ then press tab, it will suggest options such as cheat_deathless_player, cheat_bottomless_clip, etc. This only works for built in commands and globals however. If you have your own custom global variables for your map, they will not autofill; you need to remember their names.

Effecting Scripts from Developer Mode
If you are testing a singleplayer map, and just want to jump ahead to a certain location, you may have to startup scripts for that portion of the map. Or, you may just want to test a certain script.

Pausing a Script
The sleep command, will delay a scripts execution, in Ticks (seconds * 30). if you give it -1, it will stop the scripts execution completely, and the script will act like a dormant script.

Starting a Script
If a script is a dormant (or, acting as a dormant, due to sleep -1), the Wake command will begin the scripts execution. This can also bypass any other types of delays, such as if someone had set the script to sleep_until some condition, that would restrict the player until an objective was complete.

Executing Static Scripts
unlike the scripts, where you can just call a static script, like another script command, when in Developer Mode, you must make use of the Begin script command first. If my script was replace_random_objects, I would execute it as begin (replace_random_objects)