[dev1024] Job adjustments - RDM

[Kitkat]

Yes, but you aren't SE. They are notorious for taking a good idea, turning around and implementing it and making it weaker or less useful (Decoy shot, nerfed heavy strike, etc). So regardless of what you want out of this line there is possibility it will still end up being just as useless and previously existing iterations of the proposed spells. As already shown, other source versions exist and aren't useful enough to cast regularly because of duration, resist rate, or cast/recast of the spell.

Thing about spell ideas is you have to put a lot of "what if" into the planning. Say they do add these spells and they are good, but they forget to think about previous existing spells that create similar effects. Players figure out that they can stack and begin to do so creating a new form of unexpected balance issues. Thus said spells become weaker, or then can't be stacked causing one to overwrite the other creating a "uselessness" to the spells introduced since they now are only worth while for messing around or low-man lesser NM fights.

Call it pessimism, but SE is very good at making something sound good with hype, then failing to really deliver after implementation.

[saevel]

Yes, but you aren't SE. They are notorious for taking a good idea, turning around and implementing it and making it weaker or less useful (Decoy shot, nerfed heavy strike, etc). So regardless of what you want out of this line there is possibility it will still end up being just as useless and previously existing iterations of the proposed spells. As already shown, other source versions exist and aren't useful enough to cast regularly because of duration, resist rate, or cast/recast of the spell.

Thing about spell ideas is you have to put a lot of "what if" into the planning. Say they do add these spells and they are good, but they forget to think about previous existing spells that create similar effects. Players figure out that they can stack and begin to do so creating a new form of unexpected balance issues. Thus said spells become weaker, or then can't be stacked causing one to overwrite the other creating a "uselessness" to the spells introduced since they now are only worth while for messing around or low-man lesser NM fights.

Call it pessimism, but SE is very good at making something sound good with hype, then failing to really deliver after implementation.

I agree, but that applies to EVERY single spell / ability in the game. It's like the universal disclaimer when referring to SE doing something.

I specifically chose those because their the hardest to screw up. Out of all "enfeeble" ideas, the ones that are the easiest to mess up are the complex ones due to requiring SE to get multiple factors correct. The hardest to mess up are the direct ones with the fewest variables. Look at Dia III vs Paralyze II. On paper Paralyze II would seem awesome, when the monsters use it on us it's potent and has a chance to block spells, attacks, JA's and items. So putting it on the monster would be a good idea. Except in SE's work, the effectiveness is vastly diminished, monsters don't use JA's or items, and their spells seem to be mostly immune to the effects. The things you absolutely want it on would be NM's, their regular attacks can be dangerous, except it doesn't work on most of them. So in reality Paralyze II is mostly useless. Dia III on paper is just Dia II +5%, it lasts 30~2:30 seconds and does 3hp/tick damage. On paper it looks kinda meh, but in actuality it's awesome. Monsters can't resist it, it will always hit for 15% defense down, and the math of the game lends exponential gains to stacking defense down. Dia III ends up being 17.6% attack bonus to every single alliance member, and even the BLU spells's and pets's get the attack bonus, a group that has no other way of enhancing their "attack". In actual usage Dia III is our most potent and useful spell.

So I say again, those above listed debuffs would be the simplest. Cast spell, monster does resist check, if fail then monsters stat is reduced based on your MND or INT or whatever.

[cidbahamut]

On paper Paralyze II would seem awesome, when the monsters use it on us it's potent and has a chance to block spells, attacks, JA's and items. So putting it on the monster would be a good idea. Except in SE's work, the effectiveness is vastly diminished, monsters don't use JA's or items, and their spells seem to be mostly immune to the effects.

I'm sorry, but what? Paralyze interrupts NM spellcasting plenty, it's just not as frequently seen as an attack getting interrupted, but that's because there are generally more normal attacks being performed over the course of a battle than there are spells being cast. So...yay for eyeballing?

As for stat down enfeebles, are elemental debuffs still in fashion? Because I can't recall the last time I saw anyone bother to cast them and all they are is a stat down effect with some mild DoT, which seems to be what you're pushing for.

[saevel]

I'm sorry, but what? Paralyze interrupts NM spellcasting plenty, it's just not as frequently seen as an attack getting interrupted, but that's because there are generally more normal attacks being performed over the course of a battle than there are spells being cast. So...yay for eyeballing?

As for stat down enfeebles, are elemental debuffs still in fashion? Because I can't recall the last time I saw anyone bother to cast them and all they are is a stat down effect with some mild DoT, which seems to be what you're pushing for.

I tend to ignore you whenever possible, but just this one I'll reply.

Nearly every HNM is straight up immune to paralyze, as in I can cast it with 415+ enfeebling skill, tons of M.acc and HQ Ice staff, and it's still resisted 5/5 times. After that I just stop trying to land it. The few HNM's that it does land on have a pure potency reduction from 50~80%. Basically it won't even proc, and if it does it'll be a one shot thing. On anything not HNM / super immune then Paralyze II is awesome. While we fought the Tiamat v3 inside Ifrits Cauldrin one of my jobs as a RDM was to hold the baby off in a corner. It was ridiculous, hit it with Para II and I would get a good 40%+ proc rate, it was visibly noticeable. This tells me that the spell's mechanics are not weak, but that SE is deliberately making their NM's resistant to it to prevent us from using it. They are doing to Paralyze II what they did to Silence, Sleep, Gravity and Bind. Dia III on the other hand is unresistable, it's effect will always proc and always at full potency on every HNM ever created or that will ever be created. It's a guaranteed 17.6% increase in everyone's attack (actually more with Emp armor) and that is amazing. It's like berserk on everyone in the alliance.

As for the element enfeebles, you might want to go check up on them. Their -stat effect doesn't scale well. At 150+ INT it's only -13 stat. They also don't stack well, I can't reduce the monsters VIT and AGI at the same time. They use elemental skill not enfeeble skill and thus we'll always have issues landing them at high potency. What I'm arguing for is a pure enfeebling skill line of -STAT enfeebles that actually scale. Something on the order of a reverse Gain spell, -20 ~ -30 of a Stat is noticeable. Also don't limit it to just the STR / DEX / VIT stats but also include the enfeeble effects of Attack Down, Defense Down, Evasion Down, and so forth. These already exist, in the WAR break WS and several BLU spells. Also the monster use them constantly on us. If SE wanted it would be trivial to create these, you cast it and the monster checks resistance. If pass then land for an effect determined by your INT and call it a day.

It would give us a new line of enfeebles that would work in HNM situations and would give us a unique role to play. Sticking a bunch of those on any HNM would make it weaker. It wouldn't' break the game as the NM still has access to all it's OMFGBBQ moves and you haven't blocked any of it's actions. SE broke all our previous enfeebles because if they work, they work too well and block a NM's ability to do stuff.