Talk:Epic Path: Difference between revisions

From Epic Path
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:
:* create a "circle 0" and update the various mana burning rules for it.
:* create a "circle 0" and update the various mana burning rules for it.


* deflection bonus comes from any magic on the shield, replacing the 'shield enhancement bonus'. does not stack with other deflection bonuses, such as rings of protection.   
* deflection bonus comes from any magic on the shield, replacing the 'shield enhancement bonus'. does not stack with other deflection bonuses, such as rings of protection.  
   
  if we merged 'shield bonus to AC' and deflection bonus into a single bonus, I assume that would mean shields could give a deflection bonus between +1 (un-enchanted buckler) and +13 (+9 enchanted tower shield), and would apply to AC, touch, and ff AC.  By contrast, ring of protection could only give +1 to +9 (also applying to all 3 AC's).  Is this how you envisioned this working?
  if we merged 'shield bonus to AC' and deflection bonus into a single bonus, I assume that would mean shields could give a deflection bonus between +1 (un-enchanted buckler) and +13 (+9 enchanted tower shield), and would apply to AC, touch, and ff AC.  By contrast, ring of protection could only give +1 to +9 (also applying to all 3 AC's).  Is this how you envisioned this working?
as a note, by getting rid of 'shield enhancement bonus', we've effectively cut up to 9 points of AC out of the top end of possible ACs (formerly, +9 tower shield and +9 ring of prot = 22 AC)... we /could/ put some of this back into shields by letting the magic deflection bonus range go above +9 (say, up to +14? that would make a +14 tower shield = 18 AC).  A +14 heavy shield would cap at 16 AC, while a ring of protection would cap at +9.  Regardless of whether we do this, we'll still probably need to review monster to-hits against our projected best AC.


* the SSL cert expires May 5, 2019, so we should get that fixed.
* the SSL cert expires May 5, 2019, so we should get that fixed.

Revision as of 18:20, 2 April 2019