net.sf.colossus.variant
Interface IVariant

All Known Implementing Classes:
Client

public interface IVariant

Defined for which methods we currently abuse the Client to forward the question about variant specific information to static methods in TerrainRecruitLoader.


Method Summary
 java.util.List<CreatureType> getPossibleRecruits(MasterBoardTerrain terrain, MasterHex hex)
          TODO get from Variant instead of static TerrainRecruitLoader access Just forwarding the query, to get at least the GUI classes get rid of dependency to static TerrainRecruitLoader access.
 int numberOfRecruiterNeeded(CreatureType recruiter, CreatureType recruit, MasterBoardTerrain terrain, MasterHex hex)
          TODO get from Variant instead of static TerrainRecruitLoader access Just forwarding the query, to get at least the GUI classes get rid of dependency to static TerrainRecruitLoader access.
 

Method Detail

getPossibleRecruits

java.util.List<CreatureType> getPossibleRecruits(MasterBoardTerrain terrain,
                                                 MasterHex hex)
TODO get from Variant instead of static TerrainRecruitLoader access Just forwarding the query, to get at least the GUI classes get rid of dependency to static TerrainRecruitLoader access.


numberOfRecruiterNeeded

int numberOfRecruiterNeeded(CreatureType recruiter,
                            CreatureType recruit,
                            MasterBoardTerrain terrain,
                            MasterHex hex)
TODO get from Variant instead of static TerrainRecruitLoader access Just forwarding the query, to get at least the GUI classes get rid of dependency to static TerrainRecruitLoader access.