Turtle People (5e Creature)

Turtle People

Medium humanoid (lizardfolk), neutral


Armor Class 18 (Natural armor)
Hit Points 22 (1d8+4)
Speed 20 ft., swim 40 ft.


STR DEX CON INT WIS CHA
15 (+2) 10 (+0) 13 (+1) 7 (-2) 12 (+1) 7 (-2)

Skills Perception +3, Survival +5
Senses passive Perception 11
Languages draconic, aquan
Challenge 1 (200 XP)


Hold Breath. The turtle people are able to hold their breath for 30 minutes, making it easy for them to swim under things like ice, or through a subcutaneous cavern that is full of water to get the drop on their enemies.

ACTIONS

Multiattack. The turtle person can make any 2 melee attacks.

Shell. Melee Weapon Attack: +4 to hit, reach 5 feet, one target. On hit: 7 (1d6+4) bludgeoning damage.

Mace. Melee Weapon Attack: +4 to hit, reach 5ft., one target. On hit: 9 (1d6+6) bludgeoning damage.

Bite. Melee Weapon Attack: +4 to hit, reach 5 ft., one target. On hit: 6 (1d6+3) piercing damage.


Turtle people are much like lizardfolk, except for a very distinct difference. They will go out of their way to save humanoids from the lizardfolk, but not because of some higher morality, but because they absolutely hate the lizardfolk. Turtle people have no sense of morality aside from the basic thoughts of honor, do not kill what has not attacked you. They are powerful creatures that love to train their children, to help them keep themselves safe, and once their training is complete, they are seen as mature warriors. Turtle people tend to stay under the water as they are faster under water and they can build entire communities underneath the waves out of coral, ocean rock, even sunken ships, anything to keep themselves hidden from humanoids. All they want is to be left alone and undisturbed from humanoid interference, and to stay away from their distant cousins, the lizardfolk.


Back to Main Page 5e Homebrew 5e Creatures

gollark: Basically.
gollark: Thus bad.
gollark: Go encourages ways of programming which I consider bad and discourages/prohibits ones I think are good.
gollark: You seem to have missed what I've been saying.
gollark: Go generics seem to be basically just "you can make a data structure/function which contains/accepts anything matching whatever interface" which is the obvious way and rather nice.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.