public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Elijah Meeks <elijahmeeks@yahoo.com>
To: xconq7@sources.redhat.com
Subject: Item Units
Date: Sun, 22 Aug 2004 06:38:00 -0000	[thread overview]
Message-ID: <20040822055446.98854.qmail@web13123.mail.yahoo.com> (raw)
In-Reply-To: <l03130301bd4db1712248@[212.181.162.155]>

(Figured it deserved it's own thread)

Eric, you'd mentioned additional tables and we've
talked about the cow patties.  It seems like the
framework's in place for items, just add a fifth entry
to the ferry-on-entry/departure tables that's "Full"
(Or something similar).  I'd thought, when I first
worked with items as occupants, that "over-all"
would've worked, but it didn't.  "Full" would mean
that the transport paid all necessary ACP costs for
the occupant to move into the hex and load onto the
unit.

Problems:  

The AI, of course, would likely not get that these
units were useful, and would probably pick them up and
drop them at random.  An initial workaround would be
to set the ferry-on-entry to "Full" and the
ferry-on-departure to over-nothing, which means that
once the AI orders a legitimate unit to pick up an
item, it's stuck with it.  Not the best solution, of
course, but it would work.

I'd like to introduce three item types in Opal: 
Weapon, Armor and Gear.  They'd come in two flavors,
fine and magical.  So far, so good (Heck, only six new
units, I'll never reach 1000 like this).  But we've
all seen how a unit looks with three occupants,
especially when it occupies a cell with another unit
or two.  Without an occupant dialog box, it'd just be
too cluttered.

Building each magic sword by hand is also a pain.  So
I'd love to see initial-occupant and
occupant-when-created tables that call for, in the
case of the former, a unit placed with said occupant
and, in the case of the latter, an extra build to
produce, if the builder is able, the additional
occupants.  The tables would be percentage based,
especially useful with the initial-occupant table,
because then some of your swordsmen might start with
fine weapons or magic armor, adding a little
randomness to the game.  If the percentage is higher
than 100, it would indicate more than one occupant, so
that, say, a huge city could be set at:

(initial-occupant
   (hugecity magicsword 350)
)

And would always start with three magic swords with a
50% chance of a fourth.


Tablewise, occupant-adds-hit-chance/fire-hit-chance,
occupant-adds-acp, occupant-adds-damage and
occupant-adds-hp would be a great start.

And neural nets, and 3D units, and a fully 3D globe,
and XBox support, and and and...


		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

  reply	other threads:[~2004-08-22  5:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20 16:22 Three thoughts mskala
2004-08-20 18:34 ` Eric McDonald
2004-08-20 21:17   ` Andreas Bringedal
2004-08-20 21:28     ` Eric McDonald
2004-08-20 23:57       ` Andreas Bringedal
2004-08-21  1:21         ` Eric McDonald
2004-08-21  4:35           ` Jim Kingdon
2004-08-21 20:38           ` Jim Kingdon
2004-08-20 22:03     ` Elijah Meeks
2004-08-20 23:27       ` Eric McDonald
2004-08-21  1:17         ` mskala
2004-08-21  2:31           ` Eric McDonald
2004-08-21  4:33             ` mskala
2004-08-22  3:09 ` Hans Ronne
2004-08-22  6:38   ` Elijah Meeks [this message]
2004-08-22  9:37     ` Item Units Eric McDonald
2004-08-24  1:43       ` Lincoln Peters
2004-08-24  2:38         ` Eric McDonald
2004-08-24  2:51           ` Lincoln Peters
2004-08-24  3:32             ` Eric McDonald
2004-08-22 14:00   ` Three thoughts mskala
2004-08-22 18:56     ` Hans Ronne
2004-08-22 19:16       ` Lincoln Peters
2004-08-23  4:31         ` Jim Kingdon
2004-08-23 13:04           ` Elijah Meeks
2004-08-24 18:07             ` Eric McDonald
2004-08-24 20:59               ` Elijah Meeks
2004-08-25  0:54                 ` Unit-Image Bug Elijah Meeks
2004-08-25  4:58                   ` Eric McDonald
2004-08-23 16:48         ` Three thoughts Eric McDonald
2004-08-24  0:55           ` Lincoln Peters
2004-08-24  2:09             ` Eric McDonald
2004-08-24  3:02               ` Lincoln Peters
2004-08-24 18:12                 ` Eric McDonald
2004-08-25  5:34                   ` Jim Kingdon
2004-08-25 17:16                     ` Lincoln Peters
2004-08-25 22:09                       ` Jim Kingdon
2004-08-26  2:15                         ` Eric McDonald
2004-08-26  6:17                           ` Jim Kingdon
2004-08-26 19:12                             ` Eric McDonald
2004-08-26 22:08                               ` CXP??? Elijah Meeks
2004-08-27  1:50                                 ` CXP??? Lincoln Peters
2004-08-27  5:10                                 ` CXP??? Eric McDonald

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=20040822055446.98854.qmail@web13123.mail.yahoo.com \
    --to=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).