From 0f7ba1dd309870475fad4ddfafd9ed6d22e6a0bf Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Thu, 15 Jan 2026 01:49:31 -0800
Subject: [PATCH] Updated Patching DLLs (hex edits) (markdown)

---
 Patching-DLLs-(hex-edits).md | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/Patching-DLLs-(hex-edits).md b/Patching-DLLs-(hex-edits).md
index 0b0e2f6..16e0878 100644
--- a/Patching-DLLs-(hex-edits).md
+++ b/Patching-DLLs-(hex-edits).md
@@ -31,15 +31,6 @@ Launch `spicecfg.exe`. Open the patches tab. Make sure that the datecode and mod
 
 If you are using batch scripts to launch games, make sure you are using the same `-modules` parameter when you launch `spicecfg.exe` as you would for `spice.exe` or `spice64.exe`.
 
-### Available patch sources
-
-Visit the following pages for instructions.
-
-* BemaniPatcher for spice2x - https://djtrackers.github.io/BemaniPatcher
-* two-torial patcher - https://sp2x.two-torial.xyz/
-
-These are maintained by separate entities and **not** associated with spice2x developers.
-
 ### Hard Apply Patches
 
 While not required, patches may need to be written to the module in certain circumstances. With the `Hard Apply` option, spice2x writes the patches to the module after making a backup to `{module}.bak`.