This repository contains all C code for "Strung Up By Sketches". Please note that this is rushed game jam quality code, and that only my code (techticks') is included.
To use this project, download Strung Up By Sketches, apply the patch to a US ROM and place it under rom.nds
in the root directory, then continue with the original c-of-time setup instructions linked below.
An environment for hooking and linking to Pokémon Mystery Dungeon: Explorers of Sky.
This project is loosely based on EternalCode's template. The build configuration is based on scripts provided by devkitPro. The patch format was inspired by Starlight.
Special thanks to UsernameFodder for the pmdsky-debug project, End45 for the ExtraSpace patch and irdkwia for their research on item, move and special process effects.
c-of-time can also be used with Rust projects. If you want to use Rust (including mixed Rust + C projects),
continue reading the README.md
in the rust
directory.
If you want to build pure C projects, continue below.
- Install Python and devkitpro.
- If you're using Windows, follow the next steps within MSYS (refer to the installation guide for instructions on how to launch it)
- On Unix platforms, you might need to relaunch your terminal after the installation
- After you've followed the devkitpro installation guide, add the Nintendo DS modules with
sudo dkp-pacman -S nds-dev
. - Clone this repository recursively with
git clone --recursive https://github.com/tech-ticks/c-of-time.git
. Make sure that you enter the correct directory before continuing (e.g.cd c-of-time
). - Install Python dependencies:
pip3 install pyyaml keystone-engine ndspy
- Patch a Pokémon Mystery Dungeon: Explorers of Sky ROM with the
ExtraSpace
patch by End45. You can apply the patch with SkyTemple:- Open the ROM in SkyTemple
- Click ASM Patches and switch to the Utility tab
- Select the ExtraSpace patch and click Apply
- Place the ROM in
[project root]/rom.nds
- US ROM offsets are used by default. If you're using a EU ROM, change the
REGION
variable inMakefile
toEU
.
- US ROM offsets are used by default. If you're using a EU ROM, change the
To build the project, run make patch
. This command will build your code, inject it into an overlay in the provided ROM and apply the patches in the patches
directory. The output ROM will be saved as out.nds
by default.
If you want to check the generated assembly, run make asmdump
. A file out.asm
will be generated, which contains an assembly listing annotated with the corresponding source code lines.
Patches can be added to .cotpatch
files inside the patches
directory. These patch files contain offsets into functions that should be patched and assembly instructions, which allow calling into custom code. See src/main.c
and patches/patches.cotpatch
for examples.
You can use the logging macros COT_LOG
, COT_WARN
and COT_ERROR
. To view the logs, open the ROM in the SkyTemple debugger and check "Game Internal" in the log window. A macro for assertions COT_ASSERT(expr)
is also available.
To disable assertions and logging globally and save some performance, change RELEASE_CONFIG
in Makefile
.
To create custom special processes, add them into the switch
statement in CustomScriptSpecialProcessCall
. This function is only called for special process ID 100 and greater for compatibility with existing patches.
You can add custom item or move effects in CustomApplyItemEffect
and CustomApplyMoveEffect
.
This project aims to keep compatibility with existing patches for move, item and special process effects to some degree. Special process effects using the ExtractSpCode
patch can be reused without problems if they were imported with an ID lower than 100. Compatiblity with the ExtractMoveCode
has not been thoroughly tested yet and might potentially cause issues with the Metronome move.
To update symbol data from pmdsky-debug
, run git submodule foreach git pull origin master
,
then clean the build with make clean
.
If you've found symbols that are currently missing, consider contributing them to pmdsky-debug. You can find instructions in the repository's contribution docs.
For quick testing, you can also add symbols to symbols/custom_[region].ld
(symbols/generated_[region].ld
is auto-generated and should not be modified). You need to specify the file each symbol belongs to in comments:
/* !file arm9 */
MyCoolFunction = 0x200DABC;
/* !file overlay29 */
SomeDungeonFunction = 0x22DEABC;
SomeOtherDungeonFunction = 0x22DEEFF;
The built code gets injected into the custom overlay 36. The entire overlay is 228 KB big, most of which is reserved for common patches provided by SkyTemple. Your code will be placed in the last 32 KB, which are considered the "common area" . If the binary is larger than 32 KB, you will get the following linker error:
error "section '.text' will not fit in region 'out'"
To work around this issue, you can extend the space allocated in the overlay. If you decide to extend the space, you do so at your own risk. Be careful since this space might be used by future patches! Check the list of assigned areas to find out if patches used in your ROM are affected.
To extend the allocated space, open linker.ld
and edit the following line:
out : ORIGIN = 0x23D7FF0, LENGTH = 0x8010
Subtract the amount of additional bytes you want to allocate from ORIGIN
and add them to LENGTH
. Next, open patches/patch.py
and set START_ADDRESS
of the top of the file to the same value as ORIGIN
in the linker script. Note that the resulting address must be aligned to 16 (ORIGIN % 16 == 0
).
You can also change the compiler flags to optimize for size instead of speed. To do so, set OPT_LEVEL := Os
in Makefile
. Effectiveness varies per project.
- Build scripts (everything under the
tools
) are licensed under GPLv3. Review the fileLICENSE_GPLv3
for more information. - All other code is licensed under MIT. Review the file
LICENSE_MIT
for more information.