Template talk:Adventure overview
Using hList
Is there a way to make this template display the unordered lists using {{hlist}}? If so, I can't seem to figure it out.—
Yoda8myhead (talk) 20:28, 15 September 2014 (UTC)
- I need to dig into how to make #foreach and unordered lists play well together, but using <li> tags and class = hlist on the table itself seems to do the trick. --Oznogon (talk) 00:33, 16 September 2014 (UTC)
- The long and short of it: #foreach doesn't put each unordered list item on its own line, breaking the formatting. That was the preferred behavior for {{dot}}, but it breaks unordered lists as mediawiki treats all asterisks after the first as actual asterisks rather than new list items. Using <li> tags with #foreach forces it to recognize each list item as list items regardless of line breaks. A (beneficial?) side effect is that this method no longer produces a bullet before the first item in these lists, as .hlist is smart enough to omit the dot from the first item. I've tweaked the styles to accommodate this by adding a slight padding on the right side of the table cells to prevent the list items from colliding with the left-side row headers, and removing the valign attribute as .hlist overrides it. (On my browser, it's about a 1px difference.)
(tl;dr: When using #foreach to generate lists to use with .hlist, we have to use <li> HTML tags instead of * to build lists or mediawiki won't render the list correctly.) --Oznogon (talk) 00:49, 16 September 2014 (UTC)
- The long and short of it: #foreach doesn't put each unordered list item on its own line, breaking the formatting. That was the preferred behavior for {{dot}}, but it breaks unordered lists as mediawiki treats all asterisks after the first as actual asterisks rather than new list items. Using <li> tags with #foreach forces it to recognize each list item as list items regardless of line breaks. A (beneficial?) side effect is that this method no longer produces a bullet before the first item in these lists, as .hlist is smart enough to omit the dot from the first item. I've tweaked the styles to accommodate this by adding a slight padding on the right side of the table cells to prevent the list items from colliding with the left-side row headers, and removing the valign attribute as .hlist overrides it. (On my browser, it's about a 1px difference.)
Scenario Tiers
I've noticed this template now assigns a category (such as Category:Tier 1-3 scenarios) to all adventures. First off, holy cow - that's an impressive feat! Second, I'm not sure it's working as intended. I see on In Hell's Bright Shadow that the pfs flag isn't set, but the tier still gets assigned. --FoiledAgain (talk) 12:13, 17 November 2014 (UTC)
- Good catch! The tier autocategorization assumed only PFS scenarios would have multiple levels. I've tweaked {{Adventure overview}} to also require the pfs flag. Thanks! --Oznogon (talk) 20:18, 17 November 2014 (UTC)
Levels to be listed
I'm noticing that this template is being used inconsistently in regards to AP volumes and PFS scenarios versus some standalone modules.
In most cases (as shown on most AP pages like Burnt Offerings and Midwives to Death, and some standalone modules like Shadows at Sundown), the level displayed in this template is the one at which the PCs start. For a PFS scenario, the levels displayed in the template span the scenario's tier (for example, a tier 1-4 scenario, which can be played by any characters of from 1st to 4th level, lists 1st, 2nd, 3rd and 4th levels). For a publication that includes multiple adventures, the template displays the starting levels of each individual adventure (for example, Troubles in Otari, which consists of adventures for 2nd-, 3rd- and 4th-level characters, lists 2nd, 3rd and 4th).
However, for a few select standalone modules, the levels displayed span the entire range from the level at which the PCs start to the level at which the PCs end the adventure. As an example, Seers of the Drowned City, whose PCs start at level 6 and end at level 8, lists 6th, 7th and 8th levels, which is not consistent with the aforementioned cases and might need to be changed. - HTD (talk) 11:13, 29 November 2022 (UTC)
My opinion is that the level parameter should be separated into start level (the levels at which a group of PCs are eligible to play the module) and end level (the level of the PCs when the module ends). That way, it will be clear that, say, The Fall of Plaguestone is a module for 1st-level characters and will take them to 4th level, and not something like a tier 1-4 scenario that can be played by any characters from 1st- to 4th-level. - HTD (talk) 00:33, 2 December 2022 (UTC)