Developer Mode: Difference between revisions

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 was associated with the cheat code '''thedayismine''' (see picture, right). This cheat code did not work upon Oni's release, and 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, this mode is actually present in ''all'' available versions of Oni (except PS2). It just needs to be unlocked, as the community learned [[History_of_Oni_modding/The_tale_of_Dev_Mode|back in 2006]].

First, get a good hex editor. Ideally, it should allow you to search for sequences containing joker characters (that is, wildcards or bit masks). One such editor for PC is [http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm XVI32]. On Macs, [http://www.ufsexplorer.com/cihex.php CI Hex Viewer] is free, powerful, and can perform the search you need, but [http://ridiculousfish.com/hexfiend/ Hex Fiend] has a better comparison function so you can check your work afterward (open original and edited binaries and choose File>Compare "Oni" and "Oni").

|+Cheat codes and IDs

|shapeshifter

|liveforever

|touchofdeath

|canttouchthis

|fatloot

|glassworld

|winlevel

|loselevel

|bighead

|minime

|superammo

|'''thedayismine'''

|reservoirdogs

|roughjustice

|chenille

|behemoth

|elderrune

|moonshadow

|munitionfrenzy

|fistsoflegend

|killmequick

|carousel

 

;Cheat overview

:There are 22 cheat events in every version of Oni, indexed from 0 to 21 (or 0x00 to 0x15 in hexadecimal). See table on right.

:The order is the same in every version, so we can refer to the cheats by that ID, or by the cheat code used to activate the cheat event.

:When you type characters in the "pause screen", the text you enter is progressively compared with all the strings in the cheat table.

:When and if there is a match, the appropriate confirmation message is displayed for enablement or disablement (except for one-way cheats '''fatloot''', '''winlevel''', '''loselevel''' and '''munitionfrenzy''', which just have a recognition message), and the corresponding cheat event is launched when the Pause screen is closed.

;In full, each row of the cheat table consists of:

:a pointer to the cheat code string

:a pointer to the "enabled"/recognition message

:the internal ID of the cheat event to launch

There is an row for every cheat, and they appear by order of increasing ID. In most Oni builds, the developer mode cheat (ID 0x0B) is simply skipped over; '''reservoirdogs''' (0x0C) comes right after '''superammo''' (0x0A).

:In the PC, PC demo and Mac OS X (PPC) builds, every row of the lookup table takes up 16 bytes; the 3 pointers and the ID are 4-byte data words (Little Endian on PC, Big Endian on PPC Macs); if a cheat has no "disabled" message, the row's third pointer is null

:In the Mac OS 9 retail and demo, every row of the lookup table takes up 12 bytes; the 3 pointers and the ID are 3-byte data words (Big Endian); if a cheat has no disabled message, the last byte of the third element is taken up by the ID (the remaining 2 bytes are garbage, as well as the ID field)

:In the Mac OS 9 beta, the pointers and the ID are 2-byte words (Big Endian); regular elements take up 8 bytes; if a cheat has no "disabled" message, weird stuff happens to the third pointer and to the ID, and the element takes up 10 bytes... the ID can be found in what would be the first byte of the ID field.

In the PC, PC demo and Mac OS X (PPC) builds, there's extra space at the end of the lookup table and where the cheat codes/messages are stored, so one can ''add'' '''thedayismine''' as an extra cheat. On Mac OS 9, the data is packed tighter (and the text strings are stored together with their size), so the only easy way is to replace an existing cheat. Since replacing an existing cheat is the only solution that works on all platforms, the following mini-tutorial will explain how to bind the Developer Mode cheat event to the Ultra Mode cheat code, '''killmequick''' (since hardly anyone uses that cheat).