> It might be that there's no reason to believe there's any
> significant bugs remaining, in which case we can just close
> this metaticket.

During his extensive rework, pepeto found one more bug in this configuration (bug #22522), which is now fixed on all branches.

I haven't seen any other evidence of trouble, and comment #2 is vaguely positive, so I don't see any point keeping this open.

> Some of the closed tickets attached to this one may not yet
> have been fixed in 2.5.x as they may depend on the rework done
> under patch #4726.

All tickets attached to this one have been fixed on trunk, S2_5, and S2_4, it turns out.

> I wanted to record that ensuring this configuration is
> robust is a release goal for 2.5.0.

We got many more bugfixes for the team_pooled_research=TRUE case than I was expecting, so the urgency of making FALSE work has gone away; I think there are now no known issues with either configuration on any supported branch. Thanks very much, pepeto.

>Has anyone tried autogames involving teams with pooled research disabled? I suspect that one reason it's buggy is that it's a non-default configuration.

I played a couple of games with v2.5, civ2civ3 rules, all AIs in same team, and pooled research disabled. I did not notice bugs, but I can't be sure because I did not watch the tech upkeep specifically.
I did notice that AIs use to share all their techs, but they waste a lot of science by researching the same techs at same time. And I personally like to play this way because I can fight against big teams of AIs that share their resources against me, but are not too ahead in tech research.
When I tried pooled research in previous versions (without tech upkeep), a group of 6 AIs were technologically unreachable for me.

It might be that there's no reason to believe there's any significant bugs remaining, in which case we can just close this metaticket. I wanted to record that ensuring this configuration is robust is a release goal for 2.5.0.

Has anyone tried autogames involving teams with pooled research disabled? I suspect that one reason it's buggy is that it's a non-default configuration.

We've had various bugs with team_pooled_research=FALSE since the option was added in patch #1868.

This metaticket is has reduced scope compared to patch #4726, but is targeted at 2.5.0 rather than 2.6.0. I'm hoping that we can manage it without the necessary but disruptive rework that's going into 2.6.0.

Copyright (C) 2004-2006, the Gna! people. Posted items are owned by whoever posted them.
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.