Katana/Regen Build
Don't feel too bad. Castle has never answered a single PM I've ever sent him, a number of which had nothing whatsoever to do with debuff resistance or */Regen. One of the more interesting ones I sent him was a numerical analysis based on existing precedent that */Regen should actually be allowed to be numerically stronger than all of the other sets it competes with thanks to its animation time use. I really wish he read that, but I have a feeling he doesn't really care about the opinions or analysis of any other players aside from Arcanaville.
|
On the other hand, I do know that Castle doesn't tend to respond to most PMs that tends to start with "I think X should get a buff because." When I first started PMing him about game mechanics, he didn't tend to respond to any of those from me either. Historically speaking, these do not go well or end well for the devs.
** The arguable exception is Willpower, and Castle knows I think Willpower was set too strong in Issue 11. If Castle listened to everything I said, Willpower would have launched a lot weaker than it actually did. But apparently Castle has a lot more spine or I have a lot less influence than most people give credit for.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
On the other hand, I do know that Castle doesn't tend to respond to most PMs that tends to start with "I think X should get a buff because." When I first started PMing him about game mechanics, he didn't tend to respond to any of those from me either. Historically speaking, these do not go well or end well for the devs.
|
Even so, I don't think Castle even thought about the animation time use differences between */Regen and other sets. */Regen is pretty unique in that regard, and you'd only really notice it if you were specifically looking at the comprehensive differences between */regen and the other sets. Trying to point out a specific disparity between a set that already operates on a near completely different scale of effectiveness than everything else is something I'd hope he'd actually look into, especially when you consider that he's been trying to address the whole issue of animation time balance in attacks for a good, long while.
Actually, I've never sent him a PM starting that way. I generally start with asking why whatever I'm sending him a tell concerning is present and then show my evidence. The suggestion is only present at the very end and is almost always a list of potential solutions (with the various pros/cons of each that I could identify). I do realize that he probably knows more than me about the balance of the specific sets, but there are just some things that I wish he would clarify since there seems absolutely no reason why they shouldn't otherwise.
Even so, I don't think Castle even thought about the animation time use differences between */Regen and other sets. */Regen is pretty unique in that regard, and you'd only really notice it if you were specifically looking at the comprehensive differences between */regen and the other sets. Trying to point out a specific disparity between a set that already operates on a near completely different scale of effectiveness than everything else is something I'd hope he'd actually look into, especially when you consider that he's been trying to address the whole issue of animation time balance in attacks for a good, long while. |
That same argument doesn't translate to Regen directly, because the specific argument relates not just to full attack chains, but the average damage output of attack sets when slotted with SOs. Attack cast times have *both* an initial effect (or rather a mid-game effect) and place a constraint on the amount of benefit an attack set can get with recharge bonuses.
Comparing two defensive sets with comparable numbers of clicks, one with higher cast times, would be at least an analogous situation. But when comparing two mitigation sets, one of which has more clicks and one of which has less, two counterbalancing effects of clicks come into play. Clicks cost more than toggles and passives in terms of activity time. But clicks benefit from recharge more (because in general recharge can't benefit toggles and passives). That makes this a far more complex argument to make, and the burden is on the advocate in this case (well, in all cases really).
Its not a new assertion: Castle wasn't a red name when it first came up on the forums back in I4 (I don't think), but I'm assuming he probably saw discussion of it. A lot of regens suggested when the focus shifted from toggle IH to reconstruction that reconstruction's activation cost was in effect applying an offensive penalty on regens. However, there was no way to demonstrate numerically that this offensive penalty wasn't actually part and parcel of the qualitative mechanical difference between clicks and toggles, specifically that clicks could benefit from recharge. In other words, no one has suggested yet why the difference isn't (or couldn't be) an intended difference.
On the subject of uniqueness: Regen is unique - among scrapper secondaries - in terms of its rooted cost, but its not, for lack of a better way of putting it, unique in a unique way. Dark Armor is unique in its endurance penalty. SR is unique in its inability to increase damage mitigation strength with recharge bonuses (ignoring the tier 9 emergency power). Invuln is unique in its movement penalty. Uniqueness alone cannot justify taking action against an intentional qualitative difference. If it did, Regen would lose Quick Recovery: its the qualitative distinguisher among scrapper secondaries with the absolute highest game-balance impact. To be valid, a uniqueness argument must be able to state that, all other things being equal, the thing in question must be specifically equalized. But there is no rule I'm aware of that says, all things being equal, all mitigation sets must have the same number of clicks and incur the same amount of rooted penalty. If a set had to incur the rooted penalty for a large number of clicks but somehow couldn't benefit from recharge or other click mechanical advantages, then that would be a case where a balance argument could be made. That makes the uniqueness observation intrinsically weak as a balance argument. If you had an argument that could justify *why* the imbalance you've calculated shouldn't exist, relative to all of the other qualitative differences that exist, you'd probably have a much more persuasive argument.
(By the way, on the subject of Clicks, its been suggested that there is a rule that says Clicks > Toggles > Passives. To the best of my knowledge, there is no such rule. There is a rule that says in general Toggles are stronger than Passives, but no rule that says Clicks must be stronger than Toggles. If there is such a rule, the original devs didn't follow it, and the current devs consistently ignore it. Clicks tend to be stronger per activation than Toggles, but that's mainly because Toggles activate more often. In *that* sense there is such a rule, but no rule that says the *overall* net effect of a Click must be superior to comparable Toggles). So while there is a qualitative mechanical difference between Clicks and Toggles, there seems to be no requirement that Clicks explicitly end up significantly stronger than Toggles either ignoring those qualitative differences or when completely factoring them in).
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
So then if clicks are benefitted by recharge then give regeneration recharge debuff resistance!!!
Virtue: @Santorican
![](http://i.imgur.com/dmfLZ.jpg)
Dark/Shield Build Thread
However, there was no way to demonstrate numerically that this offensive penalty wasn't actually part and parcel of the qualitative mechanical difference between clicks and toggles, specifically that clicks could benefit from recharge. In other words, no one has suggested yet why the difference isn't (or couldn't be) an intended difference.
|
On the subject of uniqueness: Regen is unique - among scrapper secondaries - in terms of its rooted cost, but its not, for lack of a better way of putting it, unique in a unique way. Dark Armor is unique in its endurance penalty. SR is unique in its inability to increase damage mitigation strength with recharge bonuses (ignoring the tier 9 emergency power). Invuln is unique in its movement penalty. |
The only set that could potentially rival */Regen in the level of difference is Dark and that's only because it uses a different cap on performance. */SR isn't anywhere near as different from the "standard" than */Regen, since, as you pointed out, the only way in which it is unique is in that it doesn't have a method to increase survivability through +rech (which isn't even true because neither do WP or SD), which is, if you look at every other set, a rather minor contribution. Invinc's contributive benefit from +rech is pretty much summed up in more time with DP active. The comparative benefits of that are decent, but not so incredible as to make +rech more important for survivability than offense. Basic SO slotting already provides 66.66% uptime which is great. More +rech isn't going to make the difference completely. +Rech, for every set except for */Regen, primarily an offensive tool. The defensive benefits of it are secondary.
(By the way, on the subject of Clicks, its been suggested that there is a rule that says Clicks > Toggles > Passives. To the best of my knowledge, there is no such rule. There is a rule that says in general Toggles are stronger than Passives, but no rule that says Clicks must be stronger than Toggles. If there is such a rule, the original devs didn't follow it, and the current devs consistently ignore it. Clicks tend to be stronger per activation than Toggles, but that's mainly because Toggles activate more often. In *that* sense there is such a rule, but no rule that says the *overall* net effect of a Click must be superior to comparable Toggles). So while there is a qualitative mechanical difference between Clicks and Toggles, there seems to be no requirement that Clicks explicitly end up significantly stronger than Toggles either ignoring those qualitative differences or when completely factoring them in). |
Essentially, Clicks, Toggles, and Passives should all be balanced but each category of power has additional costs associated with it that the "lower" categories don't have to deal with in. Passives don't have to deal with endurance costs or mez shutdown. Toggles don't have to deal with animation times (or, at the very least, deal with them in an almost nonexistent manner) or being rooted. Click powers have to deal with absolutely everything. If you ignore the mitigation qualities of the powers, you would naturally conclude that Click>Toggle>Passive makes sense, but that's ignoring the factors that actually cause the powers to be balanced anyway (especially considering that sets are balanced as a whole rather than as a set of independent powers).
Well, the bigger problem, as I see it, is that while click powers benefit from recharge, it also increases their costs in the form of animation time. As you decrease the recharge time of the power, there is an exponential (though a slow exponential) growth in the amount of animation time consumed. This translates directly into a reduction in offensive and defensive capability as you have more and more powers competing in ever increasing quantities for a single resource that is never capable of being increased. Sure, you can become more survivable on a */regen, but, by doing so, you're reducing your own damage capabilities as the same time.
|
You're probably thinking that as mitigation root costs increase linearly, offensive opportunity as a percentage of the total decreases inversely. That's a completely different thing.
Well, first things, Invuln has no movement penalty. You may be thinking of Stone |
On the question of uniqueness, you've first got to confront the magnitude of the difference in which the set is made unique. */Regen operates off of a completely different scale than the other sets and uses a completely different mechanism for its contribution. Whereas every set you've mentioned uses toggles and passive powers for the vast majority of its survivability, */Regen uses click powers. Whereas every set you've mentioned uses defense and/or resistance (and mez effects, in the case of Dark), */Regen uses straight up damage recovery (Resilience doesn't count by any stretch of the imagination). Whereas every other set has a decent enough suite of debuff resistance and other debuff countermeasures, */Regen has none. The magnitude of difference between */Regen and every other set out there is huge. |
It doesn't help your case to mention all the ways Regen gets to break the rules in ways that *benefit* the set. Trust me: if the devs had a proper model for Regeneration, Regeneration would be lower. Instead, it was originally set high, then reduced in strength until the datamining couldn't tell it was too high.
Oh, one more thing:
*/SR isn't anywhere near as different from the "standard" than */Regen, since, as you pointed out, the only way in which it is unique is in that it doesn't have a method to increase survivability through +rech (which isn't even true because neither do WP or SD), which is, if you look at every other set, a rather minor contribution. |
2. When SR was designed, Willpower and Shield Defense didn't exist. Its design rules predate those sets, in terms of the unique aspects of the set. I was assuming you were considering the original four scrapper sets, because:
3. Accepting the current state of mitigation sets available to scrappers, its not true that Regen has especially high rooted time costs. Regen has reconstruction, which has a base 0.73 cast time with 60s recharge, and Dull Pain which has 0.73 cast time with 360s recharge. Assume we slot both to 1.95 recharge, and we get a net rooted efficiency cost of 0.73/(60/1.95) + 0.73/(360/1.95) = 0.024 + 0.004 = 0.028, or 2.8%. Fiery Aura has Healing Flames, a 1.5s cast time 40s recharge power. Equally slotted, its rooted cost is 1.5/(40/1.95) = 0.073 or 7.3%. Fiery Aura has nearly three times the cast time cost of Regen. Adding in IH (0.004) and MoG (0.011) doesn't help matters. Regen increases to about 4.3%, which is still only about half the cost of Fiery Aura.
4. The specific ways SR would still be unique, even among all the currently available scrapper mitigation sets is:
a. It has no way to improve on the intrinsic endurance limit for offense, which you can do in one of three ways: improve DPE, increase endurance recovery, or provide an endurance-efficient damage aura. Regen and Willpower have quick recovery. Shield Defense has a +DMG power. Invuln has a tohit buff. Dark Armor has a damage aura. Fiery Aura has an endurance recovery power *and* a damage aura *and* a damage buff. Quickness does *not* do any of those three things, and does not, as a consequence, actually increase the damage per unit time you're capable of generating while obeying the endurance recovery limit. The endurance recovery limit is actually one of the foundational balance pillars of the entire game, which makes this not a trivial difference. In fact, its the difference that comes closest to being game-breaking, because it tampers with a balance-significant parameter (as the devs define balance).
b. It has a large class of attacks which exist at essentially all levels and all ranks for which it has no damage mitigation of any kind, proactive or reactive. There are no such attacks for anything with health recovery, which includes Regen, Willpower, and Fiery Aura. It also includes Invuln on a technicality because DP has a heal, but more importantly and not a technicality Invuln has +health, which acts as resistance against all forms of attack. Even against psionics, Invuln has the equivalent of about 37% resistance with fully slotted DP. Dark Armor has resistance to all damage types. Shield Defense has +health. That leaves SR as the only scrapper mtigation set that has literally *zero* protection against a large class of attacks: non-positional psionics. This is significant because SR's original design didn't intend that: SR was designed to offer protection to all attacks. Non-positional psionics was essentially an override of SR's original design intent.
c. Its the only scrapper mitigation set for which essentially all the damage mitigation powers in the set synergize sufficiently strongly with at least one other power that the set loses more than proportional strength when any one power is eliminated. In other words, SR-1 is significantly weaker than any other set minus one damage mitigation power. That was due to a laudable but faulty design decision. To make sure the SR passives were not seen as "worthless" they added scaling passive resistances to each of them. This meant every passive synergized with each other strongly (in fact, having two provides only about half the resistive mitigation of having three, not 2/3rds - the math is complex to prove it though), and synergized with its corresponding toggle. Removing, say, slotted dodge cuts the passive scaling protection in half, and also increases net incoming melee damage (assuming SO slotting) by 45%. In normalized terms, assuming each positional vector blocks roughly 1/3rd of all damage, removing dodge reduces net strength of the set by over 22%. Without this strong double-synergy, removing any one power should reduce the set by something closer to 1/6th, at least on average: instead the ratio is closer to 1/4.5.
What's specifically unique about SR is that *every* damage mitigation power is like that: all three toggles and all three passives have an incremental reduction factor higher than 1/6 (the passives are about 1/4.5, the toggles about 1/4.2). This interlocking is the basis for the colloquial comment that with SR, you need to take everything. And that runs counter to the design intent for the damage mitigation sets. It should be optional to take any one power, for most powers, with the only cost being a loss of effectiveness proportional to the strength of the power. Some powers will of course be more valuable than others, but overall the average should hold.
Those are the top three on my list. There are a few more that are weaker distinctions, so I'm not including them here. Each of the above is balance-significant working from first principles of the devs' own statements about game balance, or things I happen to know about the design of the game. Collectively, its enough for me to prove beyond any shadow of a doubt that *something* is wrong with SR.
The only reason why none of those problems has been addressed is because Castle holds a trump card: SR isn't underperforming as a result of those problems. That makes it a low priority item to even bother looking at them. My guess is that the same holds true for Regen. Things like MoG were a thorn in Castle's side, but something like reconstruction taking too much time (when its one of the fastest clicks around) is probably too far down the priority list to devote significant time to at the moment. And for *both* SR and Regen, I would tend to agree.
By the way, a significant fraction of Regen's damage mitigation comes from the +health of Dull Pain, which is not a health recovery effect.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
Sry to hijack the thread but I have a single Q for regen folks & I did not feel it warranted a new thread.
If only one person addresses my Q then I feel it's ok.
If one's build has enough recharge to where Reconstruction is on a 20 sec recharge & Dull Pain is perm....can one then conclude Instant Healing is a skippable power. Keep in mind the finished build has base 745% regen.
My thinking is with the recharge & regen, as well as insp, one would feel comfortable skipping IH.
Thoughts & opinions please?
The answer is really going to depend on what you try to do with the character. As much as I love MoG, its short duration and long-ish recharge means it can't turn the tide alone when you're facing too much DPS to survive between Reconstructions. Assuming you can't shut down that DPS by killing foes, then at best, MoG tends to give you one more Reconstruction activation before you find yourself taking on lethal DPS levels with nothing coming back soon enough to save you. This is when I activate IH. (Edit: Well, actually I would often activate it during MoG's duration, and possibly fall back a few yards to regain HP again.)
If you never find yourself in those situations, then it pretty clearly is skippable. I'm of a mindset formed by playing (or playing with people who play) things like capped SR/Shields/Arachnos characters, and so I am prone to want to pile into things that I really have no business trying to survive. For me, that makes IH not skippable. If you're not as insane as I am, you may be able to skip it.
We might revoke your Scrapper card, though.
Blue
American Steele: 50 BS/Inv
Nightfall: 50 DDD
Sable Slayer: 50 DM/Rgn
Fortune's Shadow: 50 Dark/Psi
WinterStrike: 47 Ice/Dev
Quantum Well: 43 Inv/EM
Twilit Destiny: 43 MA/DA
Red
Shadowslip: 50 DDC
Final Rest: 50 MA/Rgn
Abyssal Frost: 50 Ice/Dark
Golden Ember: 50 SM/FA
ty much UG.
I wouldn't skip IH, it is a key power in your survivability.
Virtue: @Santorican
![](http://i.imgur.com/dmfLZ.jpg)
Dark/Shield Build Thread
A whole lot of reading going on here...
And yes IH is nice to have. 90 seconds of darn near unkillable is always welcome.
The answer is really going to depend on what you try to do with the character. As much as I love MoG, its short duration and long-ish recharge means it can't turn the tide alone when you're facing too much DPS to survive between Reconstructions. Assuming you can't shut down that DPS by killing foes, then at best, MoG tends to give you one more Reconstruction activation before you find yourself taking on lethal DPS levels with nothing coming back soon enough to save you. This is when I activate IH. (Edit: Well, actually I would often activate it during MoG's duration, and possibly fall back a few yards to regain HP again.)
If you never find yourself in those situations, then it pretty clearly is skippable. I'm of a mindset formed by playing (or playing with people who play) things like capped SR/Shields/Arachnos characters, and so I am prone to want to pile into things that I really have no business trying to survive. For me, that makes IH not skippable. If you're not as insane as I am, you may be able to skip it. We might revoke your Scrapper card, though. ![]() |
So for me, IH is optional in the same sense that Elude would be optional to SR, if Elude didn't crash and you were not invention-buffed to the soft cap to begin with.
[Guide to Defense] [Scrapper Secondaries Comparison] [Archetype Popularity Analysis]
In one little corner of the universe, there's nothing more irritating than a misfile...
(Please support the best webcomic about a cosmic universal realignment by impaired angelic interference resulting in identity crisis angst. Or I release the pigmy water thieves.)
Oh, I agree. I think I just didn't explain it in a way that made that clear. If I happen to have MoG and/or Recon handy when I realize I'm in trouble, I can use one or both of them to reset my health and then pop IH (or pop IH and let that reset my health behind MoG, etc), then do what you describe.
But yes, if I really know I'm just plain going to need it anyway, I'll just go ahead and activate it proactively.
Blue
American Steele: 50 BS/Inv
Nightfall: 50 DDD
Sable Slayer: 50 DM/Rgn
Fortune's Shadow: 50 Dark/Psi
WinterStrike: 47 Ice/Dev
Quantum Well: 43 Inv/EM
Twilit Destiny: 43 MA/DA
Red
Shadowslip: 50 DDC
Final Rest: 50 MA/Rgn
Abyssal Frost: 50 Ice/Dark
Golden Ember: 50 SM/FA
As a low-recharge Regen, I try to cycle between Dull Pain and Instant Healing in AV fights and the like. Instant Healing gets triggered immediately when it recharges. Dull Pain waits until I'm badly injured. Without Instant Healing, my level of survivability would drop significantly for a little while, and that's when I'd likely get killed.
I wouldn't skip it for normal play either. Normal play has a pretty variable level of danger, and Instant Healing, like other Regeneration clicks, lets you save up your survivability through the easy parts, then spend it on the hard parts in a mad click fest. So if you skip Instant Healing, your top end burst survivability is going to be lower, so you won't be able to crank up your difficulty as much, and you'll have to face lesser enemies through all the boring parts, making them even more boring.
"That's because Werner can't do maths." - BunnyAnomaly
"Four hours in, and I was no longer making mistakes, no longer detoggling. I was a machine." - Werner
Videos of Other Stupid Scrapper Tricks
Before the MoG change, IH WAS my tier 9. MoG was that 2nd skipped power. IH + DP and you can charge in and take on just about any and everything. As a scrapper, I would find it hard and somewhat nuts to skip any power that allowed you to do that.
"All problems can be solved by throwing enough scrappers at it."
@Riez on Virtue, Protector, Champion, and Exalted server.
Credit where credit is due, Santor. I'm the one that designed Val's build. I'm not trying to be a diva, but it's his only because he uses it. The design was by me (and I actually spent a decent bit of time on it so you can understand why I'd want some friggin' credit).
|
![Smile](images/smilies/smile.gif)
Virtue: @Santorican
![](http://i.imgur.com/dmfLZ.jpg)
Dark/Shield Build Thread
Virtue: @Santorican
Dark/Shield Build Thread