com.gamethesky.hatsoff.run
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.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | hatsoff.gamethesky.com |
| Indexed |
Record
record · key tidProperties
Advisory: hats removed.
minimum: 0
dawn
booleanAdvisory: the night was won — the President's hat came off, or the night's cap was reached.
The whole run as the only input the game takes. Comma-separated `<dtick>.<weapon>.<x>.<z>` entries: dtick is 60 Hz ticks since the previous entry, weapon is 0 mist, 1 pulse, 2 drop, 3 for giving up (the run ends on that entry; x and z are 0), or 4 for a heading on an airlift level (x and z are then the direction in tenths, 0 and 0 to hover), x and z are otherwise the ground point in tenths of a unit (x east, z south, origin at the Washington Monument). Only shots the sim accepted are logged; a verifier applies the same rate, heat and cooldown rules and refuses a log that fires faster than they allow. Example: `120.0.-402.12,5.0.-398.14,30.1.-390.10`.
maxLength: 400000
holdPeak
integerAdvisory: the most people sheltering at once.
minimum: 0
The level the run was played on. Ids are append-only.
maxLength: 32knownValues: liberty | goldengate | alamo | rushmore | raid | airlift | mall | whitehouse
rehatted
integerAdvisory: cured people the horde caught again.
minimum: 0
rules
integerThe level's own rules version the run was played under. A verifier must replay under the matching version or refuse the run. Absent means 1.
minimum: 1
Which horde: a date (YYYY-MM-DD, local to the player) for the nightly horde, or any word for a practice one. The sim seeds from the FNV-1a hash of this string.
maxLength: 64
Which rules produced these shots. A verifier must replay under the matching version or refuse the run.
minimum: 1
stage
integerDeprecated: an earlier build's stage index. Superseded by level.
minimum: 1
ticks
integerAdvisory: the tick the steps fell.
minimum: 1
Advisory: the wave the steps fell in.
minimum: 1
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
com.gamethesky.deptofwar.run
recordOne mission of Dept of War, published by the player into their own repo. The record stores every strike rather than a score: the sim is deterministic, so re-running the strike log against the same seed, mission and difficulty reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score and the rest are advisory and never trusted by a leaderboard.
-
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.
-
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.skyvortex.run
recordOne 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.skytanks.run
recordOne 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.