I might get into the habit of just copying over the decohack directory into a src dir in the zip itself 'cause why the carp not? -- having it be a standard feature would rock, though yeah, that's a bit offtopic now. :P
There are currently no plans to copy/reform the source of a DECOHack Generated Patch into a single file of some kind (maybe DEHSRC.dh?), since I figured the source would only be relevant to those who also want to see the source of a publicly-available project.
Nonetheless, after an error-free compile, I could re-stream the multi-file source trees of a single project into a single file for WAD inclusion (a tree copy would already be okay for PK3/PKE, but more sophisticated modding languages would probably be used for those projects, anyway).
Not a focus at the time, nor is it in demand, so "Low Priority Enhancement," it is.
From a comment by @XaserAcheron in GZDoom's MBF21 bugtracking issue: https://github.com/coelckers/gzdoom/issues/1418#issuecomment-873686703
There are currently no plans to copy/reform the source of a DECOHack Generated Patch into a single file of some kind (maybe
DEHSRC.dh
?), since I figured the source would only be relevant to those who also want to see the source of a publicly-available project.Nonetheless, after an error-free compile, I could re-stream the multi-file source trees of a single project into a single file for WAD inclusion (a tree copy would already be okay for PK3/PKE, but more sophisticated modding languages would probably be used for those projects, anyway).
Not a focus at the time, nor is it in demand, so "Low Priority Enhancement," it is.