I love that enchantment has nothing to do with crafting anymore but the current second dominate creature is kind of buggy. You're dropping 3 level spells to dominate those two creatures and that's if they don't save. As a player of a enchantment focused character I wanted to spit out a few ideas to get the ball rolling.
Epic Spell Focus: Enchantment
Dominate: Henchman
First creature dominated (if you have no henchman), becomes a henchman until it dies.
Dominate Person/Monster: AoE small
Dominate Person and Dominate Monster become a AoE effect with a small radius.
Geas/Quest: (Epic Spell)
Caster dominates a creature that fails the will save and remains a loyal servant until it dies. Is a henchman you can summon
and dismiss but once it dies it's gone. Mind Immune negates.
Aura of Empathy: (Epic Spell)
Caster gains +4 to Bluff, Persuade, and Perform when active. Caster is surrounded by an aura that causes a will save vs charm to any that enter.
Aura of Shame: (Epic Spell)
Caster is surrounded by an aura that causes a will save vs, -2 Saves,-4 AC, AB, damage. If will save successful receives -1
Saves, -2 to AB,AC,damage instead
Confusion/Mass Charm: AoE Large-Huge
Charm Person/Person or Animal/Monster: AoE Small
All Charm Spells: Conflicting feelings vs caster
Inflict -4 AB, AC, damage and -2 saves on PC targets due to conflicting feelings, will save for -2AB, AC, damage and -1 saves.
Gain Feat: Slippery Mind
The epic enchanter is a master of the ensnaring the mind, thus is a hard mind to conquer.
Greater Spell Focus: Enchantment
All Charm Spells: +40% Reputation NPC targets
The caster has a stronger influence through their charm (Will fight casters attackers)
Enchantment Suggestions
Moderators: Active Admins, Forum Moderators, Active DMs, Contributors, Area Developers, Artist/Animator, Suggestion Moderators
Re: Enchantment Suggestions
Rejected
BUT if any member of the code team wishes to push any of them forward for further discussion, balance and implementation they can do. I think the thrust of the ideas here are good.
In future try to keep suggestions separate though. It's hard to approve them as a group.
BUT if any member of the code team wishes to push any of them forward for further discussion, balance and implementation they can do. I think the thrust of the ideas here are good.
In future try to keep suggestions separate though. It's hard to approve them as a group.