From: Hans Ronne <hronne@comhem.se>
To: Robert Goulding <Goulding.2@nd.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: Selecting plans?
Date: Fri, 11 Jun 2004 18:39:00 -0000 [thread overview]
Message-ID: <l03130301bcefaa8c83a1@[212.181.162.155]> (raw)
In-Reply-To: <083351B7-BBCA-11D8-A4CE-000A9589320A@nd.edu>
>I've only just started playing xconq in the last couple of days - I'm
>mainly using the latest binary of the native OSX port. I've also
>installed the Windows version on a PC, and I noticed a difference in
>the gameplay (of the standard game). In the OSX version, you are able
>to select a plan for any unit. In the Windows version (and, as I just
>tested, with the Mac TCL binary) the 'Plan' item in the menu is always
>grayed out. Am I missing something that I need to do to set the plan
>in the non-Carbon version?
No. The reason why the plan menu is not fully implemented yet in the tcltk
interface is that it is a useless feature. Here is how it works:
If you run a unit under manual control, you can set its plan to whatever
you like, but it has no effect. It's your brain that makes the decisions,
not the AI.
If you put a unit under AI control, the first thing the AI does is to scrap
your plan and pick a new one more to the AI's liking. So the plan menu has
no effect in that case either.
I've been planning to use the plan menu for a semi-automatic mode in which
units would be controlled by the AI, but forced to stick to a plan picked
by the human player. I think such a mode would be very useful. But it is
still on the todo-list.
Hans
prev parent reply other threads:[~2004-06-11 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 17:09 Robert Goulding
2004-06-11 18:05 ` Eric McDonald
2004-06-11 18:39 ` Hans Ronne [this message]
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='l03130301bcefaa8c83a1@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=Goulding.2@nd.edu \
--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).