• Hello game master! Welcome to our growing community. Please take a moment to Register (top right button, see how: Slides).

    If you use Campaign Logger, you can use the same login details - we've linked the app to this forum for secure and easy single sign-on for you.

    And please drop by the Introductions thread and say hi.

Multiple regenerate buttons?

zmoazeni

New member
Is there a way to make a custom private generator that behaves like "3 Line Villages" where you can regenerate parts of the whole? For instance for that one, it allows you to regenerate Appearance, Adventure, and Villager.
 

ELF

Generator Sage
Staff member
Beta-Tester
Wizard of Combat
Wizard of Story
Currently that is not possible within Campaign Logger itself. But if you use an external generator client such as the Wordpress plugin, you can have multiple generators on the same page, each them them producing one part of the end result. Each of those can then be called separately, effectively resulting in a partial reroll.

But a full-fledged implementation of partial reroll is on my wishlist as well.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Gamer Lifestyle
Wizard of Combat
Wizard of Story
this is what i was wondering if this was a thing yet? re-rolling separate tables in a generator ? :)
This is working as of now!

YAML:
name: Multi-Line Example
explanation: A Multi-Line Example Generator
categories:
  - Multi-Line
  - Example
formatting: Old
resultPattern: '"firstLine": "{First Line}", "secondLine": "{Second Line}"'
tables:
  - name: First Line
    entries:
      - default result for first line
      - another result for first line
      - yet another result for first line
  - name: Second Line
    entries:
      - default result for 2nd line
      - another result for 2nd line
      - yet another result for 2nd line
This is a bit nerdy, though!

Let me explain:
  • The resultPattern must be in the form: '"key1": "value1", "key2": "value2", "key...": "value...", "keyN": "valueN"'
    • i.e., single-quote double-quote keyname double-quote colon double-quote value double-quote ... single-quote
  • "keyX" will be transformed to "Key X"
    • "someComplicatedHeadlineToReroll" --> "Some Complicated Headline To Reroll"
  • "valueX" will be regenerated and should be a table placeholder (e.g.)
  • Every key-value pair will be a separately re-rollable line
 

BahneGorkDK

Member
Gamer Lifestyle
Wizard of Story
hmm i must be doing something wrong but i cant debug it...

resultPattern: '"Main Mission": "{Mission type}", "Item/person": "{X}", "Location": "{location}", "Opposition": "{opposition}", "Opposition Tricks": "{tricks}", "{submission}"'
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Gamer Lifestyle
Wizard of Combat
Wizard of Story
hmm i must be doing something wrong but i cant debug it...

resultPattern: '"Main Mission": "{Mission type}", "Item/person": "{X}", "Location": "{location}", "Opposition": "{opposition}", "Opposition Tricks": "{tricks}", "{submission}"'
I found two things:
- submission should have a caption, too
- There is a crucial attribute that is not visible in the Generator UI: "wrapResultInCurlyBraces": true

The last thing I will try to fix now.
 

JochenL

CL Byte Sprite
Staff member
Wizard of Adventure
Beta-Tester
Gamer Lifestyle
Wizard of Combat
Wizard of Story
OK, fixed. Try this now:

YAML:
name: Mission
categories:
  - Mission
formatting: Old
resultPattern: >-
  "Main Mission": "{Mission type}", "Item or Person": "{X}", "Location":
  "{location}", "Opposition": "{opposition}", "Opposition Tricks": "{tricks}",
  "Submission": "{submission}"
wrapResultInCurlyBraces: true
tables:
  - name: Mission type
    entries:
      - Mission type
  - name: X
    entries:
      - X
  - name: location
    entries:
      - location
  - name: opposition
    entries:
      - opposition
  - name: tricks
    entries:
      - tricks
  - name: submission
    entries:
      - submission
 

BahneGorkDK

Member
Gamer Lifestyle
Wizard of Story
awesome got everything but sub-mission to work, but that is because sub-mission is a table where entries are a copy resultpattern.
So either there are no sub missions or there are 1 or 2 or 3 or 4.


- name: submission
entries:
- no prereqsubmissions
- |-
"PrereqSubmission 1":
"{Mission type}",
"Item/person":"{X}",
"Location":"{location}",
"Opposition":"{opposition}",
"Opposition Tricks":"{tricks}"

- |-
PrereqSubmission 1
{Mission type}
Item/person:{X}
Location:{location}
Opposition:{opposition}
Opposition Tricks:{tricks}
PrereqSubmission 2
{Mission type}
Item/person:{X}
Location:{location}
Opposition:{opposition}
Opposition Tricks:{tricks}
- |-
PrereqSubmission 1
{Mission type}
Item/person:{X}
Location:{location}
Opposition:{opposition}
Opposition Tricks:{tricks}
PrereqSubmission 2
{Mission type}
Item/person:{X}
Location:{location}
Opposition:{opposition}
Opposition Tricks:{tricks}
PrereqSubmission 3
{Mission type}
Item/person:{X}
Location:{location}
Opposition:{opposition}
Opposition Tricks:{tricks}
 
Top