What the response contains
Try aboleth, goblin, and dragon-turtle and use the returned fields to identify the right record.
Fields worth checking
- index + name
- type + size + alignment
- armor_class + hit_points
- speed + senses
Type a real query, scan the cards and confirm the key details before opening the full source.
Try aboleth, goblin, and dragon-turtle and use the returned fields to identify the right record.
Fields worth checking
A goblin lookup returns index, name, size, type, subtype, and alignment. index is the identifier used by the route; name is the displayed name. size, type, and subtype describe classification, while alignment gives the alignment stated for that entry. These fields help prevent a similar name from being treated as the wrong creature.
armor_class is a list: goblin has value 15 with armour and shield, while dragon-turtle has natural defence value 20. hit_points and hit_dice appear together, such as 7 and 2d6 for goblin. speed is an object, so walk, swim, or other modes can coexist. Read the defence type and every movement mode instead of keeping only the first number.
actions can include name, desc, attack_bonus, damage, dc, and grouped actions. Goblin has Scimitar and Shortbow; dragon-turtle has Multiattack, Bite, and Claw. special_abilities, reactions, and legendary_actions may exist or be empty. Read desc and the structure of each action before adding damage or deciding how many actions occur on a turn.