Bug - Fixed r9417 - Recognition errors is ASH with translation functions

[Fluxxdog]

> ash use_skill(15,to_skill("Jalapeño Saucesphere"))

You don't have a skill uniquely matching "15 Jalapeño Saucesphere"
Returned: false

> ash to_skill("Jalapeño Saucesphere")

Returned: Jalapeño Saucesphere
level => 7
traincost => 5000
class => Sauceror
libram => false
passive => false
buff => true
combat => false
permable => true

> ash use_skill(to_skill("Jalapeño Saucesphere"))

You don't have a skill uniquely matching "1 Jalapeño Saucesphere"
Returned:

The character causing this error has the skill in question and the MP to cast. What's more disturbing is this:

> ash to_skill("Jalapeno Saucesphere")

Returned: Jalapeño Saucesphere
level => 7
traincost => 5000
class => Sauceror
libram => false
passive => false
buff => true
combat => false
permable => true

> ash use_skill(to_skill("Jalapeno Saucesphere"))

You don't have a skill uniquely matching "1 Jalapeño Saucesphere"
Returned:

> ash use_skill(15,to_skill("Jalapeno Saucesphere"))

You don't have a skill uniquely matching "15 Jalapeño Saucesphere"
Returned: false

Could this be a side effect of the non-ASCII-in-ASH code? It was working without error in r9407.

Update: this doesn't work either:

> ash use_skill(15,to_skill(4008))

You don't have a skill uniquely matching "15 Jalapeño Saucesphere"
Returned: false

 

[Veracity]

Revision 9419 fixes the ASH use_skill() function to use the skill's name, rather than data name, when invoking the CLI "cast" command.
Ditto for the hermit() function and the CLI "hermit" command, in regards to the item being traded for.