Back to blog

Tile Pyramid — Version Analysis Across 5 Releases

We tracked function changes across 5 versions of Tile Pyramid (1.0.0 → 1.0.13) and found some interesting patterns including a significant refactor in v1.0.10.

analysiscase-studytile-pyramid

Background

Tile Pyramid is a Unity-based tile matching game with 256K+ reconstructed functions. We analyzed versions 1.0.0, 1.0.8, 1.0.10, 1.0.11, and 1.0.13 to understand how the codebase evolved.

Key findings

Version 1.0.10 was a significant refactor

Between 1.0.8 and 1.0.10:

  • −931 functions — the only version with a negative delta
  • +3,517 strings — a major string spike (high anomaly)
  • −28,427 constants — a large constant drop (high anomaly)

This pattern suggests a refactoring that moved hardcoded constants to a runtime lookup system, replacing magic numbers with string-keyed lookups.

Recovery in 1.0.11

Version 1.0.11 recovered with +695 functions — the largest single-version increase in the dataset. The string count stabilized, suggesting the 1.0.10 refactor was complete.

Trajectory table

| Version | Delta Functions | Trend | Anomaly | |---------|----------------|----------|---------------------| | 1.0.0 | — | — | — | | 1.0.8 | +1,185 | stable | — | | 1.0.10 | −931 | rollback | string spike, const drop | | 1.0.11 | +695 | stable | — | | 1.0.13 | +544 | stable | — |

Implications

Version analytics help identify when a game team refactored core systems versus when they added new features. A negative function delta almost always indicates consolidation rather than removal — functions get merged, inlined, or replaced with data-driven approaches.

This kind of insight is only possible when you can track function-level changes across releases.