-
-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legendary Action Count and Descriptions are Missing #344
Comments
Whether this was omitted because of the redundancy you mention, or simply through oversight, I can definitely see a case for including the number of legendary actions a creature can take. Even though all of the creatures in the SRD can only take 3, some creatures in the Monster Manual can take 4, so it would be useful for people extending the data for personal use. |
I actually like option 4 best even though it's changing the schema. |
One nuance with this block is that the way it refers to a monster isn't currently present in data or could be easily derived from it. E.g. I templated it with monster's name and it produces output such as |
Heh. That's fair now that we've split forms out like that. We would either a separate field for the regular name without the form, or we don't include the form in the name and have it be a separate field. |
In order to use Legendary Actions at least knowing the count is important. Within the SRD document Legendary Action counts and descriptions are included, so I'm unsure any reason this couldn't be included.
As an example for the Ancient Red Dragon:
I think this could be added in the following ways:
legendary_action_count
andlegendary_action_desc
fields to the Monster schema. This is simple and straight forward.Monster.legendary_actions
array which includes the description text, similar to how Mulitattack is presented. I don't like this solution because Multiattack fits the formatting of all other actions, and thelegendary_actions
does not meet the formatting of all other legendary actions. It could be argued this is similar to the spell casting special ability.special_abilities
array, similar to the Spell Casting feature.legendary_actions
is an object withdesc
,count
, andactions
are fields. This is a breaking API change so it's probably not wise to do it.There are 29 monsters with legendary actions in the current json data, so I've pulled the description text for all of them (actually, 29 in the json, 30 in the SRD, I've submitted a PR to add legendary actions to Adult Brass Dragon #346):
The only thing I'm unsure of is that it seems each creature with legendary actions has 3, so not including this field could have been a conscious decision, but if that's the case I'd still argue this is useful information for people using the API.
The text was updated successfully, but these errors were encountered: