<?xml version="1.0" encoding="utf-8"?>
<s1 title="ResourceLimits"><table><strong class="highlight"><![CDATA[]]></strong><tr><td><strong class="highlight"><![CDATA[]]></strong><p>Usage:</p>
</td><td><strong class="highlight"><![CDATA[]]></strong><p>resourcelimits food lumber stone iron</p>
</td></tr><tr><td><strong class="highlight"><![CDATA[]]></strong><p>Example:</p>
</td><td><strong class="highlight"><![CDATA[]]></strong><p>resourcelimits 2b 50m 2b 20m</p>
</td></tr></table><p>This directive is a stub or extension for <jump href="/wiki/TradePolicy">TradePolicy</jump>. It will internally set your goals to function in a manner similar to the original resourcelimits found in older versions of AutoEvony and <jump href="http://duelingelectrons.com">YAEB</jump> bots. </p>
<p>This directive will instruct the bot how many of each resource you wish to keep in the city, so that it can buy and sell via config <jump href="/wiki/Trade">Trade</jump> to achieve it. The bot is a powerful tool, but it is not a miracle worker. The bot will generally tend to sell down food and stone in order to buy lumber and iron, so be careful of giving it unreasonable settings. </p>
<p>This can be combined with <jump href="/wiki/TradePolicy">TradePolicy</jump> to some extent. Place your resourcelimits goal line, and after it one or more <jump href="/wiki/TradePolicy">TradePolicy</jump> lines to override the resourcelimits line for that specific resource. For example, since resourcelimits by default will set a very low internal gold <jump href="/wiki/TradePolicy">TradePolicy</jump>, you could do: </p>
<p></p>
<source><![CDATA[config trade:1
resourcelimits 100b 20m 10b 50m
tradepolicy /type:gold /min:500m]]></source><p></p>

<br/>------------------------------------------------------------------------------<br/>
<p> <jump href="/wiki/CategoryAllGoals">CategoryAllGoals</jump> <jump href="/wiki/CategoryResourceGoals">CategoryResourceGoals</jump> </p>
</s1>