Disassembly of Legend of Zelda: Links Awakening DX
Go to file
2022-12-05 22:27:31 +01:00
.circleci Use RGBDS v0.6.0 Docker image for CI 2022-10-15 00:11:23 +02:00
docs docs: add some documentation 2021-04-15 08:40:25 +02:00
revisions Clarify the relationship between Unicode, ROM codepoints, and tile addresses (#491) 2022-11-30 15:00:37 -08:00
src Merge pull request #494 from zladx/dialog-constants 2022-12-05 22:27:31 +01:00
tools tools: remove mgbdis submodule 2022-11-15 21:49:37 +01:00
.editorconfig tools: add an editorconfig file 2020-08-17 16:33:40 +02:00
.gitignore Update gitignore to use *.sav instead of game.sav 2020-07-06 04:28:13 -07:00
ladx.md5 Build all revisions 2020-06-17 15:14:30 +02:00
Makefile Makefile: track attrmap in revisions 2022-11-23 16:45:20 +01:00
README.md Fix typo in README.md 2022-10-09 20:11:45 +02:00

Links Awakening DX Disassembly

Disassembly of one of my favorite games. Taking it easy for now.

It builds the following ROMs:

  • azlj.gbc (Japanese, v1.0) md5: f75874e3654360094fc2b09bd1fed7e8
  • azlj-r1.gbc (Japanese, v1.1) md5: 6d8f9cd72201caabdfd0455a819af9ce
  • azlj-r2.gbc (Japanese, v1.2) md5: 2e2596c008d47df901394d28f5bd66ec
  • azle.gbc (English, v1.0) md5: 07c211479386825042efb4ad31bb525f
  • azle-r1.gbc (English, v1.1) md5: ccbb56212e3dbaa9007d389a17e9d075
  • azle-r2.gbc (English, v1.2) md5: 7351daa3c0a91d8f6fe2fbcca6182478
  • azlg.gbc (German, v1.0) md5: e91fd46e7092d32ca264f21853f09539
  • azlg-r1.gbc (German, v1.1) md5: b0080c2f1919a4bb0ea73b788f4a6786
  • azlf.gbc (French, v1.0) md5: 1043fd167d0ed9c4094e3c9d8e757f1e
  • azlf-r1.gbc (French, v1.1) md5: 68242187b65166b5f8225b20e2021659

Additionally, a wiki includes a high-level overview of the game engine, and technical informations on the data formats used throughout the game.

Usage

  1. Install Python 3 and rgbds (version >= 0.5.0 required);
  2. make all.

This will build both the games and their debug symbols. Once built, use BGB to load the debug symbols into the debugger.

How to contribute

  1. Fork this repository;
  2. Find a little piece of code to improve:
  • Maybe a typo, a missing constant, an obvious label that could be renamed;
  • Or start following a thread (Link's animations? The island fade-out special effect? Trading items constants?) and document some details along your read;
  • You can also look at the known improvements especially good first issues;
  1. Submit a pull request.

Having questions, or do you need help? Join the discussion on Discord. You can also read disassembling How-Tos in the Wiki, for some infos about the tools and disassembling processes.

Resources

Contributors

Thanks to these people for contributing:

(See contribution details here)