Swiftcast Ability Glitch

ISP:
Shaw

Type of Internet Connection:
Optic Fibre High Speed, connecting via stable WiFi.

Internet Connection Speed:
Unsure, can provide if absolutely needed

Date & Time:
Multiple times/ dates since patch 3.5.

Frequency:

Sometimes, very frequently/ sporadically, chooses to happen randomly and is increasing in frequency/ getting worse.

World:
Moogle

Character Name:
Mors Caelum

Retainer Name:
None

NPC Name:
None

Monster Name:
Several monsters, mostly boss monsters, raids and expert dungeons, haven\\\\'t done a low level dungeon in a while.

Class/Level:
White Mage, 60.

Party or Solo:
Party. It only occurs when I\\\\'m in a party, and it\\\\'s anywhere between 4-8 players, up to the 24 man raids.

Race:
Hyur M

In-Game Time:
Several dates and times, too many to list.

Area and Coordinates:
Several dungeons and raids, including and not limited to Expert Roulette areas, Void Ark, Weeping City, Dun Scaith, Diadem and Alexander Raids.

Housing:
None.

Steps:

Enter dungeon/ raid, and engage in battle.

Silly DPS decides they want to tank the floor. In other words, one of my party members dies. ( Also happens with Tanks and healers, but DPS dies more often. :\\\\'D! Try not to stand in the things xD)

I pop a Swiftcast to raise them. One of two things might happen at random with an almost 75% chance of these happening-

I have the Swiftcast Icon up, but it forces me to start the timer for Raise instead. I have to shake my character out of the cast and pop Raise again. Usually this triggers Swiftcast and the raise is successful.

Or, and this is my favourite, I pop Swiftcast, the icon is up, and it makes me do the timer for my Raise cast. I shake him out of cast mode, then try to hit raise again, and I get the \\\\'Invalid Target\\\\' notification. It refuses to let me raise said individual until AFTER Swiftcast has run out and the icon disappears from my stats bar. Raise is unsuccessful and I have to do full timer after the fact.

My fellow WHM main healer in our FC has also encountered this issue. It\\\\'s firing more often and steadily getting worse. I\\\\'m starting to get seriously concerned, because Swiftcast is vital to have as a WHM, and it buging out like this in dungeons/ parties is making my life hard.

Forgive the double post, but I am on a tablet and the \\\ in my posts were not my doing. It also refuses to let me edit it. ;; ¬;

I have encountered this as well, but I believe it is the result of executing Raise before Swiftcast actually takes effect. It's like using all the DoTs as Summoner and immediately using Fester afterward only to have it use before the last DoT is placed. I doubt anything can be done, we just have to slow our roll a bit lol

Quote:

---

Originally Posted by Joe777

I have encountered this as well, but I believe it is the result of executing Raise before Swiftcast actually takes effect. It's like using all the DoTs as Summoner and immediately using Fester afterward only to have it use before the last DoT is placed. I doubt anything can be done, we just have to slow our roll a bit lol

---

See, I THOUGHT at first it might just be my fingers hitting them buttons too fast. I'm not a 1.0 player, but I've been hitting buttons for almost 2.5 years now. So I thought- "Dayum, son, just slow TF down."

Which was why I haven't mentioned it at all, right? The only thing is, I noticed this happening after patch 3.5 and not before. Unless Dun Scaith has upped my finger reflexed by 10- which, every well could be the case, lel- I almost feel like the triggering is a little off. Because as of recently I've been attempting to slow down my reaction times, and it absolutely has not helped any. It's very much so hit and miss. I always check to see the icon and make sure it's up, and I always keep an eye on the damn thing now that it's started wigging out.

I was going to just shrug it off, but now Swiftcast REFUSES to let me cast Raise on downed party members if it's up at random. It wont let me cast raise at all on a dead party member unless the Swiftcast icon wears off and leaves my stat bar. It says the people I target are 'invalid targets,' and trust me, I've got the correct person highlighted. No matter what I do, if the swiftcast icon is up, my Raise wont register that the person I'm raising is actually dead, and it says they are an invalid target. I'm not so sure that has anything to do with my quick reactions, though perhaps my quick reactions are causing the glitch to happen in the first place? But even then, it picks and chooses when it wants to hit me. : C

i experience this alot before and after the patch, seems like a latency issue to me. I wish swiftcast would get whatever they did to fix mudras instead

Quote:

---

Originally Posted by BillCipher

See, I THOUGHT at first it might just be my fingers hitting them buttons too fast. I'm not a 1.0 player, but I've been hitting buttons for almost 2.5 years now. So I thought- "Dayum, son, just slow TF down."

Which was why I haven't mentioned it at all, right? The only thing is, I noticed this happening after patch 3.5 and not before. Unless Dun Scaith has upped my finger reflexed by 10- which, every well could be the case, lel- I almost feel like the triggering is a little off. Because as of recently I've been attempting to slow down my reaction times, and it absolutely has not helped any. It's very much so hit and miss. I always check to see the icon and make sure it's up, and I always keep an eye on the damn thing now that it's started wigging out.

I was going to just shrug it off, but now Swiftcast REFUSES to let me cast Raise on downed party members if it's up at random. It wont let me cast raise at all on a dead party member unless the Swiftcast icon wears off and leaves my stat bar. It says the people I target are 'invalid targets,' and trust me, I've got the correct person highlighted. No matter what I do, if the swiftcast icon is up, my Raise wont register that the person I'm raising is actually dead, and it says they are an invalid target. I'm not so sure that has anything to do with my quick reactions, though perhaps my quick reactions are causing the glitch to happen in the first place? But even then, it picks and chooses when it wants to hit me. : C

---

I may have been hasty in not reading it all and understand your dilemma now lol and will instead wish you good luck in this getting fixed AND blame Phoenix Downs, not necessarily in that order, just because they only work on Party Members :p

Quote:

---

Originally Posted by ADVSS

i experience this alot before and after the patch, seems like a latency issue to me. I wish swiftcast would get whatever they did to fix mudras instead

---

Maybe it hits people at random? Or maybe I just didn't notice it before? Or.. Maybe I wasn't doing whatever it was that triggered it as often before 3.5. xD! Either way, you're correct on that one. It probably just needs a fix- I just hope that they'll look into cleaning it up. I mean, all things considered, the update with the battle system in 4.0 means a battle overhaul when it comes to moves and move codes. Considering the 'role specific' moves that are coming into play, for instance the loss of a lot of buffs/ the lynching of the cross class moves system altogether, I just hope that A.), PLEASE let Healers/ Mages keep Swiftcast in Role Specific, and B.) That any latency issues that happen with the triggering of the move itself gets overhauled and fixed, rather than patched and ported. You know what I mean? It'd be a shame to have an issue, have the opportunity of changing or removing said issue, and then not doing so when the chance presents itself on a silver platter.

That's why I felt it would be better to bring it up both on the forums and in the in-game reports system. Perhaps if we talk about the latency issue, it can get resolved, or at the very least examined and excluded from the battle system overhaul.

I see you are from Moogle, as many french people are there it might be that it is really the internet connection currently.
Level 3/Orange provider have had some difficulties for over a week now and there were multiple threads about it on reddit for example. SE cant really do much if the lane to frankfurt is blocked a bit.

I feel I've experienced something similar. Doing my solo stuff on WHM, sometimes I feel like Swiftcasting Holy, and, same deal, sometimes it will work, and sometimes it will start hardcast while the buff icon is up.

That's a latency issue - your client has activated Swiftcast, but the server doesn't recognize that it's active before you hit Raise. Like Commander_Justitia says, France is having problems with the Internet backbone provider between you and SE's servers, which is causing higher latency and more connection problems than normal.

Just poking in to say, encountered it too and yeah it's latency and taking 1-2 seconds before you hit raise helps. :)