Good point.
Since a chooser_table works with the agent (either in a template or alone) and an associated expression, it seems like a better option in cases like this.
As I think about it, an agent doesn't seem the way to go for the tours in T2K. From what I can tell, the compset for an agent has to be forced unique, and the hero can have multiple tours.
Breaking it down -
The hero can have anywhere from 1 - 8 Tours.
A Tour consists of:
(index number based on how many tours have been chosen)
1 career choice (can be the same across multiple tours) which consists of:
2 skill selections
1 specialty selection
+1d6 years
The hero can have anywhere from 1 - 8 Tours.
I can see a
table_dynamic to add a list of tours. The showtemplate for a single entry would show index, a chooser for the career, and years of the tour.
Any thoughts on the best way to handle this?