Added rule to prevent trivial patching as a solution (#135)

* Added rule to prevent trivial pacthing as a solution

* Better rule writing for preventing patching

Author: 3rdit

templates/rules/crackmerules.html

@@ -44,6 +44,8 @@ <h3>Requirements</h3>
 
             <li><b>Don't stack unrelated protections.</b> Each protection layer should serve a purpose and contribute to learning.</li>
 
+            <li><b>Patching is not a valid solution.</b> Do not allow patching (e.g., changing a JNZ to JZ) as a valid solution type for your crackme. Solutions should require understanding the algorithm, finding a valid key/serial, or writing a keygen. If your challenge is specifically themed around patching, ensure it requires non-trivial analysis to find the correct patch locations.</li>
+
             <li><b>Educational purpose only.</b> No cracks/keygens for commercial software, game trainers, or DRM circumvention tools.</li>
 
             <li><b>Maximum file size: 5 MB.</b> Compress multiple files into a single archive. Do NOT password-protect it (server handles this).</li>