Topic: logic toolsmithy production

Hi,

I do have a question I wondered since I started playing: often I see myself waiting for tools to get produced by a toolsmithy. Even when they have all necessary wares, they seem to really slowly cycle through things I don't want them to produce, what they in fact do not produce and tell me why (is not needed by the economy), but what I then always wonder: why is this so slow? When, e.g., they do not need to produce a hammer and they don't produce one, why don't they instead start with what is needed instead of taking their time thinking about what they will not produce anyway?

Top

Quote

Would it be considered an 'ok' idea to change that: to show what they are producing at that moment?

Top

Quote

mxb2001 wrote:

It is somewhat useful as it is to let one see what's the problem. I agree though it would be nice if we got extra info such as what is currently being done also.

Which problem do you see? It does show you why one of the many thing was not made last try, but in my experience, that most of the time was not the one I was interested in and sometimes it was not even true (anymore): the toolsmithy was telling me 'x' was not produced because the economy would not need it, while there were buildings that needed workers which needed those tools - possibly just finished buildings, but still wrong at that moment. Maybe it even was producing that tool that very moment, but a player wouldn't know.

Top

Quote

I don't argue that there is a lot of information that could be useful. There could be a complex routine that puts all of that into a text that is as short as possible. If we want to go a little simpler (and shorter), we would need to prioritise. This would be my order of importance, with a cut-off somewhere yet unspecified in that list. The order in the final output could be different.

• currently producing X
• skipped Y despite demand because Z is missing
• could produce ABC, and have chosen X because WHY (e.g. because direct need from buildings/missing workers vs. from economy, if that would be possible)
• skipped EFG because not needed by economy

At the moment, I often get "skipped because is not needed by economy" all the while the building is producing something else, and it neither tells me that is is currently producing nor what. And often the 'is' is already wrong and a 'was' would be better.

Top

Quote

knarf wrote:

I don't argue that there is a lot of information that could be useful. There could be a complex routine that puts all of that into a text that is as short as possible. If we want to go a little simpler (and shorter), we would need to prioritise. This would be my order of importance, with a cut-off somewhere yet unspecified in that list. The order in the final output could be different.

• currently producing X
• skipped Y despite demand because Z is missing
• could produce ABC, and have chosen X because WHY (e.g. because direct need from buildings/missing workers vs. from economy, if that would be possible)

as explained earlier such a mechanism to choose is not implemented and hence such message is not possible

• skipped EFG because not needed by economy

At the moment, I often get "skipped because is not needed by economy" all the while the building is producing something else, and it neither tells me that is is currently producing nor what. And often the 'is' is already wrong and a 'was' would be better.

We will have a look whether we might be able to include the actual production into the message, however it might not be easy. Normally the activity of a building (whether it is producing something) should be visible from the animations. However we miss such animations for some buildings. so this might be a second means to see the activity as kind of workaround.

Top

Quote