Reply to thread

Message

<blockquote data-quote="Zaltys" data-source="post: 6120494" data-attributes="member: 6704145">I second that request.Many of my old TableSmith generators are thousands of lines long. It&nbsp; would take ages to copy everything row by row, when a single cut and&nbsp; paste would suffice. 'course, most of my old tables use a lot of functions and datasets, so I couldn't convert them into this format anyway. O.G.R.E. dataset support would be extremely useful, since there's only so much one can do with simple subtables.For instance, my random settlement generator uses datasets to modify how common certain buildings are, based on the settlement race(s) and alignment. Bakery, for example: low modifier (common) for halflings, normal for humans and high (rare) for orcs. Likely to be generated in just about every halfling village, but rarely seen in orc settlements.It would be possible to replicate the dataset with subtables, but it'd take thousands of tables and tons of redundant entries.</blockquote>

[QUOTE="Zaltys, post: 6120494, member: 6704145"] I second that request. Many of my old TableSmith generators are thousands of lines long. It would take ages to copy everything row by row, when a single cut and paste would suffice. 'course, most of my old tables use a lot of functions and datasets, so I couldn't convert them into this format anyway. O.G.R.E. dataset support would be extremely useful, since there's only so much one can do with simple subtables. For instance, my random settlement generator uses datasets to modify how common certain buildings are, based on the settlement race(s) and alignment. Bakery, for example: low modifier (common) for halflings, normal for humans and high (rare) for orcs. Likely to be generated in just about every halfling village, but rarely seen in orc settlements. It would be possible to replicate the dataset with subtables, but it'd take thousands of tables and tons of redundant entries. [/QUOTE]

Verification