AU 602: FFA1 tracker

[Addled Platypus]

I am in it for what was stated in th OP
I understood what and how the game would be

IMO here should be no vote about it.

[Thot]

Originally posted by Platypus Rex
I am in it for what was stated in th OP
I understood what and how the game would be

OP means what?

I would support the idea of using the Warrior Code from the Iron Civvers. Sounds good to me if we exclude the blue parts concerning diplomacy-restrictions. I would especially like to outlaw the F1-production-phase-bug. Imo it's a bug (a powerful one) and not a feature (even if everybody knows and uses it) and takes a lot of fun out of the game, because it's requires quite a bit of tedious micromanaging if you want to use it.

PS: snoopy has the save.

[Addled Platypus]

opening post

way pack to the Iron Civers thread

[Rommel2D]

In lieu of actually playing the game, I guess we can debate this...

The problem with the original post-

* Team behavior: Team members may communicate anything and everything to each other, maps, screenshots, science, whatever. Non-team members may not communicate except what's available in game -- you may communicate anything that would be technically communicable in game, so once map trading is available you can give specific directions; once mil. alliance is available you may make a military alliance; once communication is open, you may discuss scientific advances. Communication with one team member is communication with both. [NOTE: Thanks to snoopy, who I quoted from "Team PBEM" for the above.] It is suggested that team members share passwords so that they can cover each other when playing turns.

-is really the only part relevant to what we're discussing. The first bit is confusing because I think it is not meant to apply to the FFA game. The second bit, attributed to snoopy by Beta, seems to contradict what snoopy has since promoted (restricting map information until the tech is discovered vs no restrictions past contact). This demonstrates my point on how throwing out abmiguous statements about using 'common sense' and giving a few examples here and there is worse than useless- Civ3PBEM has so many grey areas and questionable tactics, any decent game should have (preferably) an exhaustive list of what is expected that can be referred to if need be, or (less preferably but still better than a sloppy 'we all intend to play nice' statement) an upfront agreement that all questionable tactics and exploits are acceptable.

If anyone would like to suggest another exploit list or draw up their own, I'm open to ideas, but would like to have something...

[Rommel2D]

Originally posted by Platypus Rex
opening post

way pack to the Iron Civers thread

Did you mean the original AU 602 control thread? This game isn't directly related to the Iron Civer tournament...

[Addled Platypus]

that would be correct Rommel2D

(now reading the post without the effect of beers)

[Addled Platypus]

3350BC to Krill

[Krill]

To Swissy

[Swissy]

3400BC to Thot

[Thot]

Originally posted by Swissy
3400BC to Thot

Luckily, that is not true.

--> snoopy369

[Rommel2D]

3300

PRexed

[Addled Platypus]

3300BC to Krill

[Krill]

Sent

[Addled Platypus]

e addy update

all further saves go to

PREXT at msn dot com

[Swissy]

au602, 3250bc, to Thot