Version policy

PolyTrack code compatibility

A code is verified only for the official release and date shown on its record. A previous success is not treated as permanent compatibility.

Official release observed0.6.2

Release checkedJuly 14, 2026

Verified records30 / 30

Next routine retestOctober 12, 2026

Version wording is deliberately dated.Version 0.6.2 was the official release observed on July 14, 2026. Check the official page before assuming it is still current.Check official game

Compatibility matrix

What the current collection supports

Game release	Collection result	Public guidance
PolyTrack 0.6.2	30 codes imported successfully on July 14, 2026	Use records that still display Verified.
Earlier releases	Not tested by this collection	Do not infer backward compatibility from a 0.6.2 result.
Any later release	Unknown until retested	Move affected records to Needs Retest before recommending them.

Status lifecycle

Four labels with fixed meanings

Verified

The complete code imported successfully in the stated official version.

Enters this status: Original public source, creator credit, complete code, tested version, and a successful clean import are all recorded.
Public action: Keep the code and copy action available until a retest trigger occurs.

Needs Retest

The record was previously usable, but its current compatibility is no longer confirmed.

Enters this status: A new official game version appears, 90 days pass, the source changes, or a credible failure report is received.
Public action: Disable the copy action and schedule a clean re-import before returning the record to Verified.

Broken

The code repeatedly fails in the stated official version while the source record still exists.

Enters this status: Two clean import attempts fail after clipboard and version checks, with the failure documented.
Public action: Remove the copy surface, keep the source and failure note, and wait for a corrected creator code.

Removed

The public code and preview are no longer distributed by this library.

Enters this status: The creator requests removal, the original source is withdrawn, or a rights or safety concern cannot be resolved.
Public action: Remove the code and public preview promptly; retain only the minimum record needed to explain the status unless full deletion is requested.

Retest schedule

What triggers another import

Trigger	Timing	Required action
Official version change	Immediate	Move every affected record to Needs Retest until a clean import succeeds in the new release.
Routine age limit	Every 90 days	Recheck the source and import active records again even when the displayed game version has not changed.
Credible failure report	Before further recommendation	Disable copying, record the reporter's version and symptom, then reproduce the import from a clean clipboard.
Source edit or removal	As soon as observed	Compare the new source, preserve creator intent, and move the record to Needs Retest or Removed.

Clean verification method

A successful retest must be reproducible

Open the creator's original public source and copy the complete value again.
Open PolyTrack from the official Kodub page and record the displayed release.
Import from a clean clipboard, then confirm the expected name, route preview, and Play action.
Update the tested version, verification date, result note, and internal evidence together.

Browse current records Open verification log Read collection standards