Difference between revisions of "Toolworks"
m (reformat use of resource icons) |
Mrotsalap3x (talk | contribs) m (→Extensions) |
||
Line 33: | Line 33: | ||
| The Furniture Workshop improves Timber token [[File:token timber.png|16px]] production | | The Furniture Workshop improves Timber token [[File:token timber.png|16px]] production | ||
| 5 Timber [[File:icon timber.png|16px]] | | 5 Timber [[File:icon timber.png|16px]] | ||
− | | 1 to | + | | 1 to 7 Timber Tokens [[File:token timber.png|16px]] |
| 2x1 | | 2x1 | ||
|- | |- |
Revision as of 11:20, 7 December 2017
Game Manual
- Basics
- Game content
- Infrastructure
- Vehicles
The Toolworks is where all the resources ( ) in the game are converted into the relevant tokens ( ). Each extension added to the Toolworks improves both the rate and the efficiency of conversion from resource to token. The base Toolworks always consumes a fixed number of resources per Game tick: 3 Timber , 4 Coal or 3 Iron . Each conversion is a separate process; therefore it can produce a single type of Token or all three types simultaneously.
Processes
The number of Tokens that a Toolworks returns for a particular resource changes between different buildings on the same map. As a result, it is always worth looking at all the Toolworks on the map and finding out which converts a particular resource the best. For example, within the same map two Toolworks had the following base operations:
This shows that in a single map, between two separate Toolworks, one can produce 3 times as many Iron Tokens for every three units of Iron supplied. This effect does not only affect Iron : Coal and Timber can both have different conversion rates between Toolworks. Extensions work is in a similar manner, as each extension will provide higher number of Tokens at one Toolworks than the same extension for a different Toolworks on the map. In the case of both the base Toolworks and extensions, the number of resources required remains constant with the number tokens received changing between buildings. The only exception to this is the product storage extension which always has a 1 to 1 conversion on all three resources.