Source status: Community preview — not released. Checked July 20, 2026 against the official PolyTrack devlog. WIP posts are treated as development previews, not patch notes.
Current status as of July 20, 2026
PolyTrack 0.7.0 has not been announced as a released update on the official itch.io devlog. The latest confirmed release is 0.6.2, published May 31, 2026. The latest major feature release is still 0.6.0, published March 10, 2026.
That matters because players should not plan around features as if they are already live. There are public WIP signals from Kodub, but WIP does not mean release.
What is confirmed
The official devlog confirms 0.6.0 features: experimental multiplayer, garage customization, new community tracks, editor cut/copy/paste, banked road parts, Y-intersections, longer S-curves, wall slopes, optimizations, and official track updates.
Those 0.6.0 features are live. The official 0.6.1 and 0.6.2 notes then added community tracks and stability fixes; they did not announce 0.7.0.
What is being discussed for 0.7.0
Recent creator WIP posts on Reddit show development exploration around:
- A ranking system for PolyTrack 0.7.0.
- Terrain system testing.
- Community feedback on how strict ranks should feel.
In the ranking discussion, Kodub responded that ranks would probably be rebalanced before release. That wording is important: it points to development work, not a shipped patch.
Why a ranking system would matter
A ranking layer would change how players read progress. Today, a player mostly sees finish time, leaderboard position, ghosts, and personal bests. A rank could create a clearer goal for players who are not chasing world records.
Good ranking design would help three groups:
| Player type | What ranking could add |
|---|---|
| New players | A reachable target after finishing |
| Intermediate players | A reason to clean up mistakes |
| Speedrunners | Another way to compare consistency |
The risk is motivation. If ranks feel too harsh, casual players may feel punished. If ranks are too soft, competitive players ignore them. That is why the WIP feedback phase matters.
