Talk:True Immunity (3.5e Feat)

Ratings

Ghostwheel opposes this article and rated it 0 of 4.

I'm not rating this on power, but rather on system design. Heck, from a power standpoint, it should really be Unquantifiable, since giving an undead monster true-super-real immunity from Disease or something similar is kinda weak and would not fit VH. With that said, immunity in a system against something players use fairly often is not a good thing. It strongly limits their options in the worst way possible at best, and at worst causes them to lose one or more turns until they figure out if the creature is outright immune to whatever they have. Because immunity is such a bad thing, abilities that allow that immunity to be pierced and for abilities to stay relevant are good. This... does the opposite of that. Which is why its very concept is bad for the system as a whole.

Leziad opposes this article and rated it 0 of 4.

I changed my rating, time and repeatedly seeing the effect of this feat really really soured it in my view. I will agree on Ghostwheel that this is poor system design. Firstly if a PC take it it worse than Toughness. Yes, fricking Toughness. At least the 3 hit poinst are going to come up much much much more often than the benefit of this feat. It is best used on damage immunity, such as immunity to cold or fire. However while some PC class allow you to bypass such resistance, alongside pure elemntal weapons, it is very rare that those things are used on NPCs. I cannot on the top of my head of a single monster which bypasses immunities, or at least in a way that matter. Secondly if used on a monster, it will ridiculously fuck over the PC who can bypass immunity. There a reason some classes grant the ability to halves it, it because being not able to do anything in combat really really blow.

	Foxwarrior likes this article and rated it 3 of 4.
	The arms race is over. Although it's too bad that this feat will usually matter so rarely. For a proper Very High experience, it should really apply to all of the character's immunities.

	Eiji-kun likes this article and rated it 3 of 4.
	The arms race begins. In all seriousness, it serves its purpose well. Especially in VH games where this is an issue.

Interaction with Energy Anti-Resistance

The Energy Anti-Resistance ability I came up with has 3 tiers — ability to overcome resistance, ability to overcome immunity, and ability to overcome absorption. Energy absorption is already a logical next step up from immunity; you don't merely take no damage (or suffer no ill effects) from an effect of that energy type, you actually get healed by it (or get some other benefit). Thus, for the purpose of anti-resistance, I'm not sure what this feat should do. Should it merely block capacity to overcome immunity (thus making the immunity into pseudo-absorption), or should it outright defeat energy anti-resistance, even if it overcomes absorption? My default interpretation is the former, and I just tweaked the article to say as such, but I felt that you should be made aware so you can change it if you disagree. Also, if it does merely negate ability to override immunity, should it be possible to take the feat twice for a given energy type to negate the ability to override absorption as well? Hey, it's an important question, and I want to hear what you think. --Luigifan18 (talk) 15:16, 30 September 2015 (UTC)

I missed you making this change until just now. Honestly this shouldn't need to be said, but I'll leave your example up (though without the needless explanation). I'd hoped the text was pretty clear: You are immune to something, you cannot be damaged by it in any way, full stop. If you have true immunity AND absorption to a particular element, and are hit with something that deals that element and overcomes absorption, you would still take no damage, you just wouldn't be healed by it. Absorption isn't actually immunity, the effect merely functions as such mechanically. It doesn't necessarily follow that something that overcomes absorption also overcomes immunity, because they are two separate, unrelated mechanics. If you'd like to treat it that way, fine, but it still shouldn't get around this feat. -Spanambula (talk) 06:25, 19 February 2016 (UTC)

Response to Ghostwheel's oppose rating

(yeah, this is old, but I've just come back from hiatus and am reviewing things with a fresh eye)

First, you were right, this should be Unquantifiable, so I fixed that. "I'm not rating this on power, but rather on system design." Nice to know your opposition isn't related to the mechanics of my feat, it's just because you don't like the idea of immunity. I mean, I'll agree to disagree with your playstyle views sometimes, but this argument is ridiculous. "Because immunity is such a bad thing..." is one of the most ludicrous things I've ever seen you write. So in your view, fire elementals shouldn't be immune to their own element? Wights should give themselves negative levels when they scratch their armpits? The fact is that immunity is a vital part of creature design to the D&D system. If you don't like it, fine, but that's not a valid reason to oppose something.

Secondly, "immunity... against something players use fairly often is not a good thing" is arguing against DM playstyle, not the feat. I agree that a DM who designs all his encounters to neutralize all his players' abilities is a bad thing. But I also think that a game where players can use the same ability to overcome every encounter is equally bad. Good game design should use a variety of encounters that challenge players to think creatively, which does carry a risk of frustrating your players until they figure shit out. Either way, it has nothing to do with the function of this feat, so I'd appreciate you not claiming my feat shouldn't even be on the wiki just because a DM could potentially use it to be a dick. Please either provide a legitimate reason for opposing this article or change/remove your rating. Spanambula (talk) 21:24, 20 February 2016 (UTC)

Response to Leziad's oppose rating

First things first: I'm going to break standard procedure and compare wiki material to other wiki material rather than source material, since there's precious little in 3.5e/pathfinder that lets you overcome immunities. So. Again, this is a niche ability designed for VH play with fairly high-level or even Epic level parties. Saying it's worse than toughness because it won't come up often is just silly in a wiki full of fairly niche feats. But suddenly Leziad doesn't like immunities. Well I do. I'm also not a fan of the ability to overcome immunity being handed out like candy to anyone with a few thousand gold for the appropriate weapon enhancement. It makes thematic sense in the case of some classes based around a specific damage type (like the flammenwerfer), but for the most part I'm pretty skeptical. Why? Because there are already a host of workarounds. Fire immunity? Here, have hellfire. Have light damage. Radiation damage. The wiki has all sorts of weird energy types that almost nothing has any defense against. But I guess the inability for some PC's super-special fire to be super effective all the time every time is a bridge too far.

I evidently didn't convince GW of this since he never responded (surprise.), and I probably won't convince Leziad, but I'll try. Because here's the thing: "it will ridiculously fuck over the PC who can bypass immunity. There a reason some classes grant the ability to halves it, it because being not able to do anything in combat really really blow" is a complete bullshit argument. You know what also really really blows? Being a caster in an AMF. Being a fighter stuck in a resilient sphere. Being a vanilla rogue in a dungeon full of undead, constructs, and oozes. Being a melee brute who's being attacked by aerial foes. Fighting in fog or magical darkness. Failing save-or-sucks. A whole slew of negative status effects. Getting Time Hopped. Getting Mazed. Being out of spells. Being out of GOOD spells. Being out of power points. Getting dominated and attacking your own party. When your dice decide they hate you and you fail stuff you should be really awesome at for entire encounters. And so forth. D&D is a game where crappy, neutralizing shit happens A LOT to the players. True Immunity is not an insurmountable hurdle for a party, it just isn't. Ghostwheel's argument about it costing the PCs a turn or two in figuring out what tactics to use being game-breakingly bad design still makes me headdesk with the sheer illogic of that statement. I guess all encounters should start and end with the PCs knowing exactly how to effectively fight every foe, no matter what, and if they don't then get your shit off the wiki.

If you're any kind of decent DM and you know that you're going to (for example) negate your flammenwerfer in a party that's gearing up to face the Fire-Faced Flame Demon of Flamey Fireflame by giving the demon true immunity to fire, give the werfer something else to do. Provide mooks the werfer CAN hit. Have support opportunities. Maybe he finds some kind of energy admixture weapon. Hell, if your party is high level already, have them appeal to a deity who can bless their weapons with its power to the degree that they overcome the True Immunity. This is not hard. I don't know how else to say this. This feat isn't intrinsically dickish by any reasonable definition in a game that already provides varying degrees of resistance, immunity, and a wiki full of things that ignore them. Like Ghostwheel's argument, yours comes down to arguing playstyle, and like GW, you're claiming this feat is bad game design by virtue of being an extension of an integral mechanic of the game. That makes NO sense. If you don't like immunities in general, fine, give this a 1 or something. But I'm not going to listen to your objection if all you're actually saying is "Span, your fun is wrong" because of your playstyle preferences. This is no different than saying "I think Dragons are bad for the game, therefore your draconic feat gets a 0 rating.- Spanambula (talk) 01:00, 6 February 2017 (MST)