Ren'Py 8.2+ Screen Language Animation Cache Invalidation in Development Mode

Cache Invalidation for Screen Language Animations

Ren'Py 8.2 introduced a persistent image cache that stores screen language renderings across launches, using content hashes for deduplication in the cache directory structure. This cache invalidation depends on file modification timestamps and requires explicit renpy.cache.clear() calls to reset.

The core issue centers on screen animations using ATL transforms, which may bypass standard cache invalidation mechanisms. When development images are edited but retain identical timestamps, stale cache entries can persist and display outdated content without requiring a full restart.

Development mode cache behavior differs from distribution builds, and cross-platform cache locations vary between Android app sandbox and desktop user directories. Third-party launcher tools may also interfere with cache detection mechanisms.

Unresolved Questions

• Does the ATL transform system in screen language animations trigger cache invalidation when source images are modified?
• Can developers reliably detect and force cache refresh for screen animations during active development without full application restart?
• What is the recommended pattern for ensuring fresh renders of screen language animations across different Ren'Py 8.2+ versions and platforms?