Current status as of May 14, 2026
PolyTrack 0.7.0 has not been announced as a released update on the official itch.io devlog. The latest confirmed major release is still PolyTrack 0.6.0, published on 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 are live topics players can safely write guides around today.
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.
Why terrain testing matters
Terrain changes would matter most to creators. New terrain tools can create stronger visual identity and new route-reading problems. If terrain affects only appearance, it changes atmosphere. If it affects grip or surface behavior, it changes driving.
Until official notes confirm the details, creators should treat terrain posts as previews, not production rules.
What writers should do now
Write source-checked 0.6.0 content now. For 0.7.0, write watch articles, not release guides.
Good 0.7.0 article angles:
- What a ranking system could mean for PolyTrack practice.
- How terrain tools could change custom track design.
- What players should not assume before official patch notes.
- How major updates can affect records and route memory.
Bad article angles:
- "Everything in 0.7.0" as if the update is out.
- "Released features" based only on screenshots.
- "Best 0.7.0 tracks" before the release exists.
