Shenmue II (for Dreamcast) uses "event scripts", which are loaded on-the-fly, in order to perform most of the game logic, called EV1/2/3.

This repository provides tools (essentially a cross-compiler) which will allow a developer to write their own EV1/2/3 scripts which can be used on the game, using gcc and binutils.

gcc-11.3.0

binutils-2.38

• Run the following to install the necessary packages used for the rest of this guide: sudo apt-get install binutils-dev build-essential gcc g++ make cmake patch flex bison gettext libgmp-dev libgmp3-dev libmpc-dev libmpfr-dev

NOTE: Some users have reported issues when running make -j (all cores), change as per your system dictates if you get any issues. 4 threads is probably enough.

1. Retrieve and unpack the above source code (gcc & binutils) and insert the following lines into ~/.bashrc, using something like nano ~/.bashrc.

   export PREFIX="$HOME/opt/dc"
   export TARGET=sh4-elf
   export PATH="$PREFIX/bin:$PATH"
   

   (the build process usually creates $HOME/opt/dc for you, but feel free to make it yourself)

2. Either restart your terminal or execute . ~/.bashrc to make the above changes take effect immediately and run

   sudo apt-get -y update && sudo apt-get -y upgrade
   

3. Execute the following commands to build and install binutils for the sh4-elf target:

   cd binutils-2.38
   mkdir build
   cd build
   ../configure --target=$TARGET --prefix="$PREFIX" --with-sysroot --disable-nls --disable-werror --disable-libssp --disable-tls --disable-shared --enable-static
   make -j
   make -j install
   

4. Execute the following commands to build and install gcc for the sh4-elf target:

   cd gcc-11.3.0
   contrib/download_prerequisites
   mkdir build
   cd build
   ../configure --target=$TARGET --prefix="$PREFIX" --enable-checking=release --enable-languages=c,c++ --with-cpu=m4-single-only --with-multilib-list=m4-single-only,m4-nofpu,m4 --with-endian=little --without-headers --disable-libssp --disable-tls --disable-shared --enable-static --disable-nls
   make -j all-gcc
   make -j all-target-libgcc
   make -j install-gcc
   make -j install-target-libgcc
   

You should now have a working development environment to run make in any of the directories in this repository.

Building the scripts is as easy as invoking make in a directory containing the included sample Makefile. In order to build..

an EV1:

  make -j TYPE=EV1

an EV2:

  make -j TYPE=EV2

an EV3:

  make -j TYPE=EV3

These commands will build EV* scripts which use the physical address of the Dreamcast system RAM. This doesn't work for Retail builds of the game for obvious reasons and so to compile and run EV* scripts for use on Retail builds of the game, it's necessary to add RETAIL=1 to the make command and to also add a 'P' to the TYPE name, for example, to build an EV3 for use on a Retail build:-

  make -j TYPE=EV3P RETAIL=1

There are two ways to use these:

If you are overwriting an existing script, then it is best to use the correct EV*.

For example, if the script you are overwriting is an EV1, then you should compile with make -j TYPE=EV1.

When creating a new area, EV3s are usually loaded with the same name as the area. More details will come at a later date.

After (re-)placing the script in its appropriate location, build the GDI up with something like GDIBuilder.

Initial testing with the toolchain indicated that -fPIC seems to be working for the most part, but this needs more testing. It may be possible to alleviate the need of ensuring the scripts are compiled with the relevant VMA through the use of -fPIC.

There are a few limitations and unresolved issues which still require some work.

• the examples and SDK code currently uses hard-coded function offsets which means it only supports the build i am currently working on. we can change this to use the event function table and using only indexes for that table, which will give us compatibility with all known Shenmue 2 Dreamcast builds. - Moved all functions which can be into inlined functions which calculate the fn address before calling. Should support all builds now (tested with US and GameJam and JP retail). Retail should be -basically- supported now.
• absolutely no support for tasks with parameters and completely missing any heap space memory management functions. this is useful for sharing data between tasks etc. - Completed this a little while back but forgot to update the README.
• the function calls in the simple example are probably 90% not required/useful, so tracking down the function responsible for relinquishing control back to the user and ultimately removing the loading screen needs to be identified. - Done, 2 functions out of the 7-8 are responsible for removing the loading screen and relinquishing control. Edited dev_load_scene.
• the location of start (the entrypoint) needs to be fixed at 0x0. this can be done thru linker flags. for now, any pure functions defined by our code must be explicitly forward declared and must be placed after start to ensure that it is always at 0x0 in the resulting binary. - Written up a simple linker script which puts .text.main above everything else. Should be fixed now.
• ... and likely countless more, except these are the most important for now.

Event scripts in Shenmue II are limited by their size. The size constraints are as follows:-