[Feature]: Optional Descriptions

[master-of-old]

Summary

In the Activities (Offensive, Defensive, and Other), I would like a flag (either on the dialog or globally if the dialog would not work) that would turn off descriptions to make a condensed stat block.

Game system

PFS2e

[bushvin]

Hey, I'm not quite sure where this goes?

which provider are you talking about? The scribe export?

[master-of-old]

Ah yes. I put PF2e but I did not elaborate. I am talking about in the output produced by the Scribe provider.

[bushvin]

I guess you are referring to the Export Dialog:

It is meant to be able to select the export provider, and nothing more. Modifying it to allow this kind of formatting, would require me to completely redesign the dialog, and the schema of the export providers.

But when looking at the scribe export, it is in essence clear text and can be easily edited using the scribe editor...

Having had a look at it, I'm still not 100% sure which Scribe export you're referring to either: Export NPC as Creature, List a character's ABC or List possible actions.

If you could provide a mock-up (what it is now, and what you expect), it would be easier to understand. And possibly come up with a Condensed format exporter? Adding one is more trivial than redesigning the Export Dialog...

[master-of-old]

Ok, so what I am looking for is using the "Export NPC as Creature" exporter. I was able to do what I want by deleting this line (and the plus). I made the same change to all the "activities." I pulled this example from line 695 of the current released version:

    async offensiveActivities() {
        const offensiveActivities = [];
        this._creature.activities
            .filter((f) => f.category === 'offensive')
            .forEach((a) => {
                const name = a.name;
                const traits = pf2eHelper.formatTraits(a.traits);
                const activity = pf2eHelper.formatActivity(a.type, a.actionCount, pf2eHelper.scribeActivityGlyphs);
                const description = a.description;
                offensiveActivities.push(
                    `**${name}** ` +
                        (activity !== '' ? `${activity} ` : '') +
                        (traits.length > 0 ? `(${traits}) ` : '') +
          ---->     description
                );
            });
        return offensiveActivities;
    }

That is the only change so I am not sure it warrants an entire separate exporter, especially since any change to one will likely need to be made in the other, also. It is just, for my stat blocks that I use in Play-by-Post, I do not need or want the extra verbiage.

edit::Ok, I thought putting that in a code-block would not jack with the formatting. I will try again but that part was supposed to be a source code snippet.

[bushvin]

Markdown formatting is not trivial. use a single backtick to enclose words in a single line.
for entire blocks you need to enclose it in 3 backticks. I edited your comment, check it out

[master-of-old]

Understood. And me? I just highlighted the block and hit the "code" button on the ribbon bar. Thank you for showing me that.

Do you understand what I am talking about in the exporter? Should we break this out into another exporter or... how is this best handled?

[bushvin]

No, I believe I understand your request. The example speaks for itself.

But I need to consider how to implement this in a sustainable way. I don't want to refactor the whole thing every time something changes.

It will no doubt be an additional exporter for an abbreviated version of the npc export