3e SRD:Snake, Medium-Size Viper

This material is published under the OGL

Medium-Size Viper

Size/Type: Medium Animal
Hit Dice: 2d8 (9 hp)
Initiative: +3 (Dex)
Speed: 20 ft., climb 20 ft., swim 20 ft.
AC: 16 (+3 Dex, +3 natural)
Attacks: Bite +4 melee
Damage: Bite 1d4-1 and poison
Face/Reach: 5 ft. by 5 ft. (coiled)/5 ft.
Special Attacks: Poison
Special Qualities: Scent
Saves: Fort +3, Ref +6, Will +1
Abilities: Str 8, Dex 17, Con 11, Int 1, Wis 12, Cha 2
Skills: Balance +11, Climb +11, Hide +12, Listen +9, Spot +9
Feats: Weapon Finesse (bite)
Climate/Terrain: Temperate and warm land, aquatic, and underground
Organization: Solitary
Challenge Rating: 1
Treasure: None
Alignment: Always neutral
Advancement:


Combat

Skills: Snakes receive a +4 racial bonus to Hide, Listen, and Spot checks and a +8 racial bonus to Balance checks. They can use either their Strength or Dexterity modifier for Climb checks, whichever is better.

Poison (Ex): Bite, Fortitude save (DC 11 for all sizes Large and smaller, DC 13 for a Huge viper); initial and secondary damage 1d6 temporary Constitution.



Back to Main Page 3e Open Game Content System Reference Document Creatures

This page is protected from editing because it is an integral part of D&D Wiki. Please discuss possible problems on the talk page.

Open Game Content (place problems on the discussion page).
This is part of the 3e System Reference Document. It is covered by the Open Game License v1.0a, rather than the GNU Free Documentation License 1.3. To distinguish it, these items will have this notice. If you see any page that contains SRD material and does not show this license statement, please contact an admin so that this license statement can be added. It is our intent to work within this license in good faith.





gollark: I would probably also drop forms since their functionality is fairly easy to replicate with the scripting capabilities.
gollark: Oh, and in terms of arbitrary preferences, I'd probably make some of the web APIs more functional programming™️ instead of using objects; instead of `URL` objects, you would just have a `parseURL` function returning a table of URL components, and `serializeURL` function... unparsing it.
gollark: Well, also the web is gigantically complicated and there's no hope of dislodging it.
gollark: WebRTC is overcomplicated and no, so an alternative API would... allow you to listen and send on high-numbered TCP/UDP ports, or something? Not sure of the exact implications of that.
gollark: The user agent is stupid and would instead be feature flags.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.