Lexicon Garden

com.gamethesky.skytanks.run

One Sky Tanks run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.

Repository @gamethesky.com did:plc:fpi7mvknwqh264gz6kug7pmk namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityskytanks.gamethesky.com
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

cleared

integer

Advisory: mazes cleared.

  • minimum: 0
  • maximum: 18

createdAt

requiredstring · datetime

difficulty

string

The difficulty the run was played at; absent means normal. A verifier must replay at it, and each has its own board.

  • knownValues: easy | normal | hard

faces

array

The player's own photo faces that rode in rival tanks, included on purpose (the game asks, off by default) so a replay anywhere shows them; each photo is a public blob in the player's repo. Looks only, like `rivals`: a face takes its slot ahead of the handles, the rivals' play is the sim's, and a verifier ignores this field entirely. Six at most.

  • maxLength: 6
itemsref
Reference

kills

integer

Advisory: rival tanks wrecked.

  • minimum: 0

level

requiredinteger

Advisory: the maze the run ended on, 1 to 18, three a world.

  • minimum: 1
  • maximum: 18

log

requiredstring

The whole run as the only input the game takes. Comma-separated `<dtick>.<k>.<a>` entries: dtick is 60 Hz ticks since the previous entry; k 1 holds (a 1) or lets go (a 0) of the trigger; k 4 gives up; k 5 sets the tank's controls to a = (throttle + 1) * 3 + (turn + 1), each -1, 0 or 1. Only inputs the sim accepted are logged. Example: `96.5.7,30.1.1,18.1.0`.

  • maxLength: 400000

rivals

array

Handles whose faces the rival tanks wore (people the player follows). Looks only: the rivals' play is the sim's and doesn't depend on this.

  • maxLength: 6
itemsstring
  • maxLength: 253

score

requiredinteger

Advisory: points. Higher ranks higher.

  • minimum: 0

seed

requiredstring

The mazes: `arcade` (the same for everyone), or a UTC date `YYYY-MM-DD` for that day's. Each has its own board.

  • maxLength: 16

simVersion

requiredinteger

Which rules produced this log. A verifier must replay under the matching version or refuse the run.

  • minimum: 1

ticks

requiredinteger

Advisory: 60 Hz ticks from the first count to the end of the run.

  • minimum: 1

won

boolean

Advisory: all eighteen mazes cleared.

#face

object

One of the player's own faces, as it rode in a run: which rival slot, the name under it, and the picture.

Properties

image

requiredblob

The face: a 256×256 JPEG, 64 KB at most, cropped to the middle of the photo. Readers refuse a bigger one.

  • maxSize: 65536
  • accept: image/jpeg

name

requiredstring

The name under the face, 40 characters at most.

  • maxLength: 160
  • maxGraphemes: 40

slot

requiredinteger

The rival slot the face rode in, 0 first. The slots are filled by `faces` at their slot numbers and then by `rivals` in order, so a face sits ahead of the handles, as it did on the player's screen.

  • minimum: 0
  • maximum: 5

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • com.gamethesky.skyvortex.run

    record

    One Sky Vortex run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.

  • com.gamethesky.hauntthesky.run

    record

    One night of Haunt the Sky, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.

  • com.gamethesky.fightthesky.run

    record

    One run of Fight the Sky, published by the player into their own repo: a climb up the ladder, or a single ghost fight (see `ghost`). The record stores the fighter's build and every input rather than a score: the sim is deterministic, so re-running the input log against the same seed with the same build reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score, wins and the rest are advisory and never trusted by a leaderboard.

  • com.gamethesky.make.run

    record

    One play of a Make the Sky game, published by the player into their own repo. It stores every input rather than trusting a score: each chapter's engine is deterministic, so replaying its log on the same game reproduces the run exactly. Owning the record is the identity proof and replaying it is the score proof; score and the rest are advisory.

  • com.gamethesky.epsteinfiles.run

    record

    One run of The Epstein Files, published by the player into their own repo. The record stores every input rather than a score: the sim is deterministic, so re-running the input log against the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score, level and the rest are advisory and never trusted by a leaderboard.