Diamond Knight (5e Creature)

Diamond Knight

Medium construct, unaligned


Armor Class 16 (Card Plate Armor)
Hit Points 35 (5d10+7)
Speed 25


STR DEX CON INT WIS CHA
16 (+3) 9 (-1) 18 (+4) 3 (-4) 6 (-2) 8 (-1)

Damage Vulnerabilities Fire
Damage Resistances Piercing
Condition Immunities Frightened, Charmed
Senses passive Perception 12
Languages
Challenge 1 (200 XP)


Antimagic Susceptibility. Diamond knights are incapacitated while in the area of an antimagic field. If targeted by dispel magic, it must succeed on a Constitution saving throw against the caster's spell save DC or fall unconscious for 1 minute.

ACTIONS

Diamond Spear. Melee Weapon Attack: +3 to hit, reach 5 ft., one target. Hit: 7/9 (1d8/1d10 + 3) Slashing damage.

Spear Gore. (Recharge 1d6+2 Turns) Melee Weapon Attack: +3 to hit, reach 20 ft. Line, one target. Hit: 7/9 (1d10 + 3) Piercing damage.


Diamond knights are one of the four suit related creatures, the others being heart clerics, club bashers, and spade rogues. They exist as minions to the people that summon them and take on traits that their masters have. If a diamond knight's summoner is killed or the summoner relinquishes their control over them, they wander the lands in search of new meaning. Sadly, since they are made out of a very flammable, dissolvable, and all-around destroyable substance, it is borderline impossible to find a diamond knight being hospitalized or finding one in the wilds. When they wish to, they can summon a weapon made out of playing cards made of the suit of that creature. In particular, diamond knights can summon a diamond spear, a long, tri-tip spear that can gore enemies.


Back to Main Page 5e Homebrew 5e Creatures

gollark: Thus bad.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
gollark: If you run too much current through beans they may vaporise/burn/etc.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.