Printable View
If this has been posted already, im sorry I did not see it. Has anyone used swiftcast and then a spell right after and end up hardcasting it anyway? This happens to me a lot, and unfortunately in the worse situations like when im raising someone. Am I just doing something wrong? or is this actually a problem with the game
The game has a problem accepting swiftcast. you have to spam click it several times and watch the effect show up before you can cast
Sometime lag plays a part here. I'll use Swiftcast and go to cast Thunder 3 but the ability timer hasn't refreshed yet so my Thunder 3 never actually goes off. Thinking I had already casted it I then go to Fire 3 only to find out my Swiftcasted spell never actually went off...
I found that this affects most instant-cast abilities because they aren't really "instant" per-say due to latency between server and client. Summoners may have noticed this when using Bane immediately after casting one of their DoTs (Bane doesn't spread the last DoT). What is happening is that after you use an ability, the client has to let the server know that you cast said ability, and then the server has to acknowledge it and apply buff/debuff and assign the proper status icon. If you use Swiftcast, you have to give it 300-500ms minimum to allow for the server to realize you used that ability and adjust if you're experiencing higher latency. You'll know when Swiftcast is ready by looking for the icon to appear in your buff bar. If you Swiftcast and Raise too fast, you'll actually start casting Raise before Swiftcast is acknowledged and Raise will cast normally, which means the Swiftcast buff will apply to the next skill instead.
Thank you RoyalMeatbun for your post outlining the trouble you are having with a possible system error,
In order for me to submit your report, I will need some more information. You can go Here and you can find templates for Windows and PS3 that represent the kind of details we need. Once you can provide such information we can move forward and resolve this issue. For now I am going to move this thread into Insufficient Information. You will not be able to reply, so once you have gathered the requested data please create a new bug report thread.
- Furlamseere