Flameborn Pyre (5e Creature)

Flameborn Pyre

Medium humanoid (flameborn), chaotic evil

Armor Class 14 (natural armor)
Hit Points 97 (13d8 + 39)
Speed 30 ft.

STR	DEX	CON	INT	WIS	CHA
18 (+4)	15 (+2)	17 (+3)	10 (+0)	10 (+0)	10 (+0)

Senses darkvision 60 ft., passive Perception 10
Languages Common, Ignan
Challenge 9 (5,000 XP)

Death Burst. When the flameborn dies, it explodes in a burst of fire. Each creature within 10 feet of it must make a DC 15 Dexterity saving throw, taking 10 (3d6) fire damage on a failed save, or half as much damage on a successful one. If the flameborn died because of fire damage, it deals 21 (6d6) fire damage instead.

Ignite (1/Day). As a bonus action, the flameborn can ignite itself for 1 minute. While it is ignited, a creature that touches the flameborn or hits it with a melee attack while within 5 feet of it takes 10 (3d6) fire damage and if the flameborn hits with a weapon attack, the attack deals an additional 10 (3d6) fire damage (included in the attacks). Additionally, the flameborn sheds bright light in a 30-foot radius and dim light for an additional 30 feet and takes 10 (3d6) fire damage at the start of each of its turns. This damage cannot be reduced or avoided by any means.

ACTIONS

Multiattack. The flameborn makes two attacks.

Greatsword. Melee Weapon Attack: +8 to hit, reach 5 ft., one target. Hit: 11 (2d6 + 4) slashing damage. If the flameborn is ignited, it deals an additional 10 (3d6) fire damage.

Longbow. Ranged Weapon Attack: +6 to hit, range 150/600 ft., one target. Hit: 6 (1d8 + 2) piercing damage. If the flameborn is ignited, it deals an additional 10 (3d6) fire damage.

The flameborn pyre is a rarer and more potent variety of flameborn, with the ability to engulf its entire body in flames. A flameborn pyre is more powerful than a normal flameborn, but its fire is much more uncontrollable, burning brightly but only for a short time before it explodes in a burst of flames.

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

gollark: This person apparently reverse-engineered it statically, not at runtime, but it *can* probably detect if you're trying to reverse-engineer it a bit while running.

gollark: > > App behavior changes slightly if they know you're trying to figure out what they're doing> this sentence makes no sense to me, "if they know"? he's dissecting the code as per his own statement, thus looking at rows of text in various format. the app isn't running - so how can it change? does the app have self-awareness? this sounds like something out of a bad sci-fi movie from the 90's.It's totally possible for applications to detect and resist being debugged a bit.

gollark: > this is standard programming dogma, detailed logging takes a lot of space and typically you enable logging on the fly on clients to catch errors. this is literally cookie cutter "how to build apps 101", and not scary. or, phrased differently, is it scary if all of that logging was always on? obviously not as it's agreed upon and detailed in TikTok's privacy policy (really), so why is it scary that there's an on and off switch?This is them saying that remotely configurable logging is fine and normal; I don't think them being able to arbitrarily gather more data is good.

gollark: > on the topic of setting up a proxy server - it's a very standard practice to transcode and buffer media via a server, they have simply reversed the roles here by having server and client on the client, which makes sense as transcoding is very intensive CPU-wise, which means they have distributed that power requirement to the end user's devices instead of having to have servers capable of transcoding millions of videos.Transcoding media locally is not the same as having some sort of locally running *server* to do it.

gollark: That doesn't mean it's actually always what happens.

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