To expand, you can nest table calls, functions, etc. to your heart's content. TableSmith parses text from the inside out, so it will evaluate the "deepest" pieces first then work it's way out. So, for this (odd) example:

?

1,[TreasureLevel=[GetLevel%monsterType%={Dice~3d8}]]

?

TS will first evaluate the "Dice" call, then replace "%monsterType%" with whatever that variable holds, then call the table "GetLevelwhatever" with the forced result from the dice roll, then call "TreasureLevel" with whatever the "GetLevel..." call returns.

?

The one element you can't nest is variables, since the percent sign doesn't have an open/close. When TS sees a "%", it keeps reading until it hits another "%", and then evaluates what's inside.

?

One other exception is that TS will?not evaluate a conditional that isn't true, like so:

?

{If~%monster%=1 ? [GenMonsterEnc] / [GenNPCEnc] }

?

TS will evaluate one or the other, not both (it wouldn't be very efficient to do both, not to mention the potential for side effects...)

?

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, February 8, 2021 4:30 PM, Vance <clubvance@...> wrote:

?

?

?