Initial draft of PFS Season 2 layout, based on bounties 1 & 2

tdhsmith commented 3 years ago

This is definitely preliminary work, but wanted to submit it in case you hadn't started your own version.

Removes parameters and content for fame, which is no longer awarded in season 2
Removes parameter & content for GP Income, which is now just rolled into GP earned
Adjusts rightbar & middlebox to new size & offset, and fixes their children accordingly
Shortens item/condition multiline to 5 lines

I do not own any scenarios for season 2, so this is untested for scenarios so far, but I know it is roughly the same layout for 2-00 at the very least. If nothing I can start checking against them by next week.

tdhsmith commented 3 years ago

Ok so the bounties do not match the scenarios at all. The scenarios seem to match layout1.yml quite closely... I'll examine more soon.

Should I rename layout2, given that it will be bounty-specific? Or are the layout numbers not tied to the season numbers?

Blesmol commented 3 years ago

I currently already have samples for the chronicles from s2-00 to s2-04 or so. The layout for season02 currently seems to be identical to season01. Originally I introduced the layout concept for being prepare to have season01 with a layout and seasons 02 to whatever with a different layout.

My expectation was that season02 would already come with the new layout as shown on http://www.organizedplayfoundation.org/paizo/guides/pfs2guide-en/gm-basics-pfs2-en/ in the "Filling out a chronicle" section. Not yet sure when this will come and whether Paizo will retroactively adjust the existing season02 chronicles.

So hmm... tricky. Not yet sure whether it makes sense to have a new slightly modified layout.yml now for the bounties, or try to adapt layout1.yml in a way that it can also be applied to the bounties with additional preset entries that need to be provided.

At the moment I would also tend to have a separate layout.yml file. But I would also propose to wait until the work on the last missing functionality is available and integrated into layout1.yml to avoid doing double maintenance. The missing functionality here which should be available is mainly drawing lines (to strike out entries in the items list) as targeted in #116 and perhaps allowing presets to be used for canvases (#108).

tdhsmith commented 3 years ago

I had seen that image in the society guide at one point too. Obviously a lot of their changes they wanted for the beginning of season 2 were delayed (i.e. changes around schools, fame, etc)...

Not yet sure whether it makes sense to have a new slightly modified layout.yml now for the bounties, or try to adapt layout1.yml in a way that it can also be applied to the bounties with additional preset entries that need to be provided.

My one thought was that I didn't want the parameters related to fame to be active at all, but that's a pretty minor want.

Should I wait to do other template updates in general? I have a friend finishing Fall of Plaguestone next week or two and was going to mock that up for him. No big deal either way.

tdhsmith commented 3 years ago

My one thought was that I didn't want the parameters related to fame to be active at all, but that's a pretty minor want.

Also I just recalled that another issue was that I couldn't adjust the number of lines in a multiline parameter via inheritance. (the rows in the item sections change from 7 to 5 on bounties)

Blesmol commented 3 years ago

Should I wait to do other template updates in general? I have a friend finishing Fall of Plaguestone next week or two and was going to mock that up for him.

If Fall of Plaguestone uses more or less pfs2.layout1, then this would be very welcome!

Also I just recalled that another issue was that I couldn't adjust the number of lines in a multiline parameter via inheritance. (the rows in the item sections change from 7 to 5 on bounties)

Yes, content entries are currently not named (had that very early, removed it again for various reasons). To change something like the line value for a multiline content entry, the proper way would currently be to use a preset. I won't say that its the best possible design decision, but at least at the moment that would be the way to go. This could look as follows:

layout1.yml

id: pfs2.layout1

presets:
  downtime_lines:
    lines: 6

content:
  - type:multiline
    value: param:downtime
    presets: [ downtime_lines ]

other.yml:

inherit: pfs2.layout1

presets:
  downtime_lines:
    lines: 5

Blesmol / pfscf

Initial draft of PFS Season 2 layout, based on bounties 1 & 2 #112