Or the Autonomous Forces in SPI's Outreach. A player should not see the backsides until Interaction allows the Player to see them.
An Autonomous Stargate could have a value of 4, 3 or 1. An Autonomous StarFleet could be a regular or a Dreadnought. Either of which should not be known unless there is Combat with them. The "Caretaker" Player would be able to see them at any time. >From: Allen Hill <[EMAIL PROTECTED]> >Date: 2006/12/21 Thu AM 09:46:03 CST >To: [email protected] >Subject: Re: [CBML] preventing backs of counters from showing in selection pane >> > ... specify that only >> > the front side of a counter group be visible during >> > play. >> > >> I believe that only works when the counters are owned >> by a player. >> > >Interesting. One case I can think of would be a game like Pax Romana, >where all the player counters are visible, but there are counters >representing "barbarian" forces that have a generic front side and a >randomly varying value on the back side that is hidden from everyone. > >I guess the CB solution would work a little differently than the board >game: >Have just the generic marker on the board. Create a tray for the >actual barbarian chit values that selects randomly. When a player >attacks a barbarian space and needs to get a value for the barbarians, >draw a chit from the tray. > > > >To change your delivery settings, go to >http://groups.yahoo.com/group/CyberBoardML. >Yahoo! Groups Links > > > BT Tracy Johnson Ye olde fashioned text games at: http://hp3000.empireclassic.com/ NNNN
