Send a dev trigger to the game
triggerSend a dev command to the running game and get its reply, with options to target a specific player, use the server side, and set a timeout.
Instructions
Ask the running game to do something, and return what it said.
Args:
command: One of the dev commands THIS mod serves — call commands to
see them, since they are the running mod's rather than a list kept
here. A word it does not serve is refused before anything is
written to disk: a game that does not recognise one does nothing,
and from outside that is indistinguishable from a hang.
target: Address the request to one player by name. Every request is
already addressed to this session's own player by default, so pass
this only to ask a DIFFERENT client — one another session drives on
the same machine.
argument: Only some commands read one — commands says which. Passing
one to a command that takes none is refused here, because the mod
would refuse it too and that costs a round trip.
server: Send to the dedicated server rather than the client. Some
commands are server-authoritative and refuse on a client, and each
side publishes its own list.
timeout: Seconds to wait for the game's reply. A command that does real
work on a large world can outlast the default, and for capture
that is now safe at any value: the capture lock records the
deadline this argument implies, so another session waits it out
instead of guessing from the lock's age. Raising it no longer
trades a slow capture against a collision.
refused is reported separately from ok: a refusal is the mod
deliberately saying no, and treating it as success is how a rejected action
reads as a completed one.
note is usually null and is the one field with no other way to reach you:
something that happened on the way to this reply which the reply itself
cannot show. Currently it says a capture lock was broken to take this
picture — captures are serialised across sessions sharing a save directory,
and this one's holder was judged gone. It names WHICH rule judged it: the
holder's own recorded deadline had passed, or the lock recorded no deadline
and the 60s age bound decided instead. The second is the weaker claim — a
guess about how long a capture can take — and worth knowing you are reading.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| server | No | ||
| target | No | ||
| command | Yes | ||
| timeout | No | ||
| argument | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | ||
| note | Yes | ||
| text | Yes | ||
| command | Yes | ||
| refused | Yes |