||2 years ago|
|Lua||2 years ago|
|asm||4 years ago|
|dump||7 years ago|
|img||6 years ago|
|.gitattributes||7 years ago|
|.gitignore||6 years ago|
|README.md||2 years ago|
|Yaz0.py||8 years ago|
|Yaz0_fast.pyx||6 years ago|
|chksum.py||7 years ago|
|dumptext.py||5 years ago|
|dumptext2.py||6 years ago|
|fn M US10.txt||2 years ago|
|fn O US10.txt||2 years ago|
|fn O US12.txt||2 years ago|
|heuristics.py||4 years ago|
|mm-bitflags.txt||6 years ago|
|n64.py||8 years ago|
|n64_fast.pyx||6 years ago|
|notes.md||4 years ago|
|util.py||8 years ago|
|z64crc.c||4 years ago|
|z64dump.py||2 years ago|
|z64yaz0.c||4 years ago|
|z64yaz0.new.c||3 years ago|
Zelda 64 Resources
i like to muck around in the memory of these games.
those who are more interested in the ROM may find the binary template repo more resourceful.
there is also a great deal of general documentation and notes on the wikis hosted at CloudModding.
this repo contains a ton of Lua scripts written for version 2.4.2 of Bizhawk. all the scripts you'll want to use are in the root Lua directory, and their dependencies are in further subdirectories. that means, if you want to use a script, you must preserve the directory structure. you cannot, say, extract one file from this repo's archive and expect it to work.
of these, you probably came for
this script will bind your L button to open an on-screen menu
allowing you to control many aspects of the game.
of immediate interest are the classic levitation and run-fast cheats, but also the menu of warps to any area and any entrance in the game. you can also change your Z-Targeting method to Hold in the 2nd page of the Progress menu, in case you forgot to change it in-game.
i have written a handful of ROM and RAM hacks for Majora's Mask and Ocarina of Time. these have all been written in the custom assembler syntax of lips, a MIPS assembler written in Lua. lips is included in this repository; you do not need to acquire it separately.
you only need to run
Lua/inject.lua in Bizhawk
to run the RAM hacks — that is, modifications that act
directly on the game's RAM while it runs; not modifying the ROM.
for the ROM hacks, you will need to set up a lot more. you will need:
bash 4.3 to run the shell scripts responsible for automatically running all the following software.
Python 3.4 to run the scripts responsible for splitting the ROM into files, and merging those files into a single ROM again.
LuaJIT 2.0 to run the lips assembler responsible for turning the assembly files into executable binary code. you might manage to use the Lua 5.1 interpreter, but this is not strictly supported.
gcc 4.9 or clang 3.6 to compile the programs responsible for (de)compressing the Yaz archive files, and for computing checksums.
the versions listed above are rough estimates, and newer versions of software are likely to work fine.
if you're on Windows, and you're not afraid of the (*nix) console, you can set up msys2 to install binaries of bash, python, and gcc. then all that's left is to compile LuaJIT yourself, or you can grab a 64-bit binary built by myself.
last, but not least, you will need the appropriate ROM for the ROM hack. you will probably need to change the hard-coded paths to the ROMs. (note to self: change scripts to take the required ROM as their first argument)
finally, you just run the appropriate shell scripts for the ROM hacks you want to produce. for example:
$ cd asm $ ./mm-bq zelda@srd44 00-07-31 17:04:16 uncompressed 0031 V00B3C000 ratio: 59% compressed 0031 V00B3C000 ratio: 59% compressed 1552 V02EE7040 ratio: 1% bootcode: 6105 crcs: 5CF5359C A893E696
to compile the C programs, you might need to pass
gcc -std=gnu11 -Wall -Ofast z64yaz0.c -o z64yaz0 gcc -std=gnu11 -Wall -Ofast z64crc.c -o z64crc
in the future, it'd be nice to only depend on LuaJIT to build ROMs.
cygwin's newline mangling will be the death of me.
some sheets have been put together to dump data in. some of them can be used to predict the result of glitches.
a huge laggy mess that brings google docs to its knees. this has pretty much been deprecated by the exit calculator script, which uses updated names, among other things. just load the script and type
dump_all_exits()in the Lua console, and the csv will be written to
Lua/data/_exits.csv. a 4 megabyte csv dump of all exits is also available.