>>[4:22 PM] Estild: The current idea for Rapid Fire (515) is that it would have a baseline -1 second castRT with no cooldown. However, it can then be evoked to grant a -2 second castRT, but after it wears off, the base version of the spell goes on a 2 minute cooldown and the evoked version goes on a 10 minute cooldown. The evoke cooldown can be reduced by -1 second per EMC rank (so can get it down to 5 minutes with max training, benefit is capped at -300). The baseline achieves the numbers we're after, but also gives wizards the opportunity to use it as an offensive powerup (but forces a decision on using it due to the incurred cooldown penalty). It's possible to have 1035 work similarly.

What?

I don't use Rapid Fire - I hate the way it was changed in its current form. But what I hate more is the constant reduction.......no, no, no. Let's call it as what folks will see it as, nerfing.

What's with the constant nerfing of spells to cause more headaches by slowing things down or making the spells/abilities so convoluted that you have to run a script to help utilize new functions? What is so wrong with how 915 works today?

For example, look at the weapon techniques added to the game. Cool features, but none of them trigger automatically (that I've come across) unless you're typing out more steps in your combat.

I ran around with a level 21 TWC warrior for about 20 minutes this evening. Last time I actually hunted him was probably 10-12 months ago. Apparently due to training in OHE he gets weapon technique and one of them is Riposte.
I parry an attack and I get a message saying something about "this would be a good time to Riposte".

Okay...how the hell do I riposte?
I find I can click on the link in SF and it works. Okay, cool. But stopping to move my hand from my keyboard to my mouse and try to click on text that's scrolling up is stupid. Too slow and clunky to really be of use....15 minutes of screwing around and trying to find the info on the gswiki (which I found info about Riposte under Riposte, so that was easy) on how to use the skill, but the info I find doesn't help me learn how to actually utilize Riposte.

Eventually I figured out you have to type out "weapon riposte".....
Why can't the ability just be toggled on/off so it can work automatically for me or not at all? Why do I now have to type out the use of a weapon feat/technique? Why wasn't the system designed to be user friendly and trigger automatically?

Now I have more typing to do....if I want to use these new features....oh joy.
Screw that. Instead of typing out tons of extra lines of text, folks are designing scripts to do things for you....yes, you guessed it - automatically.

Now we circle back around to nerfing of 515 - why? What is reason to stomp all over this spell again?

Will we see the same thing happen to 506?

Will we all of a sudden get told that 513 provides too much of a bolting AS boost with fire lore so we're going to only allow it to trigger once, every 2 full moon cycles during the summer months? Seriously. How much more confusing and twisted are things going to be made?

>>[4:22 PM] Estild: The current idea for Rapid Fire (515) is that it would have a baseline -1 second castRT with no cooldown. However, it can then be evoked to grant a -2 second castRT, but after it wears off, the base version of the spell goes on a 2 minute cooldown and the evoked version goes on a 10 minute cooldown. The evoke cooldown can be reduced by -1 second per EMC rank (so can get it down to 5 minutes with max training, benefit is capped at -300). The baseline achieves the numbers we're after, but also gives wizards the opportunity to use it as an offensive powerup (but forces a decision on using it due to the incurred cooldown penalty). It's possible to have 1035 work similarly.

Could we have "Making the game more fun" (not "more complex") as a higher priority than it currently seems to be on the Development radar when it comes to spell re-re-re-reviews? This is a serious request. I know initially the goal was to make bolts better (RIP) so that having the 515 boost wasn't necessary. When that failed to develop we defaulted back to the nerfed version of the 515 spell that we have now. What new and exciting developments are there for bolt casters that are being planned and developed to roll out in conjunction with the above referenced 515 nerf?

-- Robert

Rex's face lights up as you approach the Gate. He waves happily and says, "It is good to see you back, Faulkil!"

>>If you're a lich user

While I understand the truth behind the simple observation that such a script exists and performs this function, I'm going to come down hard on the other side.

This game should neither be designed nor developed with the understanding that Lich can actually make it playable / enjoyable.

I'm relatively sure that the only real consideration the GMs give to Lich is how badly they might break existing Lich features if they follow a certain path. And even then I would bet it's not a deciding criterion, but may be reflected in information the GMs choose to share if it ever really becomes problematic.

But designing the game from a playability / enjoyment view? I surely hope not!

That having been said - don't change 515 (again). Give wizards other reasons to not reach for it, don't slow the game down when they do.

Doug

>>but 99% of the time...yeah.

Yep! Don't take it as a knock. . . I'm very happy it can be done. I'm just not happy that it needs to be done to be playable / enjoyable.

Doug

>> I think some context has been lost here, because the answer to this...

Hey Leafiara - Thank you for providing the additional context!

>> Ideally, if we did a Wizard Review, we could make the actual elements more for roleplay, then actual damage.

Just throwing out my two silver... I'd like to see the actual elements for wizards be both roleplay and mechanically diverse. e.g. A fire wizard could do 'fire things' but would not have access to some of the cool 'ice things'.. Air wizards would be faster, fire wizards would be damage heavy, earth wizards would be crunchier, etc... choices that are meaningful from both an RP and a gameplay perspective. Is that more work? Yup. Is it way cooler? I think so.

>> Divergence

I have no idea what this is. :p

-- Robert

Rex's face lights up as you approach the Gate. He waves happily and says, "It is good to see you back, Faulkil!"

Okay, but the quote in the OP comes from 9 minutes earlier in exactly the same Discord conversation as the Divergence quote, and the conversation happened in, well, the Divergence thread...

Either way, I don't have any larger point to make here. I mostly just didn't want people who don't follow Discord to read about something that might or might not happen and think of it as something that's definitely going to happen. By all means, if you think it's a bad direction, now's definitely the time to explain why. In fact, his very next line after the quoted one about Rapid Fire was:



Estild — Yesterday at 1:23 PM
I also forgot to mention that we'd implement the current versions of the spell updates we're planning in the long term as the Divergence version. So if the 515 idea above is well received, then that will be the Divergence version of it. It also makes it easy for us since we'll already have the global version designed and coded when it comes time.



Emphasis on "if" and "well received."

>> Okay, but the quote in the OP comes from 9 minutes earlier in exactly the same Discord conversation as the Divergence quote, and the conversation happened in, well, the Divergence thread...

I pulled the quoted text from the post here on the officials prior to mine (post 1890). I don't spend any time on Discord.

Part of the joy of having multiple communications channels where information is inconsistently communicated. I appreciate your (and others) attempts to make that less of an issue. :-)

-- Robert

Rex's face lights up as you approach the Gate. He waves happily and says, "It is good to see you back, Faulkil!"