Intersite Game - Turn Discussion Thread

[Shoot the Moon]

Just to put it out there, scout teams aren't entirely risk free for us. Having a scout sit on our deer or our corn before we can get a warrior back would have some cost to us. In general I think there's no reason not to play early in the clock this early on but maybe just make an exception while our warrior does this little excursion.

[Twinkletoes89]

Just to put it out there, scout teams aren't entirely risk free for us. Having a scout sit on our deer or our corn before we can get a warrior back would have some cost to us. In general I think there's no reason not to play early in the clock this early on but maybe just make an exception while our warrior does this little excursion.

This isn't always war is it? I'd be surprised if a team declared on us just to park a scout on a resource as the diplo hit would make it pretty foolish

[Shoot the Moon]

This isn't always war is it? I'd be surprised if a team declared on us just to park a scout on a resource as the diplo hit would make it pretty foolish

Just about as foolish as declaring war with a warrior with absolutely no chance of killing us (because we're size 3) I'd say.

[Sullla]

There's a new turn up. As planned, I'll wait to move our warrior until most of the other teams have ended turn. kjn has the C&D report over in that thread.

[Sullla]

24 hours later, we have CivFr, CivFanatics, and We Play Civ still left to end turn. I plan on running our turn once We Play Civ finishes, since they are the team who is most likely to have a warrior far out away from their capital. We think there's good reason to believe WPC has already found another team (and thus not us), but no reason to take unnecessary chances.

[Boldly Going Nowhere]

I'd love it if these other teams would spend more time playing civ and less time word-smithing in that stupid roleplay thread..

Is it too early to start piling up the PYFT diplo hits? Not that anyone is likely to catch 2Sommetra-sword on diplo penalty, but this is glacially slow and unnecessary. Thank you for letting me get that off my chest.

[kjn]

Well, I think we are in the PYFT boat right now. Granted, we are doing it for defensive purposes and due to having lost our warrior, but it's not like the rest of the teams knows that (unless we have a team with excellent C&D- and meta-gaming skills with a warrior 3NE of our capital).

But the fact that the game engine creates race conditions is one giant strike against it in competitive MP situations.

[Shoot the Moon]

Well, I think we are in the PYFT boat right now. Granted, we are doing it for defensive purposes and due to having lost our warrior, but it's not like the rest of the teams knows that (unless we have a team with excellent C&D- and meta-gaming skills with a warrior 3NE of our capital).

But the fact that the game engine creates race conditions is one giant strike against it in competitive MP situations.

Or just a giant strike against setting a MP turn timer to 48 hours.

[kjn]

Or just a giant strike against setting a MP turn timer to 48 hours.

No, the 48-hour timer and the race condition are orthogonal problems. Even with no race conditions coming up, there will be people taking forever to play - it's only that the race conditions forces some players to sometime game the clock, even for only defensive purposes.

And if we had race conditions, the fundamental problem is still just as bad with a 12-hour or a 24-hour or a 48-hour clock.

(How to solve it? No idea. Going for a plan-and-execution model would make the game very much different, and arguably very dissimilar from how Civ "should be".)

[Boldly Going Nowhere]

Just as bad from a technical point of view only. In practice, it would be the same problem gaming the clock, but wasting our time much less severely. 48 hours for this stage of the game is just too long.