Skip to content

Latest commit

 

History

History
48 lines (29 loc) · 2.08 KB

README.md

File metadata and controls

48 lines (29 loc) · 2.08 KB

patcher-in-browser

This is for the CLIphobia who wanna patch but don't wanna touch the command prompt.

screenshot

Patches format

Each line contains what to patch (hex bytes) and how to patch (offset or bytes to be searched).

Comment lines (starting with '#') are ignored. Comment should not use ~ (tilde) since it's used for serialization of patches in URL. You can replace ~ with $HOME (in path), or %7E (in URL).

Example of patching at specified offset with hex bytes:

   DEADBEEF  FE E1  DE AF
    ACE0FBA5E:  0xFE ED  C0 DE
  0xFEDD06F00D :CA FE  0xBA BE
  DECAFDAD : B0 BA  C0 FF EE
  # BAEBEE : FE EE  F1 F0

Example of searching and replacing with hex bytes:

  # FA CE  B0 0C  =0x0F F1 CE
   0xB0 0B=  D0 0D  0F  DE ED

Patches in URL

Patches are read from URL hash at start-up, such as #{"name":"Patchy-McPatchface","patches":["BADBED~DE~FE~CA~7E","BE~=~DE~FE~A7~ED","#~FADEDFAD~FAE-FEE-F00"]}

Patches are written to URL hash when the patches input lose focus.

Patches in URL can be shared easier than uploading a patch file somewhere.

Compare file to generate patches

Expand the section "Compare file (Diff hex bytes)" to generate patches for the differences between 2 files.

Limitations

  • This tool does not support extending or truncating files
  • Huge files may not be patchable (since files are loaded and patched in RAM)
  • Responsiveness is reduced when there's too many text in text input (only happen with Chrome, not FireFox)

Similar tools

Other tools that also support patches in URL: