So
I noticed a problem* earlier with the
macro: %{selected|NPC_athletics} If
the npc doesn't have a specified athletics value it assumes zero
rather than strength. After
much looking I found a thread that seemed to exactly address my
concern: <a href="https://app.roll20.net/forum/post/3103448/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/3103448/slug%7D</a> and
the macro: %{selected|athletics} which
at a glance seemed to fix the problem, until I tested a little more.
Whether
or not the NPC has a specified athletics value, this simply assumes
str. (While academically it would be nice to figure that out in some
universal sense, I only actually care about it as an NPC mechanic,
the players can fend for themselves). Now
it is possible these are both working as intended, but I have hard
time seeing how. Ultimately
I think one of them working as expected (by me admittedly, which is
to say it uses str unless a specified athletics value exists) would
solve my problem but I am curious how to craft these types of macros
anyway. So I might as well ask for that as well. I
would like to know how to craft a macro that would allow me to use of
several values based on a basic criteria (most likely highest or
lowest), based on a pathfinder sheet macro I
tried: Athletics:{Selected|[[
1d20 +({@{npc_str_mod} , @{npc_athletics} }kh1) ]]} Which
does doesn't even pretend to work (including a wide variety of more
or less curly braces, NPCD vs NPC etc., it was a longshot, I
have no skill at this beyond parroting. The original macro [[
1d8 + ( { 5 , @{Level} }kl1) ]] found here
( <a href="https://wiki.roll20.net/Macros/Pathfinder_Examples" rel="nofollow">https://wiki.roll20.net/Macros/Pathfinder_Examples</a>... )appears
to not work on it's own (even if I create a level attribute, or change level to some attribute name I copy and paste from the character sheet), so there is that. The
alternate solution I could see would be to add the npc_athletics_flag
to the athletics or str check. But I am not even sure how you
would go about doing that (or if I am interpreting those fields
correctly). Ideally I would be able to adapt the answer to
saving throw macros and perhaps other things.