okur4 / androminion

Automatically exported from code.google.com/p/androminion
0 stars 0 forks source link

Ambassador + Ruins / Knights #485

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

Expected outcome:
1) Play Ambassador
2) Reveal Ruined Market
3) Return 0, 1, or 2 copies of Ruined Market to the supply
4) Each player, in turn order, gains Ruined Market.

Androminion currently fails at step 3 and step 4.  In this example, Ambassador 
should be able to return Ruined Market to the supply.  Then, as long as the top 
card of the ruins pile is Ruined Market, each player in turn order gains Ruined 
Market.  As soon as a card not named Ruined Market is on top of the ruins pile, 
nobody else will gain a ruins card.

Note that the player is not allowed to return two differently named ruins.  The 
returned cards must have the same name.

Everything about ruins also applies to knights.

This is the relevant piece from the DA rulebook:
"Dark Ages has two piles of cards that have a variety of cards in them: the 
Ruins pile has a mix of five different Ruins, and the Knights pile has ten 
different Knights. [...] If a card is returned to one of these piles with 
Ambassador (from Seaside), turn over the current top card and the returned card 
goes on top, turned face-up. [...] Cards that try to get specific cards from 
the Supply fail to get a Ruins or Knight if the correct one is not the top one. 
For example if you buy a Ruined Market with Talisman (from Prosperity), you 
only gain another Ruined Market if that is the top Ruins under the one you 
bought; if you use Ambassador (from Seaside) to return Sir Martin to the 
Supply, the next player will gain that Sir Martin, but the player after that 
will not gain a card, as the next Knight will not be Sir Martin."

Original issue reported on code.google.com by August.D...@gmail.com on 7 Nov 2012 at 7:02

GoogleCodeExporter commented 8 years ago
Issue 429 was previously opened for Ambassador with Dark Ages cards.  Some of 
the problems described in that issue have been fixed, but this one is still out 
there.

Original comment by August.D...@gmail.com on 7 Nov 2012 at 7:06

GoogleCodeExporter commented 8 years ago
This issue was closed by revision r719.

Original comment by tkden...@gmail.com on 12 Nov 2012 at 4:33

GoogleCodeExporter commented 8 years ago
Issue 560 has been merged into this issue.

Original comment by August.D...@gmail.com on 7 Jun 2013 at 6:03