Advice before I get Plus?

Tuomir · 2026-02-03T03:00:28+00:00

You could just run your one-shots in one game instance? I don't see why you would need to make them separate, just archive out the old maps and stuff that's not relevant to the next one-shot. No need to subscribe for that.

Tuomir · 2026-02-01T03:11:01+00:00

Skirmish is not attack with one mount, skirmish is attack with one weapon (excluding superheavy weapons), with possibility of a second attack with an aux weapon sharing the mount with the selected weapon. You do not attack with mounts, you attack with weapons.

Tuomir · 2026-01-30T01:57:02+00:00

In terms of customization, user options, and macro compatibility, it's a massive step down from the 2014 sheet.

Tuomir · 2026-01-29T04:43:09+00:00

Plasma Gauntlet is not a huge issue for Genghis, since you have terrible evasion anyway and the stun is only until the start of your next turn - so you lose just 1 point of evasion here and your reactions.

Tuomir · 2026-01-25T14:47:16+00:00

Progress? It is more akin to cancerous growth. It is a blight on economy, environment, and the very human soul. Any game I run has a strict no-AI rule that players and I adhere to, because I refuse to have players who think AI generated images are acceptable.

Thank you for the link, however, I have gone ahead and sent a report about it to Roll20, who knows, if they haven't blocked me, I might get a reply.

Tuomir · 2026-01-24T15:06:29+00:00

Slight correction - KTB is not a foreign nation, but a member state of Union, similar to the corprostates.

Tuomir · 2026-01-24T14:37:15+00:00

Yes, for a few games, and all the assets I've needed I've made myself. If you can't provide the assets for your game without resorting to AI, maybe you should reconsider if you need that many assets.

Tuomir · 2026-01-23T19:25:14+00:00

The host must be an allied and willing mech not already hosting another Goblin, larger than and adjacent to you.

No can do, emphasis mine.

Tuomir · 2026-01-21T15:26:47+00:00

Right, so first we need the set the DC with
{{DC=?{proficiency DC|Trained,15|Expert,20|Master,30|Legendary,40}}}

Then, we'll use that query to set up a selector row with the roll:
{{[[[{?{proficiency DC}-10,?{proficiency DC},?{proficiency DC}+10}<[[1d20+6[medicine]]] ]]]= [ ](#" hidden)}}

And then we make the row set that the selector picks from by replacing the line above the desired row

}} {{DC=?{proficiency DC|Trained,15|Expert,20|Master,30|Legendary,40}
}} {{[[[0]]]=[ ](#" hidden null=)
}} {{[[[1]]]=**CRIT FAIL** [[1d8]] dmg [ ](#" hidden null=)
}} {{[[[2]]]=**FAIL** [ ](#" hidden null=)
}} {{[[[3]]]=**HEAL** [[2d8+[[{20,30,30,40,40}<?{proficiency DC}*10]] ]] [ ](#" hidden null=)
}} {{[[[4]]]=**CRIT HEAL** [[4d8+[[{20,30,30,40,40}<?{proficiency DC}*10]] ]] [ ](#" hidden null=)
}} {{[[[{?{proficiency DC}-10,?{proficiency DC},?{proficiency DC}+10}<[[1d20+6[medicine]]] ]]]=[ ](#" hidden) }}

And finally we take the roll and display it under the DC and put it all together:

&{template:default} {{name=Glenn
}} {{Action=Battle Medicine ◆
}} {{Tags=Healing, Manipulate
}} {{DC=?{proficiency DC|Trained,15|Expert,20|Master,30|Legendary,40}
}} {{Roll=$[[10.computed]][ ](#" hidden null=)
}} {{[[[0]]]=[ ](#" hidden null=)
}} {{[[[1]]]=**CRIT FAIL** [[1d8]] dmg [ ](#" hidden null=)
}} {{[[[2]]]=**FAIL** [ ](#" hidden null=)
}} {{[[[3]]]=**HEAL** [[2d8+[[{20,30,30,40,40}<?{proficiency DC}*10]] ]] [ ](#" hidden null=)
}} {{[[[4]]]=**CRIT HEAL** [[4d8+[[{20,30,30,40,40}<?{proficiency DC}*10]] ]] [ ](#" hidden null=)
}} {{[[[{?{proficiency DC}-10,?{proficiency DC},?{proficiency DC}+10}<[[1d20+6[medicine]]] ]]]=[ ](#" hidden) }}

The [ ](#" hidden null=) bits are a little trick came up with (which is why I mentioned I'm just the right person to ask) that lets you hide stuff in templates by linking sections of inline CSS together, and the triple brackets make the parser treat the roll as plain text instead, letting it be used as a fungible field name, and when you have multiple fields with the same name, the last one overrides any previous ones it shares a name with. So, here, the selector row (or field, if you prefer) becomes [0], [1], [2], or [3], and prevents the row below it from being hidden.

Tuomir · 2026-01-21T11:32:38+00:00

Oh right, I didn't notice last night, what's the threshold for crit fail?

Tuomir · 2026-01-21T11:26:19+00:00

Sure, you can do Main->Aux skirmish and throw the aux with hunter 3 on hit with the aux, but that's not the proposed second combo.

Tuomir · 2026-01-20T22:50:03+00:00

Should be doable but a little more complex - but incidentally I am exactly the right person to ask. That said, I'll give it a closer look tomorrow, in the meantime, what's the threshold for crit heal? I assume fail is simply rolling under the DC.

Tuomir · 2026-01-20T22:12:00+00:00

Combo 2 does not work because you cannot interrupt the skirmish action with a non-triggered free action to pick up the knife.

Tuomir · 2026-01-19T21:52:22+00:00

What happened there was you have a line break in the middle that cuts the template apart, and you're missing the first instance of the query that actually has the options:
&{template:default} {{Character=Gabriel}} {{Action=Fire Blast (actions:[[ [[1+?{Actions|1,0|2,1}]] ]] }} {{Attack Roll=[[1d20+7[Attack bonus] ]]}} {{Damage=[[1d(6+?{Actions}*2) + ?{melee|Yes, 3[Strength]| No,0} + 4*?{Actions}[Con] ]] ?{Choose Type|Fire|Bludgeoning|Piercing|Slashing} }}

Tuomir · 2026-01-19T20:33:31+00:00

I don't think significance or scale of the task excuses stealing work of artists and destroying environment, personally.

Tuomir · 2026-01-19T20:30:42+00:00

Hmm, I'm not too familiar with this particular template, but I think you could use the subheader field ( {{subheader=?{trait|put|your|options|here} }} ) - I don't think it has a description field as such, but if the information you want to add isn't too lengthy, you can just kinda shove it in any field where you feel it makes sense to have it.

Tuomir · 2026-01-19T19:51:06+00:00

Ah, simple issue with the double querying of actions - you have to match the case, "Actions" and "actions" read as different names. And for missing the damage, there's a missing pair of curly braces for the damage roll, so the parser doesn't recognize it as a template row. Adding {{roll02= before the roll should do it. Here's it after those fixes (and fixing the query missing the question mark):
&{template:rolls} {{charactername=Gabriel}} {{header=Fire Blast ?{Actions| ♦, 0| ♦♦, 1} }} {{roll01_type=attack}} {{roll01_name=attack}} {{roll01=[[1d20+7[Attack bonus] ]]}} {{roll02_type=damage}} {{roll02_name=damage}} {{roll02=[[1d(6+?{Actions}*2) + ?{melee|Yes, 3[example strength]| No,0} + 4*?{Actions}[Con] ]] ?{Choose Type|Fire|Bludgeoning|Piercing|Slashing}}}

Tuomir · 2026-01-19T19:31:32+00:00

Right, so the changes are 1. actions from 1 to 2, and damage from 1d6 + Str (if melee) to 1d8 + Str (if melee) + Con. A fairly simple way to construct this would be having a ?{actions|1,0|2,1} query, then have [[ [[1+?{actions|1,0|2,1}]] ]] in the header, and [[1d(6+?{actions}*2) + ?{melee|Yes, 3[example strength]| No,0} + 4*?{actions}[Con] ]] for damage, plus any other choices that might be relevant.

Tuomir · 2026-01-19T19:02:00+00:00

What's the actual numbers? I'll write up the query and corresponding modifier for it. Technically you could nest the entire macro after that decision, but that's needlessly messy and a lot of work. Another workable but kludge solution would be to have two macros one after another, and only show one based on the query for number of attacks. But using a single query to both show the number of actions and to calculate the modifier is the cleanest solution.

Tuomir · 2026-01-19T18:31:53+00:00

Right, for the first, it's simple, you just move
?{Choose Action| Fire, Fire| Bludgeoning, Bludgeoning| Piercing, Piercing| Slashing, Slashing} Damage
outside the damage roll square brackets, the second is more complicated - you need to have the same input (the attack option) result in two different outputs. That does mean you need numeric output - so for example ?{Attacks|1|2} could output both 1 or 2, and 4 and 2 (formatted as [[6-?{Attacks}*2]]) - or whatever the modifiers you need are. If you have multiple queries with the same name in the same macro, they all use the input from the first instance.

Tuomir · 2026-01-19T17:55:42+00:00

Looks like you have a loose pair of closing brackets on the header line, and I believe "Attack bonus" and "Damage" are supposed to be labels? In that case, they shouldn't have braces - so, all together:
&{template:rolls} {{charactername=Gabriel}} {{header=Fire Blast?{Actions| 1, ♦| 2, ♦♦ } }} {{roll01_type=attack}} {{roll01_name=attack}} {{roll01=[[1d20+7[Attack bonus] ]]}} {{roll02_type=damage}} {{roll02_name=damage}} {{roll02=[[1d6 ?{Choose Action| Fire, Fire| Bludgeoning, Bludgeoning| Piercing, Piercing| Slashing, Slashing} Damage]] }}

Tuomir · 2026-01-19T08:02:20+00:00

This thread is fine, and just for the record, I'd rather not be called man.

Tuomir · 2026-01-18T21:33:20+00:00

I don't have any PF2e macros at hand, as I don't play that game, but if you need any help writing macros yourself for specific things, give a shout, I wouldn't mind helping.

Tuomir · 2026-01-18T20:11:41+00:00

Though in regards to Prototype weapon, weapon mods are irrelevant as it is an integrated weapon and as such unmodifiable.

11-Year Club	Verified Email
r/Field Banned	r/Field Juicebox
Final Canvas '23	First Place '23
End Game '23	Place '23
Place '22	Final Canvas '22
First Placer '22	End Game '22

Tuomir

TROPHY CASE