com.gamethesky.hauntthesky.house

A haunted house somebody made in Haunt the Sky's editor and published into their own repo: one floor, its look, its name, and optionally the maker's own cast. Anyone can play it from its link; runs in it name it by a strong ref, so a house rebuilt later never changes a night already played.

Repository @gamethesky.com did:plc:fpi7mvknwqh264gz6kug7pmk namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authorityhauntthesky.gamethesky.com
Indexed

Record

record · key tid

Properties

cast

array

The maker's own Foe Booth cast, included on purpose so everyone who plays the house meets them; each photo is a public blob in the maker's repo. Looks only. Absent, players meet their own cast.

  • maxLength: 7

createdAt

requiredstring · datetime

look

requiredstring

Whose wallpaper, floor and dark it has: the front hall's, upstairs', or the basement's.

  • knownValues: hall | upstairs | basement

name

requiredstring

The house's name, 60 characters at most.

  • maxLength: 240
  • maxGraphemes: 60

rows

requiredarray

The floor as rows of tiles, all the same length, 8 to 24 across and 8 to 20 down. `#` wall, `P` wall with a portrait, `W` wall with a window, `.` floor, `S` the start (one), `D` a locked door, `K` the key (at most one), `E` the stairs out (at most one), `A` rounds, `+` a medkit, `g` a ghoul, `h` a hound, `a` a ghoul that waits for the key, `T` the Thing (at most one), `V` the one you came for (at most one). The outside is all walls. A house is won by the stairs (any doors open with the key), or, with `V`, by putting the Thing down (its doors open then) and reaching `V`; everything that matters must be reachable. A reader refuses a house that breaks these.

  • minLength: 8
  • maxLength: 20
itemsstring
  • minLength: 8
  • maxLength: 24

Similar lexicons

semantic match

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

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