View Single Post
Old 05-29-2019, 02:37 PM   #11
geek1011
Wizard
geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.geek1011 ought to be getting tired of karma fortunes by now.
 
Posts: 2,805
Karma: 7423683
Join Date: May 2016
Location: Ontario, Canada
Device: Kobo Mini, Aura Edition 2 v1, Clara HD
Quote:
Originally Posted by GeoffR View Post
Maybe this would work? The replacement value can be any number 0-255.
Code:
Increase TOC level indentation:
  - Enabled: yes
  - PatchGroup: TOC Indentation
  - Description: |
      The space indented Table of Contents levels are quite hard to see, as the
      difference is almost too small to easily notice.
  - ReplaceBytes: {Offset: 0x8B2FD6, FindH: 42 00 4F F0 20 01, ReplaceH: 02 22 42 43 20 21}
  # Replacement value:
  - ReplaceInt: {Offset: 0x8B2FD6, Find: 2, Replace: 6}
That should work, but then I wouldn't be able to fit the bugfix in there too.
geek1011 is offline   Reply With Quote