This past weekend I came up with an interesting (to me at least) idea of an approach for Campaign Logger while prepping a new-to-me system and setting.
The idea is simple, but the implementation is a bit of cut-and-paste or JSON hackery.
The simple idea is this:
Turn the *index* of the new game book into a text list - one index item per line without the page numbers.
Mark each line with the Campaign Logger tag symbol you think best matches the index item.
Is it an @NPC or @Monster?
Is it a #Location?
How about an !item?
Is it a ~rule?
Be sure that any multi-word index entries are surrounded by " " so that they become a single tag.
Once you've tagged each line of the index, hit the big [+} in Campaign Logger and copy and paste the tagged list into the box and save changes.
Then watch as CL implements the framework of your entire game book - ready to fill in player and GM parts as needed while you prep or play the next adventure.
The idea is simple, but the implementation is a bit of cut-and-paste or JSON hackery.
The simple idea is this:
Turn the *index* of the new game book into a text list - one index item per line without the page numbers.
Mark each line with the Campaign Logger tag symbol you think best matches the index item.
Is it an @NPC or @Monster?
Is it a #Location?
How about an !item?
Is it a ~rule?
Be sure that any multi-word index entries are surrounded by " " so that they become a single tag.
Once you've tagged each line of the index, hit the big [+} in Campaign Logger and copy and paste the tagged list into the box and save changes.
Then watch as CL implements the framework of your entire game book - ready to fill in player and GM parts as needed while you prep or play the next adventure.