Well, not really, but something like that. I liked the Public works system in CtP, was a great idea to reduce MM. And it's the reduction of MM that i have in mind here, not cloning the CtP PW system.
Soo...how did it work in CtP.
In an empire management screen you set a PW slider, much like the research slider in Civ4, the PW slider assigned a % of your production to the public works pool. The public works pool was essentially a stackable resource, like gold. These PW points were used instead of workers to build tile improvements. You'd select a tile, and you could select an item from a list of available improvements. It would cost some amount of PW points and a couple of turns to finish the improvement.
Now this had some gameplay advantages, like not having to move around single workers, but it also had a UI advantage. To build an improvement anywhere, you simply selected the tile and build it. No need to find a free worker or diverting one them from its current job.
So...how could something like this work in Civ4? First off, i don't think a full PW system is even posisble without the SDK, so i won't even bother going there. But i think a UI improvement is possible however, which wouldn't require any AI changes, only worker automation changes.
Here's the idea:
1. Allow tiles (or plots?) to be selected. When selected a list of available tile improvements is shown in the interface below (similar to that of a worker, without the move/sleep/automate/etc orders)
2. Selecting one of these improvements will add it to some list.
3. The worker automation algorithm is altered so that improvements on the list will be given priority over other improvements.
A new type of worker automation would also be added that only builds improvements on the list, and nothing else.
There are still be many details that have to be worked out, mostly for the automation algorithm and how the list is maintained. But what i'd like to know now, is this possible with the python scripts?
I think the most crucial things are the following:
Can tiles be made selectable?
Is the worker automation algorithm implemented in the python scripts or in the SDK?
Soo...how did it work in CtP.
In an empire management screen you set a PW slider, much like the research slider in Civ4, the PW slider assigned a % of your production to the public works pool. The public works pool was essentially a stackable resource, like gold. These PW points were used instead of workers to build tile improvements. You'd select a tile, and you could select an item from a list of available improvements. It would cost some amount of PW points and a couple of turns to finish the improvement.
Now this had some gameplay advantages, like not having to move around single workers, but it also had a UI advantage. To build an improvement anywhere, you simply selected the tile and build it. No need to find a free worker or diverting one them from its current job.
So...how could something like this work in Civ4? First off, i don't think a full PW system is even posisble without the SDK, so i won't even bother going there. But i think a UI improvement is possible however, which wouldn't require any AI changes, only worker automation changes.
Here's the idea:
1. Allow tiles (or plots?) to be selected. When selected a list of available tile improvements is shown in the interface below (similar to that of a worker, without the move/sleep/automate/etc orders)
2. Selecting one of these improvements will add it to some list.
3. The worker automation algorithm is altered so that improvements on the list will be given priority over other improvements.
A new type of worker automation would also be added that only builds improvements on the list, and nothing else.
There are still be many details that have to be worked out, mostly for the automation algorithm and how the list is maintained. But what i'd like to know now, is this possible with the python scripts?
I think the most crucial things are the following:
Can tiles be made selectable?
Is the worker automation algorithm implemented in the python scripts or in the SDK?
Comment