PBEM and aggressive policy option
Posted: Sat Aug 20, 2005 5:50 am
2 BUGS (these may be conditions of a simplier to describe bug, but I ain't figured it out)
a) Columns are mislabelled
After some reports about difficulties making cease fires, I have determined that the setting of the second column (the one marked trade) causes ceasefires to be accepted or rejected, not the setting of the first column.
Similiarly, it is the third column (the one marked alliances) that causes trade proposals to be accepted or rejected, not the setting of the second column.
My working hypothesis, then, is that the columns are mislabeled.
b) Columns affect each other
Counter intuitively, if you tick any two of the three columns, trade proposals are rejected. Alliance needs to be the ONLY column ticked for trade proposals to be accepted (or all columns ticked).
[test conducted in released version of COG 1.1]
a) Columns are mislabelled
After some reports about difficulties making cease fires, I have determined that the setting of the second column (the one marked trade) causes ceasefires to be accepted or rejected, not the setting of the first column.
Similiarly, it is the third column (the one marked alliances) that causes trade proposals to be accepted or rejected, not the setting of the second column.
My working hypothesis, then, is that the columns are mislabeled.
b) Columns affect each other
Counter intuitively, if you tick any two of the three columns, trade proposals are rejected. Alliance needs to be the ONLY column ticked for trade proposals to be accepted (or all columns ticked).
[test conducted in released version of COG 1.1]