resource gather rate

[Constantin]

it would be very helpful if i could see the amount of a certain resource gather per hour,or day/minute ...

[Feldnalas]

a extension of the storehouse / mayor house

[Seekhunt]

you can click on the building you want to see. Then in the new window click on details on the buttom and see the stats for that building

[Feldnalas]

i think he is asking for a empire wide total

[Psychyn]

you can click on the building you want to see. Then in the new window click on details on the buttom and see the stats for that building

While yes, this is available it would be a lot easier and nicer for the eyes and mind to simply have a "Resource overview" to see how much you get off each resource per hour. ^^ If we had a suggestion forum I'd have post it myself, but finding the thread here.. I'll just leave my support.

[Seekhunt]

i could not agree more.
But the problem in this is, that nearly every building have different resources times, because they all have either longer or minor production times and distance to the nearest storehouse.

So you would not be able to make a "one time" production showing, but should rather have 2. 1 for the quickest and 1 for the longest.
and that would be a whole lot of work, and still not easy to look at.
Then there is the whole upgrade part / buff of the buildings witch again "stirs" up the times.

So all in all, its very hard to make such an overview

[BB_Azariel]

As much as I agree with the need for a global tool like that, I must add that, because of the problems pointed out by Seekhunt, such an addon would be hard to program.

Because of that, and because there are still a good number of important bugs to fix, BlueByte has not planned something like that any time soon :'( Many players have asked for it though in the French and the German versions though, and I'll mention it to them as well.

In the meantime we'll have to be patient... Sorry guys...

[Krowe]

So you would not be able to make a "one time" production showing, but should rather have 2. 1 for the quickest and 1 for the longest.
and that would be a whole lot of work, and still not easy to look at.

Agreed. But we don't need to see the production time.

With a series of simple calculations, one can convert the production times of every building into a x/hr format. For example, a mason produces a unit of stone every six minutes. This becomes 10 units of stone every hour. When buffed, it becomes 20 units of stone every hour.

Expressing production in this format has one very important advantage - you can simply add up the units of stone produced every hour across all buildings of a specific type and express it as a single value. Real-time calculations mean that the value is adjusted every time you build, destroy, stop or buff a production building.

Sure, it's not perfect, especially in inefficient production chains when supplies come JIT at best (since production will fluctuate without player intervention), but it's a lot easier to use than what we have right now.

Assuming that it is possible, perhaps a player can design, say, a Grease-monkey script for our use up until a point that the developers can afford the time to develop an official version of the tool.

Say what?

[Repture]

this is basically what I'm making right now..
I'm building a spreadsheet where you can give in what you got like X amount of Stone and X amount of wood etc.
Then the same for the buildings that actually use the resources.
So in the end I see if my stock is going up or down and what I need to build to make it go bether..

I know it isn't accurate becuase of the time changes alot of where the building is but it gives a rough number :)

[CaioToOn]

I've posted something at the other thread that is also valid here: http://forum.thesettlersonline.com/threads/15159-Statisics?p=169006&viewfull=1#post169006.

Please understand that I know this kind of feature is hard do design/develop, and that there is other priorities in the list, but I believe that statistics and resource management are a very important trait of game series, and should be considered an important future feature.