Ritual Casting Skill (3.5e Variant Rule)

This material is published under the OGL

Ritual Casting (Con; trained only; armor check penalty)

This skill is a class skill for any full-advancement spellcasting class.

You have learned to endure the rigors that are required to perform rituals. You can handle the long duration of the casting required to draw in extra magical power.

Check: You can attempt to cast augmented and combined ritual casting spells that require an hour or more of casting time. Each hour, or portion thereafter, requires a Ritual Casting check against a DC of 10 + spell level. Each check after the first one increases the DC by one until the end of the casting. A failed Ritual Casting check results in loss of control over the magical powers being harnessed. See Augmented and Combined Ritual Casting sections for results of the failure.

Retry: No.

Special: If you have 5 or more ranks of Concentration, you get a +2 synergy bonus on Ritual Casting checks.


Scarred Land Campaign Setting: Ghelspad Copyright 2002, White Wolf Publishing, Inc.

Permission to use this content granted via "Designation of Open Game Content", page 1, Relics and Rituals. Alterations were made to this entry to bring it in line with the 3.5 rules set.

Back to Main Page Publication List Publishers White Wolf Publishing Relics & Rituals
Back to Main Page 3.5e Homebrew Character Options Skill Abilities Skills

Open Game Content (place problems on the discussion page).
This is Relics and Rituals. It is covered by the Open Game License v1.0a, rather than the GNU Free Documentation License 1.3. To distinguish it, these items will have this notice. If you see any page that contains OGC material and does not show this license statement, please contact an admin so that this license statement can be added. It is our intent to work within this license in good faith.
gollark: Maybe this needs its own component in Rust for something something high performance.
gollark: I could use a bincode-type thing, chunk messages into groups of maybe a thousand each, and run them through zstandard compression, and then have a few uncompressed statistics, but I don't want ABR to store too much state in memory.
gollark: Maybe it should gather data per hour. Or I could try and actually design some extremely densely packed representation.
gollark: Message contents and timestamps would be too big unless I have some ultra-compressed packed form.
gollark: That is a display issue. I'm talking about what needs GATHERING.
This article is issued from Dandwiki. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.