public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@telia.com>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Doctrine, Plans, Tasks, Standing Orders
Date: Wed, 04 Jun 2003 17:28:00 -0000	[thread overview]
Message-ID: <l03130301bb03d7040ae5@[212.181.162.155]> (raw)
In-Reply-To: <20030603225718.1188.qmail@web13108.mail.yahoo.com>

>The design manual isn't too clear on where to put
>these commands, does anyone have any experience with
>them or is there a scenario that uses them?

Tasks and plans are parts of the AIs internal machinery. You should never
have to deal with them as a player or game module writer.

Doctrines are basic principles like how badly should a unit be damaged
before it heads back for repair. You typically set doctrines for different
sides as a game module writer.

Standing orders are commands just like any other commands that you give to
units during the game. I think they are explained in the manual. They are
not widely used, though.

Hans


  reply	other threads:[~2003-06-04 17:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 23:58 Problem With Unit Fire Elijah Meeks
2003-05-23  0:39 ` Hans Ronne
2003-05-23  4:35   ` Elijah Meeks
2003-05-23 19:11     ` Hans Ronne
2003-06-10  3:57       ` Advanced Unit Damage Elijah Meeks
2003-06-10 14:13         ` Hans Ronne
2003-06-10 17:08           ` Downloading Xconq Elijah Meeks
2003-06-02 22:19   ` Getting the Treasury to Work and Other Issues Elijah Meeks
2003-06-03 22:57     ` Hans Ronne
2003-06-04  2:03       ` Doctrine, Plans, Tasks, Standing Orders Elijah Meeks
2003-06-04 17:28         ` Hans Ronne [this message]
2003-06-05  2:09           ` Jim Kingdon
2003-06-05 17:07           ` Setting Advanced Unit Size Elijah Meeks
2003-06-05 20:13             ` Hans Ronne
2003-06-08  6:37               ` Supply and AI Elijah Meeks
2003-06-08  9:00                 ` Jim Kingdon
2003-06-10 16:11                   ` website update Erik Jessen
2003-06-08 16:26                 ` Supply and AI Hans Ronne
2003-06-08 18:44                   ` Elijah Meeks
2003-06-08 20:01                     ` Hans Ronne
2003-06-10  1:51                       ` Elijah Meeks
2003-06-28 18:08                       ` New Game Elijah Meeks
2003-06-28 23:20                         ` Hans Ronne
2003-06-04 17:06       ` Occupant Protection Elijah Meeks
2003-06-04 17:13         ` Hans Ronne
2003-06-24 20:27   ` A Couple Questions Elijah Meeks
2003-06-24 20:43     ` Hans Ronne
2003-06-24 20:54       ` Elijah Meeks
2003-06-25 21:48         ` Hans Ronne

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='l03130301bb03d7040ae5@[212.181.162.155]' \
    --to=hronne@telia.com \
    --cc=elijahmeeks@yahoo.com \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).