JimSocks
October 30th, 2020, 13:30
Nope- they are all totally different... it’s just difficult to explain ESPECIALLY when the voting website forces me to use different symbols than the FG client does currently. (That website doesn’t like < or > symbols, so I have to replace them.
I’ll try to explain them a bit differently. Here’s two terms I will use throughout:
Within story templates:
[TableName] = a “table callout” Or “callout”
<TableName> = a “table reference” or “reference”
If you are not familiar with these at least, and how they work, the rest of this will be gibberish.
So currently within a story template, there are three limitations I want to overcome.
1. You cannot share data between story templates. Each one is an island. If I roll a NPC name on one story template, there is no way for me to retrieve that name for use in a separate template. One of the voting proposals solely tackles this.
2. You can’t use table callout within a table callout. ie: [Table [TableName] Name] doesn’t work. One of the voting proposals suggests an implementation approach to add this functionality.
3. You can’t reference a single column of a callout’s results. So if a table has three columns of data, and you roll on it with a [TableName] callout, a later reference of <TableName> will spit out all three columns. But what if you only want column three from what you rolled before? You are out of luck. A reference of <TableName|3> will not work. One of my voting proposals seeks to add this functionality.
Hopefully that helps?
The voting proposals themselves are more technical to try and describe HOW this could work within the code, but also made more difficult to describe due to the symbol issue mentioned above.