Description
We're thinking about snapshots.
It occurs to us that, since snapshots are typically rather small incremental updates, it makes no sense to have all the patch files duplicated and practically identical across all versions leading up to a major release.
Take for example, the difference between 1.19-pre1 and 1.19-rc2. There were only about 60 files out of 188 that had changed between these versions, and most of those were simply line bumps. (another issue is incoming related to that)
What we'd like is some sort of incremental system, where the patch application process would start in the current project folder and walk backwards until it finds a suitable patch file to use.
A suitable file with size 0 will represent a removed patch, in case Mojang delete a file or so.
This will clean up the repo greatly, and aid in the process of creating bulk MCPConfig releases for snapshots.