A file can matter before the game draws a single pixel
A game asset is not necessarily “unused” just because players never see it. When a game starts, its engine may read resource lists, load material definitions, or check for files that other parts of the game expect to find. A small image can sit somewhere in that chain even if it never appears on screen.
The dependency can be indirect: a configuration file may name a material, which in turn points to an image. If the image is missing, the game may fail while preparing resources, rather than waiting until a level tries to display it. To a player, the file looks disposable; to the startup process, it may be a required link.
The visible image may not explain the failure
There is another possibility: software can check for a file’s presence without using its contents as artwork. A file might be listed in a package manifest, expected by a script, or referenced by code. Deleting it can therefore trigger a failure even if no obvious scene depends on it.
The exact reason varies by game, and the coconut example alone does not establish which mechanism is responsible. The useful lesson is that “I can’t find where this is used” is not the same as “nothing relies on it.” In a tightly connected game package, removing one tiny image can interrupt startup long before anyone would have noticed it on screen.
