Follow-up finding — corrected and more precise than my earlier comment. This is not specifically about dependencies; it's broader.
I ran a fully isolated set of tests:
Resource pack only, no behavior pack active in the world at all: works correctly. Client receives the download prompt, downloads the full pack (80MB in this test), and it shows Active in-game.
Same resource pack, with any behavior pack active in the world (regardless of whether the resource pack actually declares a dependency on that behavior pack): resource pack delivery breaks completely. No download prompt, no download queue, no console log entry for the resource pack at all, and it never shows Active in-game. This happened even for a resource pack with zero dependencies field and no relationship to the active behavior pack.
The behavior pack itself always loads and logs correctly in the console regardless.
So the actual bug appears to be: the presence of any active behavior pack in a world silently prevents ALL resource packs from being offered/delivered to clients, independent of whether those resource packs declare any dependency on that behavior pack. This is more severe than a dependency-resolution bug — it effectively means resource packs and behavior packs cannot be used together at all in a world on this server version.
This matches everything observed throughout my original setup: every world I tested had at least one behavior pack active, and in every case, all resource packs failed silently regardless of their individual configuration.
Jono parsons
Follow-up finding — corrected and more precise than my earlier comment. This is not specifically about dependencies; it's broader.
I ran a fully isolated set of tests:
Resource pack only, no behavior pack active in the world at all: works correctly. Client receives the download prompt, downloads the full pack (80MB in this test), and it shows Active in-game.
Same resource pack, with any behavior pack active in the world (regardless of whether the resource pack actually declares a dependency on that behavior pack): resource pack delivery breaks completely. No download prompt, no download queue, no console log entry for the resource pack at all, and it never shows Active in-game. This happened even for a resource pack with zero
dependenciesfield and no relationship to the active behavior pack.The behavior pack itself always loads and logs correctly in the console regardless.
So the actual bug appears to be: the presence of any active behavior pack in a world silently prevents ALL resource packs from being offered/delivered to clients, independent of whether those resource packs declare any dependency on that behavior pack. This is more severe than a dependency-resolution bug — it effectively means resource packs and behavior packs cannot be used together at all in a world on this server version.
This matches everything observed throughout my original setup: every world I tested had at least one behavior pack active, and in every case, all resource packs failed silently regardless of their individual configuration.