Delipunch

It seemed to work fine for me in 1.12.5. Had to allow installing mis-matched version mods in CKAN first, though.

First things first, it was the principle of the matter: I mean, you at the very least implied that there's no actual log. If you wish to reproduce my results: load non-working patches. If you wish to make it easier for the uninitiated, and by extension make the whole thing more approachable: get a real log. If you wish to help me with my patches: see previous answer. (And apologies if I sound like one of those people who demand impossible levels of support: the support I want will reduce the amount of forum support by letting patch devs support themselves)

The current patch-error-reporting system does not work anywhere near optimally. So sub-optimally, in fact, that it would be better not being there in the first place. I would say that it's nice that it tells you of the error, but since that's bassically all it does, saying "it's bad" would be an understatement. In it's current state, it's akin someone who shoots down everyone elses ideas with the conversational equivalent of nukes, whilst providing zero ideas themselves, or someone saying "0m6 m4n y0ur d01n6 17 wr0n6 y0u n00b", who mysteriously loses their 'net connection everytime they're challanged (leetspeak for emphasis). Directly speaking, it's rage-inducing. Actually, I think this is the only interpreter ever to do this: every other interpreter (compilers included as they're technically interpreters themselves) will pop an window on the screen highlighting the errors even if the UI is utter scrap. To fix this, I reccomend putting the datails of the errors into the debug section of the alt+f12 menu and/or (preferably) inserting comments into the offending patch files on the end of the offending lines, saying why it's erroring.