Developer Mode
|
|
Developer Mode is a bundle of features created by Bungie West to help them develop Oni -- a console, camera controls, and various debugging features -- that is available via the thedayismine cheat code. It was long believed that Developer Mode had been cut from retail versions of Oni; it had only been observed to work in the Mac beta that was leaked around the time of Oni's beta testing. However, the this mode is actually present in all available versions of Oni (except PS2). It just needs to be unlocked, as the community learned back in 2006.
Below you will find download links, unlocking instructions, and finally an overview of the Developer Mode's features.
Getting it to work
Download it...
In Windows, you can install the Daodan DLL to unlock Developer Mode. On the Mac, the Intel build has Dev Mode unlocked; it can be found HERE.
Using it
First check
Cheats are normally unlocked when you finish the full version of the game. For unlocking cheats "manually" (especially necessary with the demos), see HERE
Let's say cheats are enabled and Developer Mode has been made available via the thedayismine cheatcode (or simply x with Daodan DLL installed).
Just type the Developer Mode cheat and watch for the confirmation message. However, you may not notice anything special when you get back to the game (although there should be occasional console messages appearing at the bottom-left).
The quickest way to tell whether Dev Mode definitely works, right after you get the confirmation message, is to exit the Diary screen and to press End. That should teleport you to where the camera is (usually back and up, possibly through walls and ceilings).
Here's another quick test, meant to see if the Control and Alt keys work fine (on Mac, use the Option key instead of Alt): Ctrl+Shift+U and Ctrl+Alt+U should both perform the "unstick" action; Konoko will shift forward by a small amount.
Console output
In Developer Mode, Oni prints debug messages about in-game events along the bottom-left of the screen. Past messages scroll up across the screen and fade. In some situations, messages don't fade (e.g. if character debugging is enabled or you are currently using the console line).
The easiest way to check whether that output works at all is to press F8: the character class change is acknowledged with a console message.
If you don't see anything, that means console output is unfortunately disabled in your version of Oni. If you're on PC retail, you may have applied Ian's patch (aka XP patch), which disables console output. On PC demo, both console output and console input are invisible (i.e. you can enter script commands, but you're "blindfolded").
Console input
By default, Oni auto-binds the "console" toggle to the key which on U.S. keyboards has a grave accent, `, in the lowercase position and a tilde, ~, in the uppercase position. It is usually called the "tilde key" by users, and perhaps even elsewhere on this wiki; however, you would have to hold Shift to type a tilde, and the console is activated by just pressing the key without Shift, thus it is actually the "grave accent key" which activates the console. On non-U.S. keyboards, that key may not be recognized. Just add a line like "bind leftalt to console" to key_config.txt in your Oni folder and you'll be able to open the console with that key. In some cases, this bound key will not close the console; however, pressing the grave accent key, oddly enough, may work.
Usage
Hotkeys
| Hotkey (can use Alt for Ctrl) | Description | Windows | Mac |
|---|---|---|---|
| Cntl+Shift+o | Occl Makes console screens disappear |  |
|
| Cntl+Shift+i | Invis | ||
| Cntl+Shift+y | Displays FPS | |
|
| Cntl+Shift+t | Char Collision | ||
| Cntl+Shift+r | Obj Collision | ||
| Cntl+Shift+f | Fast Mode (runs Oni at up to 24x) | |
|
| Cntl+Shift+g | Slow motion | |
|
| Cntl+Shift+x | Secret X / (Mac only) Show trigger volumes | ||
| Cntl+Shift+y | Secret Y | ||
| Cntl+Shift+z | Secret Z | ||
| Cntl+Shift+Ins | Add Flag | ||
| Cntl+Shift+Del | Delete Flag | | |
| Cntl+Shift+u | Unstick player | |
|
| Cntl+Shift+n | Camera Record | ||
| Cntl+Shift+m | Camera Stop | ||
| Cntl+Shift+, | Camera Playback | ||
| ? | Place Quad | ||
| ? | Place Quad Mode | ||
| Ctrl+Shift+\ | Profile Toggle | ||
| Cntl+Shift+l | Dumps a screenshot every frame | |
|
| Ctrl+Shift+1 | Test One | ||
| Ctrl+Shift+2 | Test Two | ||
| Ctrl+Shift+3 | Test Three | ||
| Ctrl+Shift+4 | Test Four | ||
| Return/Enter | Camera Control 3 modes Normal, Detached 1-mouse controls aim Detached 2-mouse controls camera (When activated the following applies) |
|
|
| / | Single Step | ||
| Cntl+Shift+Home | Toggle active camera; Freeze raycasting | |
|
| . (period) | Single Step Mode | ||
| End | Warp to camera | |
|
| Cntl+Shift+k | Kill Particles | ||
| Backspace | Kill Particles | ||
| 7 | Explode One | ||
| 8 | Explode Two | ||
| 9 | Explode Three | ||
| 0 | Explode Four | ||
| Cntl+Shift+j | Reset Particles | ||
| Cntl+Shift+w | Drop Flag and Add Waypoint | ||
| Cntl+Shift+b | Shows current opponent's logic | |
|
| ] | Freeze | ||
| [ | Frame Advance | ||
| Cntl+Shift+s | furnitures' textures (turns red) | |
|
| F8, Shift+F8 | Cycle characters | |
|
| Cntl+Shift+p | Perf Particle | ||
| Cntl+Shift+; | Perf Particle Lock | ||
| = | Screenshot | ||
| F2 | Cutscene 1 | |
|
| F3 | Cutscene 2 | |
|
| F6 | Kill All AI | |
|
| Ctrl+F7 | Play dead | |
|
| Fkey7, Shift+Fkey7 | Cycle weapons (holster to get second weapon) | |
|
| Fkey9 | Start recording | |
|
| Fkey10 | Stop recording | |
|
| Fkey11 | Playback recording | |
|
| ` (grave accent) | Displays console | |
|
|
Move camera left | |
|
|
Move camera right | |
|
|
Pan camera right | |
|
|
Move camera backward | |
|
|
Pan camera left | |
|
|
Move camera forward | |
|
|
Move camera up | |
|
|
Move camera down | |
|
|
Pan camera up | |
|
|
Pan camera down | |
|
Runtime scripting
Basic idea
(Almost) anything you write in scripts you can enter at runtime with the console. The only thing you can't do is register new variables and functions.
You can call existing functions, check on the values of existing variables. "Existing" means either built-in ones, or part of the original level logic, or part of your own scripts for the given level.
If a function/variable was succesfully registered by Oni during level load, you will be able to refer to them from the console.
You will even be able to browse the registered variables/functions with the Tab key, while typing at the console. Tab autocompletes the command being typed, then cycles through all available commands in (hex)alphabetical order (A...Z come before a...z). Shift+Tab lets you go back.
Previous commands can be navigated with up and down arrows. You can't insert/delete text in the middle of a command : you have to use Backspace.
The only keys that have an effect while the console is active are : Escape, Enter, Backspace, (Shift+)Tab, ASCII character keys and the arrow keys.
If you press an illegal key during console input (such as F1), the input display will freeze : hit Tab a few times to fix.
Limitations
Obviously, if you have no console output, it's a bit frustrating. Even more so if console input is invisible : you're in for some blindfolded scripting then. Still there are a few commands which you can type in as complements to regular cheats :
- chr_nocollision 0 1 and chr_nocollision 0 0 enable/disable no-clipping. When in no-clipping, you can't fall down : jumping makes you flail in midair, and eventually you die (so be careful about that)
- give_powerup shield gives you a force shield (which you can't have with fatloot)
- dump_docs prints all the registered commands/variables to a file in your Oni folder (so you know just what you can type)
- other stuff...
Also, the available scripting commands may be limited in your version. The most commands are on PC retail, or on beta 4 and earlier. On Mac, the functionality is much more limited (see HERE for details).