Game Map Index

Collection policy

Track collection standards

Records are selected for traceability and reproducibility, not just quantity. A public code without a clear source or a successful version check is not published as verified.

Required

What a record must include

  • A public original creator post or another source that clearly identifies the creator.
  • A complete import value that can be copied as plain text without reconstructing missing sections.
  • Enough context to identify the track name and distinguish it from duplicates or revisions.
  • A clean import result in an official PolyTrack release, recorded with the version and date.
  • A source URL, creator credit, verification note, and status that can be reviewed later.

Rejected

What this library will not collect

  • Anonymous reposts, scraper pages, or copied codes with no traceable original source.
  • Private, paywalled, leaked, or access-controlled material submitted without creator permission.
  • Game downloads, APKs, cracks, hacks, cheat loaders, or unlicensed game and asset reuploads.
  • Dangerous redirects, executable attachments, credential requests, or links that cannot be safely reviewed.
  • Exact duplicates, incomplete codes, or records that fail verification without a useful source note.

Review workflow

Five gates before and after publication

  1. 1
    Source check

    Open the original post, record the creator name and URL, and check whether the code is still publicly offered.

  2. 2
    Duplicate check

    Compare the track name, creator, source, and complete code against existing records.

  3. 3
    Clean import

    Use the official game, record its version, and import the unmodified text from a clean clipboard.

  4. 4
    Publish record

    Add source credit, tested version, date, status, notes, and only the minimum verification image needed.

  5. 5
    Maintain

    Apply the 90-day retest rule and respond to corrections, source changes, and creator requests.

Creator control

Correction and removal requests

A creator may ask to correct attribution, replace an outdated code, remove the public code or preview, or delete the record. A credible request immediately pauses copying while ownership is checked.

1. Identify the record

Provide the Track Library URL and original creator post.

2. Show creator control

Contact from the original account or place a short confirmation on that public profile. Government ID is not requested.

3. Choose the remedy

Correction, code replacement, preview removal, public tombstone, or full record deletion.

4. Apply and record

Disable copying promptly, complete the requested change, and keep only the minimum audit note needed.

Contact page published; delivery channel pending.The final domain and mailbox have not been purchased, so new public submissions are not being accepted. Read the contact and correction guidance; a working domain address will be added there before launch.

Request template

Information that will speed up a correction

Record URL:
Original creator post:
Creator account:
Requested action: correction / replace code / remove preview / remove record
Short explanation:
Preferred public credit, if the record remains:

Policy links

Verification and source rules work together

Collection eligibility does not guarantee permanent Verified status. Version changes and failure reports follow the separate compatibility lifecycle.

Read version policyRead official terms