The Conflict Checker is divided into files. In each one it has the patch's memory location and which location is conflicting, as well as a patch number.
There are situations where a patch appears to be conflicting with itself. It lists its own location, which I'm going to assume is the start/beginning address (i don't know proper ASM semantics), its own patch number, then a conflict location that is always very near the patch's own listed location.
Is this the conflict checker throwing a false positive due to how the patch rewrites the instructions/variables or expanded/decreased memory block size or something like that? The conflicting memory location in the situations appear to be less than/before the write location of the selected patch.
Yes
Thanks for clearing that up