File not found error during production distribution on case-sensitive filesystems

Ren'Py development environments on Windows often operate on case-insensitive filesystems, allowing assets to load regardless of whether the script matches the filename's casing. However, when distributing a production build to Linux or Android, the engine adheres to case-sensitive filesystem rules.

This discrepancy creates a scenario where a project functions perfectly during local testing but fails to locate assets once packed into .rpa archives or deployed to a target device. This is particularly problematic when assets are referenced inconsistently across different script files.

What is the recommended method for auditing all asset paths to ensure case consistency before the build process? Does Ren'Py provide a built-in validation tool to detect these mismatches prior to distribution?