Additional findings (1.30.164014.27, Windows)
Test setup: a script calls FindFile(pattern, fileName, fileAttr, flags) and counts results via FindNextFile. The file $profile:ExampleMod/Configs/Example.json exists, and FileExist on it returns true.
Also reproducible with the retail server executable. DayZServer_x64.exe (DayZ Server Exp, 1.30.164014.27), started without -filePatching, shows the same behavior: the mod finds no files in its $profile: config folder. The detailed pattern results below were collected with DayZDiag_x64.exe (server and client), with and without -resolveFilePatchingUsingEnfusion=1. Both configurations behave identically.
FindFileFlags enum values are all 0 in 1.30. Script output: DIRECTORIES=0 ARCHIVES=0 ALL=0 (1.29: 0/1/2). Passing raw flag values 0, 1, 2, 3 or 4 makes no difference, the subfolder pattern returns no handle with any of them.
The problem is not only the discarded prefix. Subfolder patterns fail in every form:
Pattern Result
$profile:ExampleMod/Configs/*.jsonno handle
$profile:ExampleMod\Configs\*.jsonno handle
$profile:ExampleMod/Configs/*no handle
$profile:ExampleMod/*, $profile:ExampleMod*, $profile:ExampleModno handle
$profile:ExampleMod/Configs/Example.json (exact name, no wildcard)no handle
profiles/ExampleMod/Configs/*.json (relative to the working directory, where the profile folder actually is)no handle
<absolute path to profile folder>/ExampleMod/Configs/*.json (absolute path)no handle
$profile:*handle, lists the server working directory (e.g. !Workshop, addons, mpmissions), not the profile folder
$saves:*identical to $profile:*
Even root-relative and absolute paths into a subdirectory return nothing. Only a top-level wildcard returns results, and those come from the working directory. $profile:ExampleMod* returns no handle, although ExampleMod exists in the profile folder. That matches the prefix being discarded and the working directory being searched instead.
Impact example: A server mod loads its configs at startup via FindFile("$profile:ExampleMod/Configs/*.json"). On 1.30 it finds zero files, so the mod runs without its configs. Its in-game menu stays empty and never leaves its loading state. Reading and writing the same files by name through $profile: still works.