Skip to content

Releases: DSModdingTools/CRO-Expander

3.5

Choose a tag to compare

@ABZB ABZB released this 10 Mar 01:32

Fixed off-by-one bug introduced in previous bugfix

3.4

3.4

Choose a tag to compare

@ABZB ABZB released this 06 Mar 17:34

Fixed bug resulting in crash when expanding the relocation patch table.

This was caused by the program failing to update the pointer to the .data section in the CRO header

If you already have modified file, you can manually fix this by locating the actual start of .data (it is immediately after the end of the relocation patch table), and updating the word at 0xB8 with that address.

3.3

3.3

Choose a tag to compare

@ABZB ABZB released this 30 Jan 01:48

Fixed - Insertion address when expanding the relocation patch table was being printed in decimal instead of hexadecimal.

3.2

3.2

Choose a tag to compare

@ABZB ABZB released this 20 Mar 19:07

Fixed bug resulting from now-unneeded catch

3.1

3.1

Choose a tag to compare

@ABZB ABZB released this 19 Mar 21:53
  • Bugfix, .data size was not being correctly set when there were existing unused padding bytes
  • Now can handle moving multiple tables at once

3.0

3.0

Choose a tag to compare

@ABZB ABZB released this 17 Mar 08:36

Additional functionality added:

  1. Search for a dynamic call(s) to a function (as defined in the internal relocation patch table), and point it somewhere else.

  2. Search for a dynamic reference to a table (as defined in the internal relocation patch table), move the table to another location, and update all references to said table.

Each can be searched for either by the address at which the function or table starts, or by an address that the reference is written to. Moving a table also requires that the user specify the length of the table (in bytes), those bytes will be copied to the new location, and the previous location overwritten with 0xCC. If the user wants to copy the table, a size of 0 should be used.

The primary use of moving tables is to allow them to be extended, although this will generally require that the user locate the function(s) that reference the table and update the table size there (or wherever it might be).

2.1

2.1

Choose a tag to compare

@ABZB ABZB released this 18 Feb 04:44
fcd7fc7
  1. Cleaned up .code expansion to be more efficient
  2. Added arbitrary address insertion (intended for very specific use cases)

2.0

2.0

Choose a tag to compare

@ABZB ABZB released this 16 Feb 07:21

Now can also expand .data and .bss

1.0

1.0

Choose a tag to compare

@ABZB ABZB released this 01 Jan 02:52
0ca0b3a

Initial release!