Welcome, Guest
Username: Password: Remember me

TOPIC: Beneath Castle Altus - Saturday 11:00AM - Full

Beneath Castle Altus - Saturday 11:00AM - Full 6 years 11 months ago #49

bpsymington wrote:

Arcanist Kolixela wrote:

Donald Rients wrote:

Arcanist Kolixela wrote:

Matthew Hayward wrote: Just a thought - I've got 3 Cabal sets, and we're playing all 5 spell casting classes.

If Druid and Elf Wizard want to equip cabal sets we could get the probably-never-before achieved feat of copying common, uncommon and rare scrolls from the Gloves synergy property.

Anyway - let me know - right now I'm not equipping the full set on Bard/Cleric/Wizard.

I am equipping 3 Bracelets of the cabal, so if 1 more equips it they get +2 spell damage/healing, and if 2 more equip we'd all get +3.


I am running the Cabal bracelets, so if the Elf wants to swap over to them it's +3 spell damage.

As far as the cabal set is concerned I won't drop Gloves of Glory for those terrible gloves, not worth doing IMO



Gosh, I just can't see a great benefit in those sets. I rather have the capability of casting two spells at one when the time is needed..


It requires using up the Gloves slot (costing most builds ring #3) and a Charm Slot (made redundant by the Eldrich 2 piece) AND it's been ruled that you can NOT MEC the second spell cast by the Cabal set (for unknown reasons)

It's useful to cast 2 spells but the drawbacks are severely stacked against the effect.


Not unknown reasons - you can only use the MEC once per round. Lots of tokens with that limitation.

I agree the Cabal set isn't worth the loss of the third ring slot.


There is no activation trigger for the MEC (it does not take your action or free action) and the only interaction in the game it affects is the use of the MEC with the Cabal 3 piece set.

No reason was stated for ruling that the MEC could not be used twice in the turn or that the MEC would double the base damage of both spells cast. Therefore the reasons are unknown.

Please Log in or Create an account to join the conversation.

Time to create page: 0.070 seconds