Fluent spells

[Burns]

Ars Alchemy: 2k sounds good
: [Spell] Then that's a little bath of heat for Ars Alchemy
*Burns*: Did it work?
*Burns*: Popped some error...
: *Burns* failed to cast a spell
Ars Alchemy:
*Burns*: Let's try again...
: [Spell] Bath of heat for Ars Alchemy
*Burns*: Ah, good to know...

Spell #1 popped an ugly error message and gave no VE, but costed heat and a cast, Spell #2 worked fine.
The magic words are 'bath of heat for'. I suspect that the first try didn't work out because of the ' in the sentence, which is kind of bad for fluent casts, even more so since it's not in the list of prohibited characters in the outer circle description.

I guess it requires some more testing, but if nobody knows, nobody can do something about it

Edited July 19, 2011 by Burns

[The Warrior]

perhaps it was the lowercase b in bath

[Burns]

Wrong case just leads to a failed spell, not a disabled spell, though.

' in the line, but not in the saved words, gives the following message:

[quote]<magicduel.com>

Error: SyntaxError
Err description: undefined
Err number: undefined
Err message: at index 4: expected ';', got 'have'

Ajax response:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's a Kiley' and location = '1_0x2_1' and npc = 0' at line 1You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's a Kiley' and location = '1_0x2_1' and npc = 0' at line 1
alert('Spell failed, check casting');


document.chatmsgform.msg.value='';
do_refreshchat();[/quote]

Also, even the fully correct words don't do the trick if combined with words before it.
'Burning Shield for Kiley' worked, 'Crate a Burning Shield for Kiley' did not.

Since i have a lot of spells to test currently, i'll update regularly with new findings.

A solitary letter added before the saved words, or a wrong case used in the spell words, is sufficient to make the spell fail, but unlike before it comes out as failed spell instead of normal text. I guess one can argue how good the natural casting worked right after implementation, but now it's just like before, with the difference only being that there's no - anymore.
I DID like the 'natural casting' a lot, and i'd like to see it return

Edited July 20, 2011 by Burns

[Grido]

still causing issues?

[Chewett]

Someone test please

[Rophs]

I set my attacklock cast words to "testing alock fluently"

 

"I am testing alock fluently AmberRune" failed

"testing alock fluently on AmberRune" failed

"I am testing alock fluently on AmberRune" failed

[Chewett]

But testing alock amberrune works?

How does it fail? nicely or with errorrs?

[Rophs]

fails nicey

"testing alock fluently AmberRune" cast

[Chewett]

Cool ok thanks.
redmined.