From 4d8f9053de8613aa2f9534aa66f8b1fe33fbcacf Mon Sep 17 00:00:00 2001
From: sp2xdev <127630192+sp2xdev@users.noreply.github.com>
Date: Sun, 17 Aug 2025 08:32:22 -0700
Subject: [PATCH] Updated patches.json specification (markdown)

---
 patches.json-specification.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/patches.json-specification.md b/patches.json-specification.md
index c03c14d..94b5f19 100644
--- a/patches.json-specification.md
+++ b/patches.json-specification.md
@@ -97,7 +97,7 @@ The `peIdentifier` is then produced by concatinating the 3-character `gameCode`
 
 For instance, if `gameCode = LDJ`, `TimeDateStamp = 0x64EF0FF5`, and `AddressOfEntryPoint = 0x1037754`, then `peIdentifier = LDJ-64ef0ff5_1037754`.
 
-We use the timestamp and the entry point offset as opposed to a file hash, since files can be pre-patched by other tools, and can have additional sections added (e.g., for translations). We also explicitly do not use the game datecode since that information does not come from the DLL but rather a separate XML file, which is often incorrect on people's setups.
+We use the timestamp and the entry point offset as opposed to a file hash, since files can be pre-patched by other tools, and can have additional sections added (e.g., for translations). We also explicitly do not use the game datecode since that information does not come from the DLL but rather a separate XML file, which is often incorrect on people's setups. The filename of DLLs are not used either to identify contents since there are scenarios where DLLs are renamed (e.g., `bm2dx_omni.dll`)
 
 ## Example
 URL `https://spice2x.github.io/patches/` is available with: