Nidhogg (5e Creature)

Nidhogg

Large dragon, any evil alignment

Armor Class 15 (natural armour)
Hit Points 76 (9d10 + 27)
Speed 30 ft., fly 60 ft.

STR	DEX	CON	INT	WIS	CHA
18 (+4)	12 (+2)	16 (+3)	7 (-2)	12 (+1)	10 (+0)

Damage Immunities poison
Condition Immunities poisoned
Senses blindsight 10 ft., darkvision 60 ft., passive Perception 11
Languages Abyssal, Common, Draconic, Infernal
Challenge 6 (2,300 XP)

ACTIONS

Multiattack. The nidhogg makes three attacks: one with its bite and two with its claws.

Bite. Melee Weapon Attack: +7 to hit, reach 10 ft., one target. Hit: 11 (2d6 + 4) piercing damage, plus 5 (2d4) poison damage.

Claw. Melee Weapon Attack: +7 to hit, reach 5 ft., one target. Hit: 9 (1d10 + 4) slashing damage.

According to legend, the nidhogg were once gigantic feathered dragons that roamed the planes freely, gorging themselves on whatever they could find, until they were banished by the gods to the Lower Planes. Now, they are scaly and serpentine, and they hatch foul plots and make alliances with unspeakable evils, awaiting the day that they can strike against the gods that imprisoned them there.

Back to Main Page → 5e Homebrew → 5e Creatures

gollark: Then, I just gave up and compiled it on my other thing with an older kernel, where it eventually worked.

gollark: I decided to look at the code in more detail. This was a mistake. It contained thousands of lines with minimally useful comments, for some reason its own implementation of hash tables (this is very C, I suppose), and apparently its own implementation of WiFi mesh things even though that should really be handled generically for any device.

gollark: After I was able to work through git's terrible CLI enough to make that work, and "fixed" some merge conflicts, it somehow compiled still, but upon plugging in the thing, hung things again. I had dmesg open, and apparently it was a page fault somehow in the code assigning names or something?

gollark: Then I noticed that they had merged patches a lot from the repo for a similar wireless chip, so I decided to just try and merge the "kernel 5.10 compatibility" thing from that, which had not made it in yet.

gollark: There was a repo on GitHub for doing that with it, but `insmod`ing it after compiling *somehow* hung my kernel so I had to reboot.

This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.