From 7de5c76d85eabc65220df9c6f9c76d546fed99b7 Mon Sep 17 00:00:00 2001 From: Marko Lindqvist Date: Wed, 24 May 2023 07:39:36 +0300 Subject: [PATCH 14/14] README.actions: Update actions location They are now in actions.ruleset See osdn #48003 Signed-off-by: Marko Lindqvist --- doc/README.actions | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/README.actions b/doc/README.actions index 3f3e9928de..a407e64553 100644 --- a/doc/README.actions +++ b/doc/README.actions @@ -15,12 +15,12 @@ action is enabled (and all its hard requirements are fulfilled). A ruleset author can therefore disable an action by not defining any action enablers for it in their ruleset. -A generalized action enabler lives in game.ruleset. It consists of the action it -enables and two requirement vectors. The first requirement vector, actor_reqs, -applies to the entity doing the action. The second, target_reqs, applies to its -target. If both requirement vectors are fulfilled the action is enabled as far -as the action enabler is concerned. Note that an action's hard requirements -still may make it impossible. +A generalized action enabler lives in actions.ruleset. It consists of +the action it enables and two requirement vectors. +The first requirement vector, actor_reqs, applies to the entity doing +the action. The second, target_reqs, applies to its target. If both requirement +vectors are fulfilled the action is enabled as far as the action enabler is +concerned. Note that an action's hard requirements still may make it impossible. In some situations an action controlled by generalized action enablers may be impossible because of limitations in Freeciv it self. Those limitations are -- 2.39.2