Thread: Made casting system like from before the 1.19!

This new casting system is some kind of joke!

While casting it constantly gives me an error "<spell/skill> cannot be used now."
I have to wait 2/3 melee swings to be able to use skill/cast a spell again, while mob still hits me.
It's really destroys fun of gaming

Please restor casting system like it was before patch 1.19.
Or at least look at this issue and fix it.
I beg of you!

As an evidence here is my log from 2 kills of a NM:

Code:

You defeat Old Six-arms.
You obtain a megalocrab leg.
Punishing Barbs set.
Slow set.
You summon Dexter.
You dismount Dexter.
Blizzard II cannot be used now.
Blizzard II cannot be used now.
Blizzard II cannot be used now.
Slow cannot be used now.
Slow cannot be used now.
Blizzard II cannot be used now.
Thunder II cannot be used now.
Blizzard II cannot be used now.
Blizzard II cannot be used now.
Blizzard II cannot be used now.
Blizzard II cannot be used now.
You defeat Gluttonous Gertrude.
You obtain a dodo feather.
You obtain a piece of dodo tenderloin.
You obtain a piece of dodo tenderloin.
You summon Dexter.
You dismount Dexter.
Blizzard II cannot be used now.
Profundity II cannot be used now.
Profundity II cannot be used now.
Blizzard II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
Profundity II cannot be used now.
Thunder II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Thunder II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Featherfoot cannot be used now.
Featherfoot cannot be used now.
Featherfoot cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Stoneskin II cannot be used now.
Thunder II cannot be used now.
Thunder II cannot be used now.
You defeat Old Six-arms.

Uhm, we get the same message with light shot and other skills as doW. Its not casting system, but battle system. Theive already said they don't want queueing

Yep, welcome to the world 70% of combat classes have already been dealing with and esp more so when trying to initiate any tp/mp/timing type of skill; pretty much every thing besides auto attack (which only the melee people get lol!)

Originally Posted by Medura

...Theive already said they don't want queueing

Yeah, but it's ruining the fun of game. There is nothing more frustrating then dying to mob because I wasn't able to put stoneskin on me on time...

They created a game where people can play solo. But how to play solo, when the game makes it impossible?!

People already complaining about not being able to solo level 30 leves not earlier then on level 36, because some brilliant mind puts level 38 mob on the way to the leve objective (read: ie.Toad poacher in Mun-Tuy Cellars)

Their PTR team sucks

I'm having this problem too. But, none of my friends are. It makes the game unplayable so you would think more people would be talking about it if it were widespread.

It doesn't seem like lag. My other abilities that don't have a cool down fire off right away. It is driving me mad, I hope someone can shed more light on the issue.

1.19a is out and the problem is sorted. for me at least. having fun from soloing NMs once again. ty SE

Originally Posted by Rubicon

FFXI was like this. You can't just queue up what you wanted next. As a mage, I think it's for the best. Siphon MP off dead mobs is kinda cheap.

Umm... Siphon MP is INTENDED to work that way. It grants a MP bonus when used on defeated enemies (says so in the ability help). Try it sometime, once the enemy dies, but has not faded away, select any other ability and try to target it. Now try siphon MP and try to target it. It specifically lets you target defeated monsters to use it on.

I have the same issue of the cool down timers not working. Make go nuts when I think a spell is ready when it's not.. I'm sure that has to be a bug. But it only happens off and on not all the time.