@holy

what if we used a hashtable for each player to track the contents of their multiboard?  then use a trigger that updates the multiboard based on the hashtable contents?  I was thinking (playernumber, rowNumber) as the key scheme and it would map to an array with each index a column.. so like

Player 1 -> hashtable1
|  row1   |  ["Title","Value","OtherColumnValues"]  |
|  row2   |  ["a","b","c"]  |
|  row3   |  ["a","b","c"]  |



Maybe with classes that define certain templates of multiboard.. e.g. time's multiboard template could look like
Player 1 -> hashtable1
|  row1   |  ["Name","Stacks"]  |
| playerid |  ["TrekkingBowler",20] |
with a function for adding new rows like
if {none of the row keys match the playerID affected by wrathful portent}
hashtable1 key(playerID) = ["player's name", 1 ]
else { add one to hashtable1[player 1][playerID][1] }
and the same could be done every 10 seconds without a new stack applied to remove 1 stack.. there should be a catch statement that notices if the ["player's name", stackvalue] stackvalue ever reaches zero and it removes the dude from the hashtable.

Then the trigger for updating would iterate over the hashtable and display everything where we want it based on our structure.