Titans (5e Creature)

Titans

Truly rare are the mighty titans, giants born with immense power, and gifted with incredible strength and size, even among the already herculean giants. A fully grown titan stands at least 20 feet taller than the average for its kind, though some tell stories of titans as big as mountains. A titan looks physically very similar to its giant counterparts, though some aspect always betrays its nature; for example, the skin of a fire titan glows like heated metal, while its eyes resemble spheres of lava.

Favoured of the Gods. Giants believe that titans are favoured by the giant gods, and that each titan has an auspicious destiny, such as slaying a ferocious ancient dragon, or creating a work of art that would awe onlookers for countless ages. It is also believed that when a titan dies, its soul joins the gods and all the titans that came before it, while its remains, possessions, and demesne are viewed as sacred by other giants, who await the coming of a new titan to claim all that its predecessor left behind. As such, a titan might count the possessions of a previous titan among its treasures, or live in its former home.
The killing of a titan is seen as tantamount to sacrilege, so giants that learn that a titan was killed will often hunt its killers down, then offer any remains to appease the fallen titan's soul.

Colossal Recluses. Titans are solitary by nature, seldom leaving a favoured lair. A fire titan might claim the caldera of a massive volcano as a home, while a cloud titan's flying castle appears as a tiny speck to all ground-based viewers. However, as a titan invariably holds a high place in the ordning of giants, its presence usually beckons other giants to live nearby. As such, a storm titan's undersea palace might be close to a number of storm giant dwellings, while frost giants might live on a mountain near a frost titan's mighty glacier fortress.

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

gollark: I think all the updater thing would need to do is:on the non-CC side, just track what files changed since the last release, generate a checksum, and either generate an archive or a bunch of URLs for it.on the CC side, periodically check a manifest file, store its own version locally, check if a newer version is available on the server, and if so download the files which have changed.
gollark: Probably gitget.
gollark: I should look at how Opus does its updates, since Opus is generally considered good.
gollark: I see. Your standards for "not too hard" are probably different to mine.
gollark: I mean, git is complicated and has many legacy things behind it, a simple CC updater thing with limited diff-ing capability is still pretty generalizable.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.