Skip to content

Conversation

@OperationNT414C
Copy link

@OperationNT414C OperationNT414C commented May 8, 2016

V6
Minor fix for background load
Default offset 0x12000 is also added if the binary is directly started for File Browser

V5
Update fatfs to fix File Browser illogical crashes (for example, if the background was not set to black)
Add a default offset at 0x12000 if a ".dat" file is added to entries through File Browser

V4
Displays the number of binary patches for current entry (if there is at least one patch)
Add the possibility to set transparency for borders and fonts
Fix a crash on start if no config file exists

V3
Add the possibility of binary patching, limited to 4 for each entry
New keywords for config file to support binary patching:

  • "patchMemSearch" represents the searched pattern in hexadecimal values (730064006D0063003A002F00 => sdmc:/ with null value between each letter)
  • "patchMemOverwrite" represents the values which will overwrite the found pattern (in hexadecimal values)
  • "patchMemOverwriteStr" represents a string which will overwrite the pattern (it replaces "patchMemOverwrite" usage)
  • "patchMemOverwriteWStr" represents a string with wide characters (null value between each character) which will overwrite the pattern (it replaces "patchMemOverwrite" usage)
  • "patchOccurence" represents the occurence to modify: if the pattern can be found multiple times in the loaded binary file, only the indicated occurence will be overwritten (0 means all occurences will be overwritten)
    A patch of an entry MUST always end with "patchOccurence" (it is like an entry which must always end with "key").

V2
Add screen-init support

@OperationNT414C OperationNT414C changed the title Screeninit support Screeninit/binary patching/full alpha support May 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant