EQ2 craft macro : EverQuest 2 Premium Discussions

See subject, I have to stop the macro, and restart and sometimes even need to reconfig the macro again to get it going.. and then, just like clockwork, will stop running after about 30 combines.

Is this a known issue? is there a workaround?


Thanks

That shouldnt happen.

When it is running does it say x of 9999 in the status tab of the plugin?

What exactly happens whtn it stops? Does it say stopped crafting?

Yeah, Wyv.. it says x of 99999 combines in the status tab

When it stops, it doesnt give any error messages, as far as I can tell, its still running but it will not continue to click the "begin" button (to start a new combine)

Allmost like its a endless pause loop or something.

It still says its crafting, doesnt say it has stopped.. just will stop clicking.

how long should the delay be between the 2 clicks that starts the combine proccess? seems like for me, its a random time between 5 and 8 seconds.. should it be faster?

I appreciate your help Wyv

Yes, it is random. It is to help look like a real player crafting.

When it stops, see if it shows 30 of 9999 combines.

Look at the bottom of the status window to see if it shows a message there.

Wyv, Played with it again last night.. stopped at 32 of 9999 combines. I restarted my system, started Xu again and it ran fine all night.

I dont know what caused it, I had been using the beta launcher and decided to try the launcher instead and it worked fine.. I didnt think there was a difference between the two .exe's

Anyway, thanks for your time Wyv, im up and running for now.

Wish that happened to me, question which windows did u have locked and which windows up ? For EQ2 and Crafter

Yes, lock your crafting window.

the main progress window was locked, per wyvs instructions.. it happend a coulple of times yesterday, I just restarted my system and it worked like a charm.. especially since the update, I was able to read my book all night and my macro never stopped.

Thanks again for your replies wyv.

only thing I did different was run the xu patcher not the xu beta3 patcher
Not sure if there is a difference