Alchemist rush order issues

[JTdesertace]

I'm a 33 alchemist

so far no rush order works im currently in teir four one the first teir four option.

it has me creat 3 differnt items 2 a peice so like 2,2,2

it closes down after accepting writ when it has started count down.

the error is " could not find a recipe for ' ' , or ect....

so i cant find which spells have the format problems i check the ones that it says to make and they look fine.


Please help

 

[litewave]

I remember it shutting down everytime when manually doing a certain spell (I think it was blessed rush but not sure as i was busy cranking out levels to take advantage of bonus weekend). I didnt get a error message it just closed down the bot. Forgot about that til i saw ye note.

That was also used in writs occasionally. A similiar spell may might be causing part of your problem. if you know what spells the writ wants, try telling the bot to do them manually and see which it barfs on. ie populate the to do list yeself based on the writ text.

Knowing which spell will help them debug the problem.

 

[Nuprecon]

I remember it shutting down everytime when manually doing a certain spell (I think it was blessed rush but not sure as i was busy cranking out levels to take advantage of bonus weekend). I didnt get a error message it just closed down the bot. Forgot about that til i saw ye note.

That was also used in writs occasionally. A similiar spell may might be causing part of your problem. if you know what spells the writ wants, try telling the bot to do them manually and see which it barfs on. ie populate the to do list yeself based on the writ text.

Knowing which spell will help them debug the problem.

Normally if the craft bot just shuts down its due to the bot not being able to find a recipe and adding it to the "CustomWrits.xml" in "InnerSpace\Scripts\EQ2Craft\Recipe Data" will fix the problem.

How ever, if you could post the name of the recipe that is crashing maybe it can be added to the SVN version of the file as well.

 

[marcusw03]

don't forget the handy craft -debug that will output the problems to a file.