pet.trezy.dropFood

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

Repository @trezy.pet did:plc:ollch4g7tes2reb5eceiwuol namespace authority
Details · procedure
Kindprocedure
Authoritytrezy.pet
Indexed

Procedure

procedure · POST

Input

application/json

food

requiredstring

The id of a published pet.trezy.food.

x

requiredinteger

Horizontal position in scaled world px.

Output

application/json

droppedAt

string · datetime

error

string

Present instead of rkey/droppedAt when the drop was refused for an expected reason. A stable machine code the client branches on — add codes, never rename them.

  • knownValues: not-authenticated | unknown-food | bad-position | terrarium-full | save-failed

message

string

A sentence to show the player, accompanying `error`. Free to reword; do not branch on it.

rkey

string

The morsel's key in the space. What the client passes back as createInteraction's `drop` when a pet eats it.

Similar lexicons

semantic match

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

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

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