Much facepalm. Couldn't read past this one, was entertaining for a while but to be able to answer your own question so obviously without realizing it either means you're the dumbest person alive or an obvious troll. I truly hope for your sake that it's the latter.Please read the previous posts that already address this before commenting. Swiftsong is not meant to be used for any battle purpose which negates it's importance in this topic. Stoneskin is directly for battle use, along with sneak/hide which can also be used under certain circumstance during a fight. Please understand the game more.
What about Hide from Rogue? It is not possible to use it during combat and there would be an adventage to use it during battle (enmity reset).There is no advantage to having swiftsong in battle. There is an advantage to having stoneskin in battle. Swiftsong was designed to be used outside of battle only, not for pre-engagements like stoneskin 2. And considering they already gave us an aoe version of stoneskin in the past it just doesn't make sense that they would bring it bake the way they did. It's a slap in the face to people who play whm.
Is the fact that we can't use Hide during combat also a design flaw?
Last edited by Felis; 12-10-2014 at 12:58 AM.
This thread is pretty hilarious. I gotta say, though, I would've prefered that SE made the aoe thing part of the Graniteskin trait, rather than making it a seperate skill from Stoneskin.
Cast Stoneskin inside of combat? Behaves as usual.
Cast Stoneskin outside of combat? Applies Stoneskin in an aoe around the target.
Having to allocate hotbar space for an ability that can only be used outside of combat is a pain. Pretty much have to make it part of a macro, instead.
/ac "Stoneskin II" <me>
/ac "Stoneskin" <t>
Well i understand it why they didnt include it as a part of the original SS.
SS1 is like 2.5sec cast time
SS2 is 5.7sec.
They prob thought that we would be overwhelmed by all the time saved if SS2 had a 2.5sec cast time too, so they got the great idea to give it an absurdly long cast time.
And now people dont even wait til i cast it.
And before you bring this, no i wont waste SC at the beginning of a dungeon / primal for SS2.
Last edited by CUTS3R; 12-10-2014 at 03:49 AM.
omg... which part of your brain cell died?
Individually buffing a full party during progression runs where you spend most of your time wiping gets old fast. Im so glad we finally got this spell![]()
You have to keep in mind that this was added purely for pre-engagement convenience, and nothing else. It doesn't matter whether it's its own spell or an added trait, the fact remains that its sole intended purpose is to make the party buffing (before battle) faster. You can still use Stoneskin normally during battle.
What are the alternatives? Removing the time-saving convenience of this spell in the next patch? Making it work during battle? Both of these options are ludicrous, if you ask me.
Your suggestion to make it usable in battle with a very long recast time is interesting, but it would nevertheless make certain mechanics a lot easier through this skill alone. Additionally, it wouldn't solve issues where a very quick wipe happens with the skill still being on cooldown.
Last edited by Holy-chan; 12-10-2014 at 04:24 AM.
Well, then you should be happy with it, because it CAN be cast during battle. That's what the regular Stoneskin is. It's the in-battle version of Stoneskin II. This is just an adaptation of it so that when out of battle you can cast it on everyone at once. In battle, it obviously has to be on one character at a time.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.