Worklist purging behaviour changes 2.6 -> 3.0 (civ2civ3)
Posted: Sat Jan 11, 2020 9:35 am
In version 2, if a building (not units - we're only talking about buildings in this message) is in a worklist, has already been built and comes to the front of the queue, then, the building is purged from the worklist, a message telling you this appears in Messages, and the city continues building the next thing.
In version 3, this is changed and you get "City can't build Improvement from the worklist; reason unknown! Postponing..." in Messages, the building stays at the front queue and the city keeps building it. You must then manually delete it from the worklist.
The new behaviour can be useful in two edge cases, but there are so many other reasons that it's real bad, that I think that the new behaviour is unintentional and therefore a bug.
The two edge cases where the new behaviour is an improvement are the power-problem and the sewer-shit.
The power-problem is where you mess up and unnecessarily build more than one power station for a city. There are several ways to get this wrong and several ways to correctly-intentionally get it right (build more than one). The most irritating is when you own the Hoover Dam (somewhere), have Hydro in this city, and the city happily goes on and builds a redundant Solar. The new behaviour prevents the power-problem, because earlier on you got the above message and have already been forced to think about it.
The sewer-shit is caused by the requirement of having to have 9 pop to build the sewer. You get 9, you queue a sewer, you get hit by plague (the exact problem you're trying to solve) and when sewer gets to the front of the queue it won't build. With the new behaviour you're forced to think about it, and sort it out somehow.
For everything else, the new behaviour is bad. In fact, one of my solutions for the sewer-shit (and other problems) was (when I noticed it) to just throw a worklist of all improvements at the city and it'll purge the one's it has and build the ones it hasn't. With the new behaviour, this just doesn't work at all.
Does anyone agree with me? Can I raise it as a bug on hostedredmine? Or is there (again) something I haven't read that makes the new behaviour sensible?
In version 3, this is changed and you get "City can't build Improvement from the worklist; reason unknown! Postponing..." in Messages, the building stays at the front queue and the city keeps building it. You must then manually delete it from the worklist.
The new behaviour can be useful in two edge cases, but there are so many other reasons that it's real bad, that I think that the new behaviour is unintentional and therefore a bug.
The two edge cases where the new behaviour is an improvement are the power-problem and the sewer-shit.
The power-problem is where you mess up and unnecessarily build more than one power station for a city. There are several ways to get this wrong and several ways to correctly-intentionally get it right (build more than one). The most irritating is when you own the Hoover Dam (somewhere), have Hydro in this city, and the city happily goes on and builds a redundant Solar. The new behaviour prevents the power-problem, because earlier on you got the above message and have already been forced to think about it.
The sewer-shit is caused by the requirement of having to have 9 pop to build the sewer. You get 9, you queue a sewer, you get hit by plague (the exact problem you're trying to solve) and when sewer gets to the front of the queue it won't build. With the new behaviour you're forced to think about it, and sort it out somehow.
For everything else, the new behaviour is bad. In fact, one of my solutions for the sewer-shit (and other problems) was (when I noticed it) to just throw a worklist of all improvements at the city and it'll purge the one's it has and build the ones it hasn't. With the new behaviour, this just doesn't work at all.
Does anyone agree with me? Can I raise it as a bug on hostedredmine? Or is there (again) something I haven't read that makes the new behaviour sensible?