pet.trezy.food
One kind of food. Published by the game, never by a player — the definitions guard refuses these from anybody but the publisher, the same as species and tiers. A food a client cannot draw must render nothing rather than a substitute, so these outlive any given build on purpose.
Details · record, key any
| Kind | record |
|---|---|
| Record key | any |
| Authority | trezy.pet |
| Indexed |
Record
record · key anyProperties
What it is called out loud — the accessible name of a morsel lying on the ground, since the sprite carries no text.
Which frame of the food sheet draws this. ⚠ UNLIKE MONEY, WHERE THE FRAME INDEX *IS* THE TIER AND THEREFORE CARRIES MEANING, this is an arbitrary slot. It is carried per record so the sheet stays append-only: a new food takes the next free frame and no existing food moves. A frame past the end of the sheet this build ships is dropped by the client rather than drawn, because empty space at a believable size is a blank rectangle a player would try to feed to something.
minimum: 0
Stable identifier, matching the record key. What a dropped morsel names, and what dropFood validates against.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
pet.trezy.foodDrop
recordOne morsel lying on the ground. Lives in the player's `pet.trezy.terrarium` SPACE, not their public repo: it is transient scenery, and a repo record would need a new OAuth scope in three places — which happyview-config.ts documents as breaking sign-in outright when the third is missed. A high price for recording that a morsel is at x=412. ⚠ NOTHING HERE IS SIGNED, SO NOTHING HERE MAY CARRY CONSEQUENCES. setPreferences.lua states the rule this obeys: a space is access control, not attestation. Fo
-
pet.trezy.dropFood
procedurePut one morsel on the ground. Writes to the caller's terrarium space; the space is created lazily by the first drop, so a player who never feeds anything never gets one.