The game does not output empty particle texture reference warnings in the console at all, even though it results in use of the missing texture.
Attached are four resource packs which each modify the model for minecraft:stone. These resource packs should be applied independently of each other.
For the purpose of this report, each of the four resource packs is made to be flawed in some sense, as to demonstrate specific cases of absent or invalid references to textures, and the game's reaction to each:
- stone-no-block-texture does not reference a texture to use for the block itself
- stone-invalid-block-texture references a nonexistent texture to use for the block
- stone-no-particle-texture does not reference a texture to use for the particles produced by the block
- stone-invalid-particle-texture references a nonexistent texture to use for the particles produced by the block
To reproduce this issue, firstly make sure no other resource packs are applied, and then:
- Apply one of the four resource packs
- Pay close attention to the game's output log to check for any errors with the resource packs, noting which errors appear with each pack
- Once the resource pack is done loading, place and break stone blocks to check for missing textures, noting where they occur
- Repeat this with the other three resource packs
As the missing texture is never, under any circumstances, meant to be used or seen in-game, outside of cases where resources are misconfigured to a point where it must show up, it'd be expected that a warning be shown in the game logs regarding the use of the texture to notify resource pack developers to its presence in cases that may otherwise be overlooked.
The game only appears to output an explicit error in cases where an invalid texture is specified.
Not only is this internally inconsistent among these four detailed cases, it's also inconsistent with other related resource pack errors, such as invalid models, blockstates files referencing nonexistent models, sound events pointing to nonexistent sounds, and so on.
In addition, the unresolved texture reference output for textures which do in fact see direct use within the model could be considered somewhat incomplete, as it doesn't explicitly announce that the missing texture will be used, only hinting that there may be one. I can't think of any cases where the message would show up where the missing texture wouldn't end up being used, however it might be a good idea to output the "Using missing texture" error after such cases as well.