| ?user_input_command_file |
NO
|
(system-internal)
|
A Tag with this symbol targeting a file is created whenever a user enters a text command. |
| !task |
NO
|
(system-internal)
|
This Tag is DEPRECATED. It used to be used for tasks, but no longer has any effect. |
| !provide |
NO
|
(system-internal)
|
This Tag is used to mark a 'require_' Tag with something that satisfies the requirement.
The first argument of an !offer Tag should always be the !require tag. The remaining arguments can be whatever is appropriate and should be documented in the description of the require_ symbol.
See also: [[symbol:!offer]]. |
| !offer |
NO
|
(system-internal)
|
This Tag is used to mark a 'require_' Tag with an offer that may satisfy the requirement.
The first argument of an !offer Tag should always be the !require tag. The remaining arguments can be whatever is appropriate and should be documented in the description of the require_ symbol.
This is similar to [[symbol:!provide]], but where [[symbol:!provide]] means that the requirement has been met, this symbol just means that it might be able to meet it. Several offers may be made on a require_ Tag before one of them is chosen and used with [[symbol:!provide]]. |
| !nullify |
NO
|
(system-internal)
|
This Tag is used to deactivate other tags when needed.
It does not have a meaning on its own, but nullifies/negates/deactivates/ends other tags.
Note that this behavior is not recursive: You can't !nullify another !nullify tag. |
| !set_status_message |
NO
|
(system-internal)
|
This Tag is used to overwrite the status message Elody displays.
To do so, create a Tag with this symbol where the comment is the text you want to display.
If the comment is None, a default value is used instead that describes what the lod-executor is currently doing. If the comment is the empty string, no message is displayed.
Target this Tag with a [[symbol:!nullify]] Tag to deactivate it again. The last non-nullified !set_status_message will be the active one.
Note that this is related to [[symbol:!set_status_message]]:
[[symbol:!set_idle_message]] is a normal Message that is generated when the user needs to do something, and it remains visible after they do.
[[symbol:!set_status_message]] is not a real Message object but a dummy that is displayed at the bottom of the Scenario so long as there aren't any active Options to choose from. |
| !set_idle_message |
NO
|
(system-internal)
|
This Tag is used to overwrite the idle message Elody will display if there are no Rules or Options eligible to be used under the current parameter settings.
To do so, create a Tag with this symbol targeting a hidden Message.
Target this Tag with a [[symbol:!nullify]] Tag to deactivate it again. The last non-nullified !set_idle_message will be the active one.
Note that this is related to [[symbol:!set_status_message]]:
[[symbol:!set_idle_message]] is a normal Message that is generated when the user needs to do something, and it remains visible after they do.
[[symbol:!set_status_message]] is not a real Message object but a dummy that is displayed at the bottom of the Scenario so long as there aren't any active Options to choose from. |
| ?scenario_plan_only_trust_explicitly |
NO
|
(system-internal)
|
This Tag is created when a Scenario starts, if that Scenario was based on a Plan.
If its weight is 1, Elody will distrust all Rules that aren't explicitly trusted using [[symbol:?scenario_plan_user_trust]] or [[symbol:?scenario_plan_rule_trust]], regardless of their rating. |
| ?scenario_plan_rule_trust |
NO
|
(system-internal)
|
These tags are created when a Scenario starts, if that Scenario was based on a Plan.
For each Rule that should be especially trusted or distrusted, one of these Tags is created. The comment is the name of the Rule, the weight is 1 if the Rule should be trusted (it is treated as if it had a rating of 5 and moderator approval) and 0 if it should be distrusted (it is treated as having a rating of zero).
Note about the name of the Rule: If a version is given, the trust/distrust is specific to that version. If no version is given, it applies to all versions of that Rule. |
| ?scenario_plan_user_trust |
NO
|
(system-internal)
|
These tags are created when a Scenario starts, if that Scenario was based on a Plan.
For each User who should be especially trusted or distrusted, one of these Tags is created. The comment is the ID of the user, the weight is 1 if the user should be trusted (all their Rules are treated as if they had a rating of 5 and moderator approval) and 0 if they should be distrusted (all their Rules are treated as having a rating of zero). |
