Witcher Potions and Alchemy (5e Variant Rule)

Potions and Alchemy (based on the Witcher)

This page will describe a variation on the base rules to overhaul the potion and alchemy system of the system that frankly dosent work. This will be roughly based on the Witcher series

the main changes this rule variation is to make the potion recipes easier to keep track of. descriptions of each of the ingredients and also a new system to make it easier to keep track and use your potions


Ingredients


Potions

PotionEffectIngredientsPreparationTasteBuying priceSelling price
SwollowExampleExampleExampleExampleExampleExample
CatExampleExampleExampleExampleExampleExample
ThunderboltExampleExampleExampleExampleExampleExample
White HoneyExampleExampleExampleExampleExampleExample

teir 1

name, effect, ingredents, preperation, taste, buying, selling

Cat

Swollow

Thunderbolt

White Honey



Back to Main Page 5e Homebrew Rules

gollark: The first one is the actual data, the second one is metadata (currently just the hash of the data section).
gollark: You are wrong. Anyway, the manifests are effectively just two lines of deterministic JSON (i.e. JSON with all keys sorted and no whitespace, so it'll always hash the same way).
gollark: Eventually I could even start signing the manifests so that you could safely download potatOS from *anywhere* and verify that it's the right thing easily.
gollark: So if it detects a new manifest, it can check the hashes of all stored files, redownload the changed ones, and verify them against the manifest.
gollark: Instead of just having potatOS ping pastebin every five minutes to check for new versions of the main code, it will be able to look for a manifest containing SHA256 hashes of all the files and also cryptographic signatures.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.