Import guide
How to import PolyTrack codes
Use a complete code from a credited source, then test it in the current official game.
- 1
Copy a verified record
Confirm the creator, original source, tested version, and last verification date before copying.
Browse track records - 2
Open the official game and enter the editor
Use Kodub's official itch.io page. The game opens in a new tab because third-party iframe embedding is not allowed.
Open official PolyTrack page - 3
Load the code and test the route
Import the complete text in the track editor. If it fails, record the game version and use the checks below.
Troubleshooting
Match the failure before retrying
Copy the complete code again and confirm the clipboard contains plain text.
Compare the track's tested version with the version shown in the official game.
Look for a newer verification date or mark the record as needing a retest.
Do not republish it without the creator's permission; mark the record removed.
Import FAQ
PolyTrack code questions
These answers describe this collection's current verification and source policy.
Where do I paste a PolyTrack code?
Open the current official PolyTrack game, enter the track editor, open its import control, and paste the complete code as plain text. This site links to the official game but does not run the importer itself.
Should I copy the shortened code shown on a track card?
No. The shortened value is only a visual preview. Use the Copy button on a Verified card or the Copy complete code button on its detail page to copy the full stored value.
Why does the import field stay empty after I paste?
Copy the complete value again, confirm the clipboard contains plain text, and retry the editor import control. Browser clipboard permissions or an incomplete selection can leave the field empty.
Why is a code rejected or loaded with the wrong layout?
Compare the record's tested version and verification status with the version shown in the official game. A changed game format, incomplete code, or outdated record may require a new verification pass.
What do Verified, Needs Retest, Broken, and Removed mean?
Verified means the stored code imported in the stated official version. Needs Retest pauses trust after a version or evidence change. Broken means a retest failed. Removed means the public record or preview was withdrawn under the collection policy.
Can I import a track without opening the official game?
No. Track Library is a reference and code collection, not a hosted copy of PolyTrack. Open Kodub's official page to import and play; the game is not embedded here through an iframe.
What happens if the original author post disappears?
The record should be reviewed instead of silently replacing its source. Depending on the remaining evidence and creator request, it may be marked Needs Retest or Removed, and removed material should not be republished without permission.
Can I submit a new track to this site now?
Not yet. The public contact channel remains closed until the final domain and author-contact address are ready. The collection standards page already documents the evidence required for a future submission.
Does a successful import guarantee that I can finish the track?
No. Verification confirms that the stored code loaded with the expected name, route preview, and playable entry in the tested version. It does not guarantee difficulty, completion, performance, or the absence of creator-designed hazards.
Which PolyTrack version were the current codes tested on?
The current collection was checked in official PolyTrack 0.6.2 on July 14, 2026. Check each record's date and status because a later game update can trigger an earlier retest before the normal 90-day cycle.