rndtreas.htm

---
title: "PST:EE 2DA Files : rndtreas.2da"
---
    <div class="title_main"> rndtreas.2da</div>
<br />
This file defines what items are generated when a creature uses an item of filename <code>RNDTRE0#.ITM</code>, where <code>#</code> is the row number of <code>RNDTREAS.2DA</code> to use.  <code>RNDTRE0#.ITM</code> is replaced by the generated item.  Therefore, this works like a random treasure table.<br />
<br />
The first column of <code>RNDTREAS.2DA</code> specifies the name of the row, currently a simple generic name.  The rest of the 19 columns have headers <code>2</code>, <code>3</code>, <code>4</code>, <code>5</code>, ..., <code>18</code>, <code>19</code>, <code>20</code>.  The column used is specified by a roll of a D20, with rolls of 1 replacing <code>RNDTRE0#.ITM</code> with no item.  Note that this is different from <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code>, which has an extra column labelled <code>1</code>, but similar to <code><a href="../2da_pstee/rndmagic.htm">RNDMAGIC.2DA</a></code>. Only 20 columns in total are supported, else the 2da file will fail to work entirely.  When this happens, all <code>RNDTRE0#.ITM</code>s are replaced by erroneous invisible items that cannot be removed.<br />
<br />
The PSTEE version of <code>RNDTREAS.2DA</code> is shown below.  In essence, <code>RNDTREAS.2DA</code> works exactly the same as <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code>, so see <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code> for an example of how <code>RNDTREAS.2DA</code> works.  However, <code>RNDTREAS.2DA</code> can be directly referenced by <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code> without actually having <code>RNDTRE0#.ITM</code> as a resource.  For example, an entry in <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code> that reads <code>RNDTRE05</code>, and a D20 roll of 6 will replace <code>RNDTRE0#.ITM</code> with <code>AEGIS</code>.<br />
<br />
In PSTEE we have:<br />
<pre>
2DA V1.0
*
    1   2           3       4           5       6           7           8           9           10          11          12          13          14          15          16          17          18          19          20
1   *   10*10       copear  broring     brobra  rustdag     clotchrm    dratchrm    10*10       broring     10*10       10*10       copear      broring     brobra      rustdag     clotchrm    dratchrm    10*10       brobra
2   *   40*50       silear  silring     silbra  stiletto    hammer      ax          bloochrm    cratchrm    RNDSCR01    40*50       stiletto    silear      silring     silbra      40*50       ax          silring     cratchrm
3   *   50*100      golear  golring     golbra  axqual      qstlo       gsknife     gsdagger    RNDSCR02    hearchrm    knotchrm    bonechrm    50*100      golring     RNDSCR02    gsknife     50*100      bonechrm    RNDSCR02
4   *   hearchrm    20*500  20*500      20*500  hearchrm    20*500      20*500      20*500      20*500      20*500      hearchrm    20*500      20*500      20*500      hearchrm    20*500      20*500      20*500      20*500
5   *   heaven      umei    zero        bell    aegis       50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000     50*1000
</pre>

<br />
<code>RNDTREAS.2DA</code> is supposed to support 9 functional rows of random treasure (from <code>rndtre01.itm</code> up to <code>rndtre09.itm</code>).<br />
However, because of lax or missing range checks it is possible to extend the list quite a bit beyond the nine entries. The engine seems to use the ASCII code of the last filename character. After <code>9</code> there would be <code>:</code>, <code>;</code>, <code>&lt;</code>, <code>=</code>, <code>&gt;</code>, <code>?</code>, <code>@</code>, followed by <code>A</code> to <code>Z</code>. While characters like <code>:</code> or <code>?</code> are difficult to use because of their special meaning on filesystems, you can still use <code>A</code> to <code>Z</code>, which results in additional 26 random treasures (from <code>rndtre0a.itm</code> up to <code>rndtre0z.itm</code>). The entries between <code>9</code> and <code>A</code> can simply be filled with empty dummy entries.<br />
<br />
If <code>RNDTRE0#.ITM</code> references a non-existant or an ignored row number (or if <code>#=0</code> under any circumstances), then <code>RNDTRE0#.ITM</code> is replaced by an erroneous invisible item that cannot be removed.  Note that the replacing item is <b>NOT</b> <code>RNDTRE0#.ITM</code> itself, in this case. This blank item can likely be altered by setting the default 2da entry to a valid item.<br />
<br />
Items that can be referenced:
<ul>
  <li>specific items (for stackable items, a <code>*#</code> suffix, that is, an asterisk followed by a number, can be added to the item ResRef to specify the amount of that item to create, e.g. <code>BOLT04*4</code> generates a single stack of 4 <code>BOLT04</code> items; for non-stackable items, a <code>*#</code> suffix does nothing; the limitations on the size of <code>#</code> are the same as that for gold pieces described below)</li>
  <li><code>#</code>, that is, a number, refers to a gold value (e.g. <code>#=016</code> replaces <code>RNDTRE0#.ITM</code> with a stack of 16 gold).  The maximum stack of gold allowable is 256 pieces.  More than that listed will max out at 231 (interestingly, this is the remainder when you divide 256 into 999; <code>#</code> need not be three digits, so if <code>#=4</code> or <code>#=04</code> or <code>#=004</code>, a stack of 4 gold will still be generated without error) &mdash; <code>*</code>, that is, a single asterisk, generates an erroneous item, i.e. an invisible item that cannot be removed.  This is useful if you want your creature not to drop anything, but you do not want to use this for containers and item piles</li>
  <li><code>RNDMAG##</code>, which references <code><a href="../2da_pstee/rndmagic.htm">RNDMAGIC.2DA</a></code>, where <code>##</code> is the row number to use, allowing further randomisation; a D20 is rolled to determine which column of this file to use</li>
  <li><code>RNDSCR##</code>, which references <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code>, where <code>##</code> is the row number to use, allowing further randomisation; a D20 is rolled to determine which column of this file to use</li>
</ul>
<br />
Items that cannot be referenced:
<ul>
  <li><code>RNDEQU##</code>; using this will create <code>RNDEQU##.ITM</code>, exactly as it is (circular loops are not possible)</li>
  <li><code>RNDTRE##</code>; using this will create <code>RNDTRE##.ITM</code>, exactly as it is (circular loops are not possible)</li>
</ul>
Since <code>RNDTREAS.2DA</code> can reference <code><a href="../2da_pstee/rndmagic.htm">RNDMAGIC.2DA</a></code> and <code><a href="../2da_pstee/rndscrol.htm">RNDSCROL.2DA</a></code>, and <code>RNDWEP.2DA</code> but not <code>RNDEQUIP.2DA</code>, this 2da file is the second to the top of the random treasure table hierarchy.