Lexicon Garden

com.gamethesky.epsteinfiles.run

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.

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

Record

record · key tid

Properties

buried

integer

Advisory: files redacted and buried.

  • minimum: 0

caught

integer

Advisory: FOIA requests denied.

  • minimum: 0

createdAt

requiredstring · datetime

difficulty

string

How hard the run was. A verifier must replay at the same difficulty. Absent means normal. Each difficulty has its own daily board.

  • maxLength: 16
  • knownValues: granny | easy | normal | hard

inputs

requiredstring

The whole run as the only input the game takes. Comma-separated `<dtick>.<code>` entries, or `<dtick>.4.<v>` for a run and `<dtick>.5.<v>` for a word: dtick is 60 Hz ticks since the previous entry; code 0 fires a redaction (on a press level it's an answer: `<dtick>.0` denies, `<dtick>.0.1` agrees, `<dtick>.0.2` spins), 1 moves up a belt, 2 down a belt, 3 resigns (the run ends on that entry), 4 sets the run direction along the belt (v is -1 up the belt, 0 stop, 1 back toward the desk), and 5 blacks out word v on the redaction round's page. Only inputs the sim accepted are logged; a verifier refuses a log the sim would not have accepted. Example: `60.0,14.1,3.0,40.4.-1,22.4.0`.

  • maxLength: 400000

level

requiredinteger

Advisory: the level the run ended on.

  • minimum: 1

player

string

Cosmetic: who the player played as, Spam Blondi, Odd Branch, Dan Squarehead or Ca$h Plate. The sim never sees it.

  • maxLength: 32
  • knownValues: blondi | branch | squarehead | plate

score

requiredinteger

Advisory: the final score.

  • minimum: 0

seed

requiredstring

Which batch of files: a date (YYYY-MM-DD, local to the player) for the daily batch, or any other string for a practice one. The sim seeds from the FNV-1a hash of this string.

  • maxLength: 64

simVersion

requiredinteger

Which rules produced these inputs. A verifier must replay under the matching version or refuse the run.

  • minimum: 1

start

integer

The level the run started at: 1 for a full run, any other level for practice, 0 for the redaction round alone. Absent means 1. Only full runs of a daily batch rank.

  • minimum: 0

ticks

integer

Advisory: the tick the run ended.

  • minimum: 1

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.hatsoff.run

    record

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

  • com.gamethesky.skytanks.run

    record

    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.

  • 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.