Hello, all

I have recently been playing Time Gate Knight's Chase, where I couldn't simply sit idle and had to change the binary slightly to allow for multiple movement key options.
This brought to my mind a question I wanted to ask here: in 2026 how do you folks document / preserve the patches you make? I am personally in favor of keeping documentation as code, but have not been coping very well, in my personal opinion. Including some immediate options I can think about, but it is exactly why I am posting here - asking for options from others 😀

* keeping patching notes in a text file and building with patch maker - patch is stored as binary
* keeping patching notes in a text file and providing instructions for fpatch - patch is stored as text (but is not necessary readable or clear with regards to what it actually does!)
* writing bespoke C program based on the notes, which actually follows the text notes in its structure / code, also possibly leaving comments
* asking an LLM to write a one off bespoke C program based on the notes, which is to follow the text notes
* ...

Well, I hope you get the idea of what I am after, so please advise. Only to reiterate, I am after solutions that are native-DOS-runnable and can thus be directly brought to the target PC for patching.