From 5e13f11e3f4d0c945f97c686a151cf87ac6d4c9c Mon Sep 17 00:00:00 2001
From: Abdessamad Derraz <3028866+Abdess@users.noreply.github.com>
Date: Tue, 10 Nov 2026 12:21:10 +0100
Subject: [PATCH] docs: say what GZDoom's FileSearch serves

RetroDECK writes bios/gzdoom into [FileSearch.Directories]
(gzdoom/rd_assets/rd_config/gzdoom.ini:19). BaseFileSearch reads that
list after the program directory for the engine pk3s, and for -file,
-deh, -bex and zvox.wad (src/common/utility/findfile.cpp:224-296).
IWADs come from IWADSearch.Directories and their Load files from the
IWAD's folder (src/d_iwad.cpp:456-476, 613-624, 877-901), so no entry
of the profile is read from bios/gzdoom and nothing is bound.
---
 emulators/gzdoom.yml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/emulators/gzdoom.yml b/emulators/gzdoom.yml
index 026507747..94a554604 100644
--- a/emulators/gzdoom.yml
+++ b/emulators/gzdoom.yml
@@ -30,6 +30,14 @@ notes: |
   The last three are skipped for shareware IWADs and with -noextras.
   ref: src/d_main.cpp:2050-2071
 
+  BaseFileSearch tries the program directory first for these resources, then
+  the name as given, then each FileSearch.Directories path. The same search
+  serves -file, -deh and -bex arguments and zvox.wad. IWADs are not looked up
+  there: candidates come from the IWADSearch.Directories paths, and the Load
+  files of an IWAD block from the IWAD's own directory.
+  ref: src/common/utility/findfile.cpp:106-115, 224-296,
+       src/d_main.cpp:1802-1803, 2083, src/d_iwad.cpp:456-476, 613-624, 877-901
+
   Game data is a user-supplied IWAD. iwadinfo.txt declares each known
   IWAD with its IWADName, MustContain lumps and support files. The
   search directories are scanned for the file names of its Names block