Archive vs. Raw Assets: Choosing the Right Deployment Strategy in Ren'Py

Deployment File Organization

Ren'Py distributes game assets either as raw files in the game directory or bundled into .rpa archives. Raw files enable instant hot‑reloading during local development, while archives lock assets and improve load times for released builds.

Case Sensitivity Pitfall

Developers often test on Windows or macOS, whose file systems are case‑insensitive. When the same game is deployed on Linux, a file named Image.png may be referenced as image.png in the script, causing a File Not Found error because the archive or directory entry does not match the exact case.

Unresolved Decision

Should a production release keep assets in the game directory to simplify patching, or bundle them into .rpa archives to protect the code and reduce load times, especially when the deployment target is a case‑sensitive file system?

• Does Ren'Py prioritize files in the game directory over duplicates in .rpa archives, and how does this affect asset overrides?
• What is the impact of file‑name case mismatches when using archives on Linux versus Windows?
• What is the recommended workflow for updating individual assets in a production build without rebuilding the entire archive?